Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Domain separation and Continual Improvement Management

Log in to subscribe to topics and get notified when content changes.

Domain separation and Continual Improvement Management

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 then control several aspects of this separation, including which users can see and access data.


Support: Level 1

Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation.

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

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.

Table Contents
[sn_cim_register] Improvement Initiatives
[sn_cim_task] CIM Tasks
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.