--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Domain separation and Cloud Provisioning and Governance # Domain separation and Cloud Provisioning and Governance {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](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 and Cloud Provisioning and Governance Domain separation in Cloud Provisioning and Governance enables the logical segregation of data, processes, and administrative tasks into distinct domains. This separation allows ServiceNow customers, particularly service providers (SPs), to control user access and visibility of data across multiple tenants. It supports data isolation at runtime, including UI, caching, reporting, and aggregations, ensuring that data is routed and managed correctly for each domain. Show full answer Show less ## Key Features * **Support for Service Providers:** SPs can use domain separation to manage multiple customers securely by separating catalogs, resource pools, quotas, permissions, IP address management, scheduling, and billing views per domain. * **Domain Assignment:** Each company is assigned a unique domain, and all related entities (cloud accounts, service accounts, contacts, and cases) reside in the same domain, ensuring consistent data access control. * **User Access Control:** Users and records default to the global domain unless explicitly assigned. Users can only see data in their domain or child domains, while SPs controlling the top-level domain have broader visibility across all domains. * **Domain Separation Configuration:** Requires activation of the *Domain Support - Domain Extensions Installer* and *Service Catalog - Domain Separation* plugins to enable domain separation within Cloud Provisioning and Governance. * **Domain Visibility:** Cloud administrators and users must be manually assigned roles per domain to control access. Domain admins see only their domain data unless assigned to the top-level domain. ## Important Considerations * Not all Cloud Provisioning and Governance tables are domain separated; however, this does not affect domain separation functionality. * Delegated domain administration to cloud admin users of child domains is not supported. * Domains follow a hierarchy where the top domain acts as a parent for service provider domains. ## Practical Benefits for ServiceNow Customers By implementing domain separation in Cloud Provisioning and Governance, service providers can securely manage multiple customers' cloud infrastructure services within a single instance. This capability ensures data privacy, enforces clear administrative boundaries, and simplifies multi-tenant management. Assigning users and resources to domains guarantees that customers see only their relevant data, improving operational security and compliance. ## Next Steps To implement domain separation effectively, activate the required plugins and assign users and entities to appropriate domains. For detailed guidance on setup, maintenance, and best practices tailored to service providers, refer to ServiceNow's domain separation considerations documentation for Cloud Provisioning and Governance. Domain separation is supported in Cloud Provisioning and Governance. 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-cloud-management__section_cwx_fvq_xkb} {#domain-separation-cloud-management__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-cloud-management__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-cloud-management__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-cloud-management__p_msc_nfg_h1c} ## Cloud Provisioning and Governance domain separation overview {#domain-separation-cloud-management__section_fqd_5dk_mkb} All tables in Cloud Provisioning and Governance are not domain separated. Delegated domain separation is not supported. Domain separation for Cloud Provisioning and Governance supports: Service Providers (SPs) using the application to provide data separation. : In this scenario, SPs can provide data separation to multiple customers, where domains are necessary to contain all relevant customer data and processes. For example, an SP provides support to customers who typically use Cloud Provisioning and Governance to manage their IT infrastructure on the cloud. SPs can provide catalogs, template profiles, resource pools, and filter, resource profiles, quotas, and permissions as domain-separated offerings to their customers. They can also provide IP address management (IPAM), lease and business hours scheduling, and a view to billing. ## How domain separation works in Cloud Provisioning and Governance {#domain-separation-cloud-management__section_pvf_wkx_vcb} Domain separation for Cloud Provisioning and Governance aligns one or more companies to a domain. To use domain separation with the application, assign all user accounts to a specific company associated with that domain. All entities that are related to the company, such as cloud accounts and service accounts, are created in the same domain as the company. When a new company is created, create a domain with a unique name and assign it to the company. All related entities for an account, such as contacts and cases, must reside in the same domain. When you create a related entity for a domain-separated account, the entity is assigned to the company domain. Members of a domain can only view the data that is contained within their domain or child domains that are lower in the domain hierarchy. By default, all users and all records are members of the global domain unless you assign them to a particular domain. After you assign a user or a record to a domain, the instance compares the domains. This comparison determines whether the user can view the record. Service Providers (SPs) use domain separation to segregate data for each customer. Users in a given domain can only view the data in their own domains or in child domains. SPs typically control the top-level domain, which allows them to view data that is associated with all domains. Don't delegate administration to cloud admin users of the child domains in Cloud Provisioning and Governance. ## Set up domain separation for Cloud Provisioning and Governance {#domain-separation-cloud-management__section_lnv_nmq_vcb} Ensure that you activate the following plugins: : Domain Support - Domain Extensions Installer plugin (com.glide.domain.msp_extensions.installer) to enable domain separation in Cloud Provisioning and Governance : Service Catalog - Domain Separation plugin (glideapp.servicecatalog.domain_separation) to enable separation of catalog items in different domains in Cloud Provisioning and Governance ## Changes to Cloud Provisioning and Governance tables {#domain-separation-cloud-management__section_zfl_zmq_vcb} Domain separation for Cloud Provisioning and Governance adds the Domain and Domain Path fields to the list views. These fields are not exposed by default. As a domain admin you can customize lists and forms to view these fields. Not all tables in Cloud Provisioning and Governance are domain separated. While some top-level tables are domain separated, several child tables are not domain separated. However, this does not impact how the Cloud Provisioning and Governance application works in a domain-separated context. ## Account domains and related entities {#domain-separation-cloud-management__section_wxj_cnq_vcb} When you create related entities for an account, the domain for the related entities is set to the account domain. ## Domain visibility for cloud administrators and users {#domain-separation-cloud-management__section_b4w_h4q_vcb} Manually assign users with the Cloud User Portal (sn_cmp.cloud_service_user) roles and Cloud Admin Portal (sn_cmp.cmp_root_admin) roles for each domain to the TOP/MSP/Default/Company or leaf domain. Domain administrators and users in Cloud Provisioning and Governance can only view data in the domain that they are created in, until they are assigned to the TOP domain. The Top domain represents a single common parent domain, which acts as a single parent node, for the Service Provider domains. ## Next Steps {#domain-separation-cloud-management__section_d3m_m2k_fkb} For more information on creating, implementing, and maintaining domain separation for Cloud Provisioning and Governance services in the instance you are setting up for your customers, see [Domain separation in Cloud Provisioning and Governance - considerations for service providers](https://www.servicenow.com/docs/MDIZGZ04VHAvOXnbvpSCHA "Review the following considerations to effectively create, implement, and maintain domain separation for Cloud Provisioning and Governance services in the instance that you are setting up for your customers."). **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)