--- sourceDocument: Brazil IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Domain separation in CIM # Domain separation and Continual Improvement Management {#ariaid-title1} Release version: Brazil Updated September 10, 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 and Continual Improvement Management Domain separation in Continual Improvement Management (CIM) enables ServiceNow customers to segregate data, processes, and administrative tasks into logical groupings called domains. This separation applies to all features of the CIM application, including data, business logic, user interface, reporting, and caching, ensuring that users only see and access information relevant to their domain. It supports multi-tenant use cases, allowing service providers and tenants to securely manage improvement initiatives within their respective domains. Show full answer Show less ## Key Features * **Comprehensive domain separation:** Applies across CIM data, logic, UI, cache keys, reports, rollups, and aggregations. * **Out-of-the-box support:** No additional setup or configuration is required to enable domain separation in CIM. * **Domain-aware tables:** The Improvement Register and CIM Tasks tables include Domain and Domain Path columns to segment data by domain. * **Role-based access:** Users can view or create improvement initiatives and tasks only within their assigned domain or hierarchical parent domains. * **Multi-domain visibility:** Parent domain users can access child domain initiatives, supporting cross-domain management. * **Integration-aware domain control:** Users must belong to the domain of any integrated application records they associate with improvement initiatives. ## Practical Use Cases * An Improvement Requester in a specific domain can create and view initiatives limited to that domain and its parent or global domains. * Improvement Managers can oversee initiatives across multiple domains but focus updates and content within specific domain contexts. * Service providers using chat to respond to tenant messages ensure that tenant users see only the responses relevant to their domain. * Users creating improvements on behalf of others must be in the same domain as the user they represent. ## Key Outcomes By leveraging domain separation in Continual Improvement Management, ServiceNow customers achieve secure, organized, and scalable multi-tenant improvement workflows. This separation ensures data privacy, controlled access, and clear process boundaries, facilitating efficient management of continuous improvement initiatives across distinct organizational units or service providers. Domain separation in Continual Improvement Management is configured to apply to all features of the application. Separation of data is configured along with separation of logic and process. 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 {#cim-domain-separation__section_gb5_syq_xkb} {#cim-domain-separation__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. {#cim-domain-separation__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.{#cim-domain-separation__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=brazil&pubname=brazil-platform-security&ft:locale=en-US).{#cim-domain-separation__p_msc_nfg_h1c} ## Domain separation and Continual Improvement Management overview {#cim-domain-separation__section_pvf_wkx_vcb} When an improvement opportunity is discovered within your organization, you can implement the improvement in a structured manner using Continual Improvement Management with domain separation. Once an improvement initiative is created, the Improvement Manager uses the Improvement Register to review and prioritize the improvement, and assigns improvement tasks. CIM task owners are responsible to fulfill assigned tasks to the desired outcome of that improvement. Both Improvement Register and CIM Task tables support domain separation so the Improvement Requester, task owners, Improvement Coordinator, and Improvement Manager can view only the improvement initiatives and related tasks within the (tenant) domain to which they belong. ## How domain separation works in Continual Improvement Management {#cim-domain-separation__section_ydt_kth_scb} Domain separation is supported in Continual Improvement Management with no CIM setup or configuration required. Improvements can be created in separate domains, including the global domain. Continual Improvement Management extends the platform Task \[task\] table. When domain separation is implemented, CIM users can view and request improvements initiatives only in the domain assigned. Domain and Domain Path columns are available for two main CIM tables (Improvement Register and CIM Tasks) provided with the base system. The Domain column contains the name of the domain to which the event or alert belongs, and the Domain Path column contains the unique domain identifier. {#cim-domain-separation__table_hxr_qd5_d2b__entry__2} | Table | Contents | |-|-| | \[sn_cim_register\] | Improvement Initiatives | | \[sn_cim_task\] | CIM Tasks | [ ] {#cim-domain-separation__table_hxr_qd5_d2b} Note: If the domain column is not shown, click the Update Personalized List icon and add the required column. You can also add the domain path column, if desired. Use cases: * An Improvement Requester that belongs to the Acme domain creates an improvement initiative and wants to view it.A user must belong to the Acme domain, its parent domain, or the global domain to view the improvement initiative. * An Improvement Manager that belongs to a parent domain tries to view an improvement initiative in a child domain.The user of a parent domain can view improvement initiatives of the parent as well as all child domains of that parent. * An Improvement Requester that belongs to Acme domain wants to create an improvement initiative on behalf of another user in the Acme domain.A user must belong to the same domain as the user for which the improvement initiative is created. * An Improvement Requester wants to associate a record for an integrated application in the Acme domain.A user must belong to the domain of the integrated application from which a record is associated. * An Improvement Manager has access to multiple domains, but wants to update a record with content within a specific domain.The domain specified for the current record drives the functionality of that record and reference fields. {#cim-domain-separation__ul_xfb_glm_d2b} **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=brazil&pubname=brazil-platform-security&ft:locale=en-US)