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

Domain separation for Credentials and Connections

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

Domain separation for Credentials and Connections

This is an overview of domain separation for Credentials and Connections.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.

Credentials are tied to various ServiceNow features which access systems outside the instance. Credentials follow the domain separation tied to the feature employing the credentials.

Connections are protocol-specific information referencing a target host outside the instance. A connection can specify the domain to run an activity.

How domain separation works in Credentials and Connections

Credentials access resources outside of the instance, and are used by the Discovery, Orchestration, Service Mapping, and Cloud Management applications. These credentials are not tied to a specific domain, rather, they can be bound to an application and then follow the domain separation that the application uses. Credentials can also be assigned to a MID Server, and then follow the domain separation specified by the MID Server configuration.

Connections access a target host using a JMS, JDBC, or HTTP(s) connection. You can specify global or a specific domain to which the connection belongs.