--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # Domain separation # Domain separation in AI Agent Studio {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Domain separation in AI Agent Studio Domain separation in AI Agent Studio enables ServiceNow customers to logically segregate data, processes, and administrative tasks into distinct domains. This separation controls user access and visibility to AI agent configurations, ensuring data protection and operational boundary enforcement across different organizational units or customer environments. Show full answer Show less The domain separation applies both at design time---when creating or updating AI agents, workflows, tools, and triggers---and at run time---when conversations are initiated through various channels, such as the ServiceNow Otto panel or web client. ## Design-time Domain Separation During design time, administrators assign specific domains to AI agent records and agentic workflows. Access to these records is restricted to users belonging to the same or higher domain, maintaining security and data integrity within AI Agent Studio configuration tables. ## Run-time Domain Separation At run time, domain visibility is determined by the user impersonated by the AI agent or by the "Run as" attribute defined in the agentic workflow trigger. This ensures that conversations initiated by AI agents respect domain boundaries, allowing agents to access configurations only within their authorized domain scope. ## Technical Implementation * The **sysdomain** field is added to all AI agent tables to support domain separation. * The **sysdomainpath** feature must be enabled in the ServiceNow instance to fully utilize domain separation capabilities. * The **sysoverrides** column on domain-aware tables enables process separation, allowing different domains to have customized processes independent of parent domains. ## Supported Features and Limitations * AI agent configurations, tools, and memory categories can be active or inactive depending on the domain. * Domain-specific overrides are supported for properties (**snaiaproperty**) and triggers. * Agentic workflow discovery respects domain visibility, ensuring workflows are accessible only within their domains. * Note that AI agent and agentic workflow details themselves cannot be overridden across domains. ## Practical Benefits for ServiceNow Customers Implementing domain separation in AI Agent Studio allows customers to: * Maintain strict data and configuration isolation between different business units or clients. * Control user access to AI agents and workflows based on domain membership. * Customize AI agent behavior and triggers on a per-domain basis without affecting other domains. * Ensure secure and compliant AI conversational interactions aligned with organizational boundaries. Domain separation is supported for AI agents in the AI Agent Studio. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data. ## Domain Separation Overview {#aia-studio-domain-separation__section_ity_lyh_cfc} AI agents use basic domain separation capabilities to help protect your users' data. Domain separation support for AI agents is applied at design time and run time. Design-time support : Refers to creating or updating agentic workflows, agents, tools, trigger configurations, and so on. AI agent configurations can be made domain-specific for individual agents and the actual agentic workflows. Administrators can apply specific domains to those records. Similar to other basic domain separations, records in the AI agents tables are accessible if the user belongs to the same or a higher domain than those records. Run-time support : Refers to the agentic conversation on the ServiceNow Otto panel, web client, or any conversational channel. In the agentic conversations, the user that the agent impersonates functions as an agent with any AI agents who initiate the conversation on demand. For example, if the conversation is happening via a trigger mentioned on the Run as field on the Trigger form of an agentic workflow. If the user that the agent impersonates belongs to the same or a higher domain, that agent can access and use configurations that are associated with that domain. The domain visibility for an agentic workflow is resolved during run time based on the Run as attribute in the agentic workflow trigger condition. For more information, see [defining a trigger for an agentic workflow](https://www.servicenow.com/docs/ouU24g1HbKI4I9H0oVZWUg "Create an agentic workflow in AI Agent Studio so that AI agents can coordinate to solve complex problems."). When an agentic conversation is triggered on demand, the domain visibility is applied to the particular agent in action. When an agentic conversation is initiated through a trigger, the domain visibility is applied to the user who resolves the caller (in an incident record where the Run as attribute is set to Caller), when the conversation runs against the incident record. Note: The sys_domain field is added to all AI agent tables to achieve domain separation in AI Agent Studio. The sys_domain_path, which is available for domain separation, is enabled on your instance. To understand more about the ServiceNow domain separation, see [Exploring domain separation](https://www.servicenow.com/docs/access?context=c_DomainSeparation&version=australia&pubname=australia-platform-security&ft:locale=en-US). ## How domain separation works in AI Agent Studio {#aia-studio-domain-separation__section_jty_lyh_cfc} Process separation is enabled through the use of the sys_overrides column in domain-aware tables. Any table that contains both the sys_domain and the sys_overrides fields can be configured to have different processes from the parent domain. AI Agents support only configuration tables to be process separated. Below are the list of tables that are process separated: * sn_aia_agent_config * sn_aia_usecase_config_override {#aia-studio-domain-separation__ul_bf2_dhp_cfc} Domain separation in AI agents supports: * Agentic workflow discovery. * AI agent and its tools can be active in the X domain and inactive in the Y domain. * Memory category can be active in the X domain and inactive in the Y domain. * sn_aia_property can be overridden in a different domain. * Triggers can be overridden in different domain. {#aia-studio-domain-separation__ul_dxn_nhp_cfc} Note: AI agent and agentic workflow details can't be overridden in the different domains. **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)