---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/intelligent-experiences

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Domain separation

# Domain separation and Now Assist AI Agent Studio {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Domain separation is supported for Now AssistAI 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}

Now Assist
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 Now Assist 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://servicenow-prod.fluidtopics.net/hAE0HO19ogLgwX0KK2loVw "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.  
Nota:  
The sys_domain field is added to all AI agent tables to achieve domain separation in Now Assist AI agents. 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 Now Assist
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 Now Assist 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}  
Nota:  
AI agent and agentic workflow details can't be overridden in the different domains.
**Tópicos relacionados**   

* [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)