---
title: Configure an agentic workflow
description: You can configure agentic workflows from the AI Agent Studio, but you must duplicate them to modify settings. The USEM AI agents included with the application and used in the agentic workflows are activated by default and aren't editable.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/now-assist-vr-acticvate-agentic-workflow.html
release: australia
topic_type: task
last_updated: "2026-07-29"
reading_time_minutes: 2
breadcrumb: [Configure AI skills and agentic workflows for USEM, Implement, Unified Security Exposure Management, Security Operations]
---

# Configure an agentic workflow

You can configure agentic workflows from the AI Agent Studio, but you must duplicate them to modify settings. The USEM AI agents included with the application and used in the agentic workflows are activated by default and aren't editable.

## Before you begin

**Note:** Depending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents. For more information, see [ServiceNow product tiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/ai-native-sku-overview.md).

Agentic workflows and their AI agents use [role masking](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/implement-aias-security-new.md) to determine which users can access them. Ones installed with your applications have specific roles that come included with the application. If you select **Users with specific roles** for user access, you must configure the security controls to include these roles. For the instructions to change the security controls, see [Define security controls for an agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/define-sec-controls-aw.md).

The ServiceNow Otto® panel must be activated. See [Activate the ServiceNow Otto panel standard chat](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/activate-now-assist-panel.md) for more information.

Role required: aia-admin

## Procedure

1.  Navigate to **All** > **AI Agent Studio** > **Overview**.

2.  Select the **Agentic workflows** tab

3.  Select the link for the agentic workflow that you want to configure and activate.

    You will only see the agentic workflows you're entitled to.

    **Note:**

    If you want to modify an agentic workflow, you must [duplicate](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/clone-aia-usecase.md) it, adjust the settings to suit your specific needs, and then activate the duplicate.

    The Guided setup is displayed. The pages are read-only.

4.  Select the more options menu \[Omitted image "icon-menu-square.png"\] Alt text: Indicates there are more actions available

5.  Select **Duplicate**.

    All the information will be copied except any UI actions, and any triggers will be inactive. Change the new workflow’s description to clearly differentiate this workflow for the LLM.

    **Important:** This AI agentic workflow uses the Knowledge Graph to connect vulnerability data for its responses. You cannot modify the default Knowledge Graph that is used for this agentic workflow, but you can duplicate it and make changes to create a customized Knowledge Graph. See [Using Knowledge Graph Designer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/using-knowledge-graph-designer.md) for more information.

    After you create your customized Knowledge Graph, you must modify the sn\_vul\_ai.retrieve\_vr\_data\_knowledge\_graph\_schema system property so it points to your new Knowledge Graph.

6.  Select **Duplicate** in the modal to confirm your choice.

7.  Fill in the fields in the Guided Setup.

    1.  Define key requirements.

    2.  Select **Save and Continue**.

    3.  Define user access to allow which users can access and interact with this agentic workflow.

        **Note:** The sn\_vul.vulnerability\_admin and sn\_vul.vulnerability\_analyst roles automatically inherit the sn\_vul\_ai.write\_rem\_insights and sn\_vul\_ai.read\_rem\_insights granular roles. If you determine that you want more control over read and write access for the records on the Remediation Compliance Insights \[sn\_vul\_ai\_remediation\_insights\] caching table, these granular roles permit you to grant and deny access for viewing, creating, editing, and deleting records. The VR.System role also inherits these granular roles so background job execution for the workflow can occur.

        For the aggregation framework, the sn\_vul\_ai\_read\_lookup\_aggregations and sn\_vul\_ai\_write\_lookup\_aggregations have been added.

        -   The sn\_vul\_ai\_read\_lookup\_aggregations \[read\] role is inherited by the sn\_vul.vulnerability\_admin, sn\_vul.vulnerability\_analyst, sn\_vul.remediation\_owner, and VR.System roles.
        -   The VR.System role inherits the sn\_vul\_ai\_write\_lookup\_aggregations \[write\] role.
    4.  Select **Save and Continue**.

    5.  Define data access by choosing the user identify this workflow uses for permissions and data access.

    6.  Select **Save and Continue**.

    7.  Add triggers you want the agentic workflow to use to launch automatically.

    8.  Select **Save and Continue**.

    9.  Select channels where you want this agentic workflow to be available to engage with users.

    10. To activate the agentic workflow, select **Save and test**.