---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# That runs with specific roles

# Create a flow with roles {#ariaid-title1}

* Release version: Australia
* 
* Updated July 21, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create a flow or subflow that runs with assigned roles. Assigning roles enables you
to create a user-initiated flow that runs with its own roles rather than the user's
roles.

## Before you begin

Role required:

* flow_designer or admin to run a flow with a standard role
* an application administrator role to run a flow with a high-security role
{#create-flow-roles__ul_stb_jqb_zjc}

## About this task

Create a flow that runs with its own roles rather than just inheriting the roles of the user who starts the flow. For more information about assigning roles to a flow, go to [Flow roles](https://servicenow-prod.fluidtopics.net/XdVk0vgxYbYYmytwHd~GtQ "Create flows and subflows that run with specific roles. Assigning roles enables you to create user-initiated flows that run with their own roles rather than the user's roles."). For example, allow a flow to run with the itil role so that it can access data belonging to IT Service Management applications such as incidents and problems.

For information about application administration and the special roles that it requires, see [Application administration](https://www.servicenow.com/docs/access?context=application-administration&version=australia&pubname=australia-application-development&ft:locale=en-US).

## Procedure

1. If necessary, log in with a user who has an application administrator role.
2. Navigate to AllProcess AutomationFlow Designer.
3. Click + NewFlow or + NewSubflow.
4. On the Flow Properties form, define the Name, Application, and Description for the flow.  
   For more information, see [Create a flow in Workflow Studio](https://servicenow-prod.fluidtopics.net/gEVHy7dO3gkmJ7P2I90Ygg "Run a sequence of actions and flow logic when the trigger conditions occur.").
5. Expand the Additional properties section.
6. In the Run As field, select User who initiates session.  
   Role selection is not available if the System User option is selected in the Run As field.
7. In the Run with roles field, select one or more roles that you want the flow to use while it runs.  
   The roles you select replace any roles that the user normally has. If you don't select any roles, then the flow runs with the roles normally associated with the user.  
   Tip:  
   If you have the Explicit Roles plugin (com.glide.explicit_roles) activated, add the snc_internal role to your flow.  
   For example, an inbound email flow normally runs as an existing user or as the Guest user when there is no existing user. Guest users don't have access to IT Service Management data such as incidents and problems. Running a flow without any roles may produce access errors when the flow tries to access restricted data on the guest user's behalf. Running a flow with a role such as itil ensures that the flow can access the data it needs.
8. To add one or more application administrator roles, select + Add high-security roles.  
9. In the High-security roles field, select one or more application administration roles that you want the flow to run with.  
   Important:  
   This field only displays high-security roles to users who logged in with an application administrator role.
10. Select Build Flow.

## What to do next

Continue to build and test your flow until you're ready to activate it. You can
modify your flow's roles at any time by updating the Flow Properties form.

*[\>]: and then