--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # Domain separation in the AI Admin Hub console # Domain separation in the AI Admin Hub console {#ariaid-title1} Release version: Australia Updated July 31, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 the AI Admin Hub console Domain separation in the AI Admin Hub console allows ServiceNow customers to logically separate data, processes, and administrative tasks into distinct domains within a single instance. This separation controls user access and visibility, ensuring data isolation and appropriate service delivery across multiple tenants or organizational units. It supports essential elements such as the user interface, caching, reporting, and aggregations, enabling service providers to manage multi-tenant environments effectively. Show full answer Show less ## Key Features * **Domain separation support:** Enables segregation of data and AI skill configurations per domain, supporting multi-tenant use cases. * **Skill configuration per domain:** Generative AI capabilities are organized into skills that can be configured uniquely or have variants created for each domain, with all skills defaulting to the global domain initially. * **Integration with ServiceNow Otto:** Works with domain separation to restrict data access and AI processing within users' respective domains, ensuring summarizations and AI outputs are domain-specific. * **Granular control:** Domains can have different inputs, roles, triggers, and prompts for AI skills, allowing customization per tenant or business unit. * **Skill activation and management:** Skills must be activated and configured separately within each domain, requiring deactivation of the global skill record and creation of domain-specific records. * **Usage tracking:** Although domain data is separated, Assist consumption is tracked at the instance level via the Subscription Management dashboard. ## Practical Application for ServiceNow Customers ServiceNow customers can leverage domain separation to: * Ensure tenant data privacy and process isolation in multi-tenant or distributed organizational environments. * Customize AI skill behavior and access controls tailored to each domain's requirements, such as different input fields for summarization or access restrictions on AI panels. * Create and test AI skill variants per domain without affecting the global configuration, supporting gradual rollouts or domain-specific tuning. * Manage AI capabilities consistently while maintaining clear boundaries between tenants or business units. ## How to Enable and Configure Domain Separation for AI Skills * Enable domain separation on your ServiceNow instance before configuring AI skills. * Deactivate the global skill record to prevent universal access, then switch to the target domain scope. * Create and activate a domain-specific skill record by configuring it within the AI Admin Hub console. * Recreate any related configuration records that are missing in the domain-specific skill to ensure full functionality. * Repeat this process for each skill and domain where AI capabilities should be available. This approach ensures that AI skills are securely and appropriately scoped, providing a tailored experience aligned with domain-specific business needs and compliance requirements. Domain separation is supported for the AI Admin Hub console. 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. ## Support level: Basic {#domain-separation-in-the-now-assist-admin-console__section_bzh_25q_f1c} {#domain-separation-in-the-now-assist-admin-console__domain-sep-supported} * Business logic: Ensure that data goes into the proper domain for the application's service provider use cases. * The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations. * The owner of the instance must set up the application to function across multiple tenants. {#domain-separation-in-the-now-assist-admin-console__ul_yhr_g2j_xkb} Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer's message, the customer must be able to see the SP's response.{#domain-separation-in-the-now-assist-admin-console__p_lsc_nfg_h1c} For more information on support levels, see [Application support for domain separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#domain-separation-in-the-now-assist-admin-console__p_msc_nfg_h1c} In the AI Admin Hub console, generative AI capabilities are organized into skills. Each skill can be configured differently for each domain or you can create a variant of a skill for a domain. By default, all skills exist in the global domain. ## How domain separation works in the AI Admin Hub console {#domain-separation-in-the-now-assist-admin-console__section_b24_25q_f1c} You must enable domain separation on your instance first before you can use it for ServiceNow Otto skills. ServiceNow Otto works with domain separation. When you use ServiceNow Otto in a domain-separated environment, users are only able to access data within their domain. For example, if a user uses the summarization skill, ServiceNow Otto only uses material that exists within the user's domain when generating that summary. When a skill is domain separated, only users who are in that domain can use the skill that you have configured for that scope. If you're a service provider that hosts multiple clients in the same instance, you can set up domain separation to separate tenant data, processes, and administrative tasks. However, Assist consumption is tracked according to instance without differentiating between tenants. You can track your ServiceNow Otto usage in the Subscription Management dashboard. If you want a domain to have a different version of an existing skill, you can reconfigure and activate the skill or create a variant in the preferred domain. See the section on granting access to ServiceNow Otto skills to a domain. ## Use cases {#domain-separation-in-the-now-assist-admin-console__section_c24_25q_f1c} You can configure the inputs, roles, triggers, and prompts when you're activating or editing a skill or a later variant of the skill. Some use cases include the following examples: * Use the Activity field as an input in the incident summarization in one domain but only use the short description and description fields in another domain. * Grant certain roles access to the ServiceNow Otto panel in one domain while another domain has no role restrictions. * Trigger the generative AI capabilities by using quick actions in Agent Chat in only one domain. * Create a variant of a skill to test one prompt in one domain while another domain uses the default prompt for the skill. ## Granting a domain access to AI skills Domain separation is possible at the skill level and at the individual configuration level. When using the guided setup in the AI Admin Hub, each configuration option has its own record that you can separate by domain. To create a record in a different domain, you must set up the skill while in the scope of your preferred domain. 1. Navigate to the ServiceNow Otto Skill Config (sn_nowassist_skill_config) table. 2. Add the Domain field to the list. If it isn't present, select the gear icon at the top of the list and add the Domain field into the Selected column, then select OK. 3. Find the skill that you want to enable on a domain-by-domain basis. Set Active to false on the skill that is in the global scope. Change the scope to edit the record. 4. Change your current domain to the domain that you want to enable the skill in. 5. Navigate to AllAI Admin HubAI Skills. 6. Navigate to the skill that you want to activate according to domain and select Activate skill. 7. Configure the skill as usual. For more information, see [Activate an AI skill](https://www.servicenow.com/docs/_cxB8oDyWVk~yp8cPa8TMQ "Configure the triggers, settings, and display locations for AI skills to enable generative AI capabilities across the ServiceNow AI Platform."). 8. Return to the AI Skill Config (sn_nowassist_skill_config) table. There should be a new record in the current domain. Open the new record. 9. In a different browser tab, return to the ServiceNow Otto Skill Config table and open the deactivated skill record in the global domain. 10. Compare the global skill record to the one created within your domain. Records on the related list may not be present in the domain-specific skill. If they are not there, you must recreate those records in your domain and attach them to the related list in your domain-specific skill. 11. Repeat the process for each skill and each domain where you want to have the skill available. **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) *[\>]: and then