This is an overview of domain separation for Credentials and Connections.With
domain separation you can 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: Standard
- Includes Basic level support.
- Business logic: Processes can be created or modified per customer by the service
provider (SP). The use cases reflect proper use of the application by multiple SP
customers in a single instance.
- The owner of the instance needs to be able to configure the minimum viable product
(MVP) business logic and data parameters per tenant as expected for the specific
application.
Use case: An admin needs to be able to make comments mandatory when a record closes for
one tenant, but not for another.
Overview
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.
