{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4060,"path":"build-workflows/workflow-studio/create-flow-roles.md","title":"Create a flow with roles","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a flow with roles\n\nCreate 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.\n\n## Before you begin\n\nRole required:\n\n-   flow\\_designer or admin to run a flow with a standard role\n-   an application administrator role to run a flow with a high-security role\n\n## About this task\n\nCreate 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/flow-roles.md). 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.\n\nFor information about application administration and the special roles that it requires, see [Application administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/application-administration.md).\n\n## Procedure\n\n1.  If necessary, log in with a user who has an application administrator role.\n\n2.  Navigate to **All** > **Process Automation** > **Flow Designer**.\n\n3.  Click **+ New** > **Flow** or **+ New** > **Subflow**.\n\n4.  On the Flow Properties form, define the Name, Application, and Description for the flow.\n\n    For more information, see [Create a flow in Workflow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/create-flow.md).\n\n5.  Expand the **Additional properties** section.\n\n6.  In the **Run As** field, select **User who initiates session**.\n\n    Role selection is not available if the **System User** option is selected in the **Run As** field.\n\n7.  In the **Run with roles** field, select one or more roles that you want the flow to use while it runs.\n\n    \\[Omitted image \"example-flow-properties-run-with-roles.png\"\\] Alt text: Run with roles property using the itil role.\n\n    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.\n\n    **Tip:** If you have the Explicit Roles plugin \\(com.glide.explicit\\_roles\\) activated, add the snc\\_internal role to your flow.\n\n    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.\n\n8.  To add one or more application administrator roles, select **+ Add high-security roles**.\n\n    \\[Omitted image \"add-high-security-roles-option.png\"\\] Alt text: The Add high-security roles option is after the Run with roles option\n\n9.  In the **High-security roles** field, select one or more application administration roles that you want the flow to run with.\n\n    \\[Omitted image \"example-high-security-roles-field.png\"\\] Alt text: The High-security roles field contains two example application administration roles for the Employee Center and the Secrets Management applications.\n\n    **Important:** This field only displays high-security roles to users who logged in with an application administrator role.\n\n10. Select **Build Flow**.\n\n\n## What to do next\n\n\\[Omitted image \"example-flow-execution-details-run-with-roles.png\"\\] Alt text: Sample flow execution details of a flow that ran with the itil role.\n\nContinue 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.\n\n**Parent Topic:**[Create a flow in Workflow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/create-flow.md)\n\n"}}