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

Domain separation and Trusted Security Circles

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

Domain separation and Trusted Security Circles

This is an overview of domain separation in Trusted Security Circles. 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.

Overview

Support: Level 2

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.

How domain separation works in Trusted Security Circles

Domain separation enables MSPs to standardize Trusted Security Circles procedures across the customer base they serve with lowered operational costs and a higher quality of service.

Separate customer work spaces for workflows, dashboards, reports, and so forth ensures that customer data is separated and never exposed to other clients.

Domain separation support in Trusted Security Circles by version releases

Release Support level Notes
Jakarta Level 2 (Data, Requestor, Fulfiller)
Kingston Level 2 (Data, Requestor, Fulfiller)
Madrid Level 2 (Data, Requestor, Fulfiller)

Domain separation setup

Setting up domain separation for Trusted Security Circles requires that you request domain separation, register the central instance for each domain, and configure the job queue.
Important: If you are using domain separation, you must activate the Domain Support - Domain Extensions plugin before activating Trusted Security Circles. Several of the setup steps are also different for domain separation setup.
Feedback