---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Domain separation

# Domain separation and Subscription Management {#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 Domain Separation and Subscription Management

Domain separation in Subscription Management allows for the organization of data, processes, and administrative tasks into distinct domains.
This feature is essential for controlling user access and data visibility, particularly in multi-tenant environments.
It supports user-based subscriptions and monitoring of Now Assist usage in domain-separated instances.
Show full answer Show less  

## Key Features

* **Domain Control:** Administrators can manage which users access specific data through domain configurations.
* **User-Based Subscriptions:** Users can view the domain hierarchy of subscribed users, helping to maintain clarity in multi-tenant scenarios.
* **Allocation Summary:** Provides insights into subscription allocations across domains, assisting administrators in avoiding over-allocations.
* **Now Assist Monitoring:** Users can track assist usage by domain, with SP domain users viewing all domains, while tenant users see only their own usage.

## Key Outcomes

Implementing domain separation enables ServiceNow customers to efficiently manage subscriptions and usage, ensuring data integrity and proper user access. Users benefit from clear visibility into their subscription allocations and assist usage, which promotes better resource management and operational efficiency across different domains.  
Domain separation is supported for Subscription Management. 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-subscription-mgmt__section_r4f_ktc_v2c}

The
support level is Basic but has some exceptions or special conditions.{#domain-separation-subscription-mgmt__p_nsc_nfg_h1c}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider (SP) use cases.
* The user interface, cache keys, reporting, rollups, and aggregations all use the domain at production run time.
* The owner of the instance must be able to set up the application to function across multiple tenants.
{#domain-separation-subscription-mgmt__ul_msq_t2x_zkb}

Sample use case: When an SP uses chat to respond to a tenant-customer's message, the client
must be able to see the SP's response.{#domain-separation-subscription-mgmt__p_psc_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-subscription-mgmt__p_qsc_nfg_h1c}

## Overview of domain separation inSubscription Management {#domain-separation-subscription-mgmt__section_lwq_ktc_v2c}

Subscription Management enables you to manage your subscriptions and monitor subscription usage on your instances. Domain separation is enabled for user-based subscriptions and for monitoring Now Assist usage.  
Note:  
This feature is only available in domain-separated instances. This feature isn't visible in instances without domain separation.

## How domain separation works for user-based subscriptions in Subscription Management {#domain-separation-subscription-mgmt__section_mwq_ktc_v2c}

In domain-separated instances, Subscription Management provides information about the domain of each user that has been allocated a user-based subscription.

Users in the SP domain can view the domains that each of their tenant users is a part of from the Subscribed users tab of subscription details. The Domain column shows the domain
hierarchy of all child and grandchild domains and enables you to filter subscribed users by domain.

Users in tenant domains can only view subscription allocations from the global domain and domains that their organization manages. Users in tenant domains can't see user subscription allocations from parent or sibling domains.  
Note:  
User records created before domain separation is activated are in the global scope until manually assigned a domain. Subscription allocations to global users are visible in all domains.

The Allocation Summary section in the subscription details displays information based on the total number of subscription allocations available across all domains. Administrators can use this information to help avoid
over-allocating user subscriptions in tenant domains.

If you make allocation changes that aren't reflected in the Allocation Summary or Allocation History, clear the cache.

## Monitoring Now Assist usage by domain {#domain-separation-subscription-mgmt__section_zqk_k4k_4fc}

In domain-separated instances with Now Assist, Subscription Management provides information about assist usage by domain.

Users in the SP domain can view assist usage by domain by navigating to AdminSubscription ManagementSubscriptionsAccount level entitlementsNowAssist usage and reviewing the current instance details.

Users in tenant domains can only view their own Now Assist usage. Users in tenant domains can't see the number of assists used in parent or sibling 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)

*[\>]: and then