Test user access to an agentic workflow
Run a manual test to verify that only the users you want to access the agentic workflow can do so.
Before you begin
Role required: sn_aia_admin and either admin or at least one role required by the ACL of the agentic workflow being testing and each of the ACLs of its downstream components
About this task
You can establish the security settings for an agentic workflow in the guided setup to establish which users can access it. See Define security controls for instructions on how to change the user access settings. When you select Save and continue on that step of the guided setup, an ACL is created that establishes limitations on which users can access the agentic workflow.
Once you have created these ACLs, you can verify that they work as intended by using the Test access test type of a manual test of an agentic workflow.
To see instructions for performing manual tests to evaluate performance, see Test performance manually. For more information about automated tests, see Evaluate an agentic workflow.
Procedure
-
Navigate to All > AI Agent Studio > Testing.
-
Select Start manual test.
-
In the Choose a test type drop-down menu, select Test access.
If you want to test the basics of how an agentic workflow works, select AI agent or worfklow. The full instructions for that test type can be found in Test performance manually.
-
Search for or select the name of the agentic workflow you want to test.
-
Select an invoking user.
The invoking user can be the user that triggers the agentic workflow or it can be the invoking user of an upstream component, such as an agentic workflow. For more information about how the invoking user works, see Security for AI agents.
When you select an invoking user, the user roles are populated in the Invoking user roles field. The field is read-only. If you want to change a user's roles, you must change the user's User record. See Assign a role to a user.
-
Select Test access.
[Omitted image "aw-test-access-form.png"] Alt text: Completed test form for a test access test type
Result
The results of the access test are opened in the Access Analyzer in a new browser tab.
Access Analyzer identifies all the ACL calls made in the execution of the agentic workflow, including its AI agents and tools, if any are present. You can see the results of each ACL to verify that each one has the correct user access defined.
What to do next
If the results are different than what you expect or want, you can redefine the security controls of the agentic workflow.
You can also test an agentic workflow's performance with either a manual test or automated evaluations. See Test performance manually or Evaluate an agentic workflow.
---
title: Test user access to an agentic workflow
description: Run a manual test to verify that only the users you want to access the agentic workflow can do so.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/intelligent-experiences/test-aw-access.html
release: brazil
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
breadcrumb: [Create an agentic workflow, AI Agent Studio \(legacy\), AI agents and agentic workflows, Enable AI Experiences]
---
# Test user access to an agentic workflow
Run a manual test to verify that only the users you want to access the agentic workflow can do so.
## Before you begin
Role required: sn\_aia\_admin and either admin or at least one role required by the ACL of the agentic workflow being testing and each of the ACLs of its downstream components
## About this task
You can establish the security settings for an agentic workflow in the guided setup to establish which users can access it. See [Define security controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/define-sec-controls-aw.md) for instructions on how to change the user access settings. When you select **Save and continue** on that step of the guided setup, an ACL is created that establishes limitations on which users can access the agentic workflow.
Once you have created these ACLs, you can verify that they work as intended by using the **Test access** test type of a manual test of an agentic workflow.
To see instructions for performing manual tests to evaluate performance, see [Test performance manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/test-aia-use-case.md). For more information about automated tests, see [Evaluate an agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/execute-aia-eval.md).
## Procedure
1. Navigate to **All** > **AI Agent Studio** > **Testing**.
2. Select **Start manual test**.
3. In the **Choose a test type** drop-down menu, select **Test access**.
If you want to test the basics of how an agentic workflow works, select **AI agent or worfklow**. The full instructions for that test type can be found in [Test performance manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/test-ai-agent.md).
4. Search for or select the name of the agentic workflow you want to test.
5. Select an invoking user.
The invoking user can be the user that triggers the agentic workflow or it can be the invoking user of an upstream component, such as an agentic workflow. For more information about how the invoking user works, see [Security for AI agents](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/aia-security-implementation.md).
When you select an invoking user, the user roles are populated in the **Invoking user roles** field. The field is read-only. If you want to change a user's roles, you must change the user's User record. See [Assign a role to a user](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/t_AssignARoleToAUser.md).
6. Select **Test access**.
\[Omitted image "aw-test-access-form.png"\] Alt text: Completed test form for a test access test type
## Result
The results of the access test are opened in the Access Analyzer in a new browser tab.
Access Analyzer identifies all the ACL calls made in the execution of the agentic workflow, including its AI agents and tools, if any are present. You can see the results of each ACL to verify that each one has the correct user access defined.
## What to do next
If the results are different than what you expect or want, you can [redefine the security controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/define-sec-controls-aw.md) of the agentic workflow.
You can also test an agentic workflow's performance with either a manual test or automated evaluations. See [Test performance manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/test-aia-use-case.md) or [Evaluate an agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/intelligent-experiences/execute-aia-eval.md).
| title | Test user access to an agentic workflow |
| description | Run a manual test to verify that only the users you want to access the agentic workflow can do so. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/intelligent-experiences/test-aw-access.html |
| release | brazil |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 3 |
| breadcrumb | Create an agentic workflowAI Agent Studio \(legacy\)AI agents and agentic workflowsEnable AI Experiences |