--- sourceDocument: Australia Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # Role masking for AI agents # Role masking for AI agents {#ariaid-title1} * Release version: Australia * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Role masking for AI agents Role masking for AI agents and agentic workflows in ServiceNow enhances security by restricting the roles an AI agent uses during execution. This ensures AI agents operate with least-access privileges, limiting their access to only what is necessary for their tools and tasks. Without role masking, AI agents inherit all roles of the triggering user, potentially granting excessive access. Show full answer Show less ## Key Features * **Role Restriction:** AI agents run with roles limited to the intersection of the invoking user's roles and an approved list of roles defined in role masking configurations. * **Execution Modes:** AI components can run as either an AI user or a dynamic user. Role masking applies only when running as a dynamic user, not when running as an AI user. * **Role Configuration:** Multiple roles can be assigned individually through the Agent Access Role Configuration form, allowing fine-grained role management per Business Unit. * **Dynamic Role Management:** Roles are managed as separate records in the Agent Access Role Mapping table, enabling independent role updates without impacting other teams. ## Key Outcomes * **Improved Security:** By limiting AI agent roles to only what is necessary, the risk of unauthorized access or unintended data exposure is minimized. * **Reduced Blast Radius:** Errors or misuse triggered by prompts are contained within the limited role set, enhancing operational safety. * **Enhanced Auditability:** Restricted roles make AI agent behavior easier to monitor and audit for compliance and governance purposes. * **Flexible Role Management:** Business Units can tailor role assignments to their specific needs without affecting others, supporting decentralized administration. ## Prerequisites * ServiceNow Now Assist for Platform version 10.0.2-SS or later * snaia.admin privileges to configure role masking Role masking for AI agents and agentic workflows helps administrators enhance security by limiting the roles those agents use during tool execution, and by verifying that AI agents run with least-access privileges. An AI agent runs tools, queries data, and updates records on behalf of the user who triggered it. Without role masking, the agent inherits all of the triggering user's session roles, which can give the agent more access than its specialty requires. Role masking lets you restrict the AI agent's runtime role set to only the roles needed for the agent's tools and tasks. By limiting the role set, you reduce the blast radius of any prompt-driven error or misuse, and you make the agent's behavior easier to audit. ## Role masking rules {#role-masking__section_pfn_g2l_pjc} 1. Role masking limits the roles with which an agentic workflow, AI agent or Skill can execute to the intersection between the roles assigned to the invoking user and the roles included in the role masking approved roles list. 2. AI user vs Role mask:The AI admin can choose for the component to run as either an AI user or a dynamic user. If set to run as a dynamic user, the AI admin can configure role masking for the component. Role masking can't be configured for agentic workflows or AI agents set to run as AI users. * If an AI user is selected, all roles assigned to the AI user are available to the agentic workflow or AI agent. This can be used to provide elevated access to the agentic workflow AI agent. * If Role masking is applied to an agentic workflow, AI agent, or tool running as a dynamic user, the component runs with roles with roles limited to the intersection of the current invoking user's roles and the roles included in the role masking approved roles list. {#role-masking__aia-role-masking_ul_qgr_bql_ghc} {#role-masking__aia-role-masking_ol_z3m_qpl_ghc} To know more about AI agent role masking, see [Role masking in AI agents](https://www.servicenow.com/docs/access?context=aia-role-masking&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US). ## Prerequisites {#role-masking__section_rtj_c2l_pjc} To configure role masking on your ServiceNow instance, you must have: * Now Assist for Platform version 10.0.2-SS. * The sn_aia.admin privileges. {#role-masking__aia-role-masking_ul_gm3_zml_ghc} ## Dynamic role addition {#role-masking__aia-dynamic-role-masking} You can add multiple roles to an AI agent's role masking configuration as individual records, rather than as a single delimited list. Each role you add through the embedded list on the Agent Access Role Configuration form creates a record in the Agent Access Role Mapping table. Note: Existing records with the `role_list` column continues to operate as expected. All new role configurations is implement through the `sys_agent_access_role_mapping` table. This design supports the common case where different Business Units can use the same AI agent. The agent is shipped with a minimum set of roles, and each Business Unit can add the specific roles based on their use case. Since each role is a separate record in the table, Business Units can add and remove their own role entries independently, without affecting the role entries owned by other teams. To know more about the configuration, see [Configure role masking for an AI agent](https://www.servicenow.com/docs/n~9MHbykHHMXM~601jS6PQ "Restrict the roles that an AI agent uses at runtime by creating an Agent Access Role Configuration record that limits the agent to a defined set of roles.").