--- sourceDocument: Australia Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # Permissions-based access control # Permissions-based access control {#ariaid-title1} Release version: Australia Updated March 12, 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 Permissions-based access control ServiceNow's Now Assist leverages AI agents to automate tasks ranging from simple responses to complex problem solving. To ensure security and compliance, permissions-based access control restricts AI agents according to assigned roles and Access Control Lists (ACLs), similar to standard user restrictions. This framework enforces least-privilege access, ensuring AI agents only have the permissions they need and operate strictly within defined boundaries. Show full answer Show less ## Key Features * **Agent Role Inheritance and Identity Types:** Controls which roles and identities AI agents inherit from invoking users to determine their permission scope. * **Access Control Lists (ACLs):** Define who can invoke AI agents and what data they can access once invoked. * **Role Masking:** Allows configuration of an allow-list for roles that AI agents and workflows can inherit, limiting permissions during execution to enforce least privilege. * **Guided Setup for Security Controls:** Step-by-step configurations for AI agents, agentic workflows, and custom skills to specify user and data access permissions. * **Manual Access Testing:** Enables administrators to verify which users can discover and invoke AI agents or workflows to ensure proper access control. * **Role References:** Detailed descriptions of roles such as Now Assist Admin and AI Admin Hub console user, clarifying the permissions each role grants for managing Now Assist features. ## Practical Application for ServiceNow Customers By implementing these permissions-based controls, ServiceNow customers can confidently deploy AI agents knowing they operate securely and within intended limits. Configuring agent roles, identities, ACLs, and role masking ensures that AI agents cannot exceed their authorized scope, preventing unauthorized data access or execution. The guided setup and testing tools streamline configuration and validation, helping administrators enforce security policies effectively. Understanding role permissions allows customers to assign the appropriate level of access to manage and monitor AI agents and skills. Use Agent Role Inheritance, identity types, and granular roles to verify your AI agents have only the permissions they need, and can act only within their intended boundaries. ServiceNow uses AI Agents to perform tasks that range from simple automated responses to complex problem solving. AI agents are restricted by their assigner roles, and are subject to the same ACL limitations as standard users. Now Assist provides several mechanisms to enforce least-privilege access across your * Access control lists (ACLs) that determine who can invoke an agent, user identities that define what data an agent can access once invoked. * Role masking that limits inherited permissions during tool execution {#naai-permissions-based-access-control__ul_apm_shy_q3c}These controls help avoid agentic overreach and verify that AI agents operate within boundaries you define. ## Access controls for AI agents {#naai-permissions-based-access-control__section_agent_access} The following topics describe how to implement, configure, and verify access controls for Now Assist AI agents and agentic workflows. [Implement access control in AI agents](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Understand how ACLs and user identities work together across agentic workflows, AI agents, and tools to control who can invoke an agent and what resources it can access once invoked. : Use role masking to define an allow-list of roles that agentic workflows and AI agents can inherit from invoking users, enforcing least-privilege access during tool execution. [Define security controls for an AI agent](https://www.servicenow.com/docs/access?context=define-sec-controls-aia&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Step through the AI agent guided setup to configure who can access an agent and what data it can act on, covering both user access and data access settings. [Define security controls for an agentic workflow](https://www.servicenow.com/docs/access?context=define-sec-controls-aw&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Step through the agentic workflow guided setup to configure who can access a workflow and what data it can act on, covering both user access and data access settings. [Test user access to an AI agent](https://www.servicenow.com/docs/access?context=test-aia-access&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Run a manual access test to confirm that only the intended users can discover and invoke a given AI agent. [Test user access to an agentic workflow](https://www.servicenow.com/docs/access?context=test-aw-access&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Run a manual access test to confirm that only the intended users can discover and invoke a given agentic workflow. [Configure security controls for a skill](https://www.servicenow.com/docs/access?context=nask-access-control&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : Configure access control for custom skills built with the AI Skill Kit to manage who can invoke skill-based functionality. ## Roles and permissions reference {#naai-permissions-based-access-control__section_roles} The following reference topics describe the roles installed with Now Assist and what each role permits. [AI Admin Hub roles](https://www.servicenow.com/docs/access?context=roles-installed-with-now-assist-admin&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) : A reference list of the roles installed with AI Admin Hub, including the permissions required to activate and manage Now Assist features and skills. [Now Assist Admin \[sn_nowassist_admin.nsa_admin\]](https://www.servicenow.com/docs/access?context=roles-installed-with-now-assist-admin&version=australia&pubname=australia-intelligent-experiences§ion=sn-nowassist-admin-role&ft:locale=en-US) : Details the sn_nowassist_admin.nsa_admin role, which allows users to create, edit, and configure Now Assist skills and settings. [AI Admin Hub console user \[sn_nowassist_admin.user\]](https://www.servicenow.com/docs/access?context=roles-installed-with-now-assist-admin&version=australia&pubname=australia-intelligent-experiences§ion=sn-nowassist-admin-console-user-role&ft:locale=en-US) : Details the sn_nowassist_admin.user role, which provides read-only access to the AI Admin Hub console.