Contents IT Operations Management Previous Topic Next Topic Domain separation and Service Mapping Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Domain separation and Service Mapping This is an overview of domain separation and Service Mapping. 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. OverviewSupport: Level 1Domain 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.In ServiceNow environments where domain separation is configured, customers can view or manage only application services in domains to which customers have access. How domain separation works in Service Mapping Because of the nature of patterns in Service Mapping, domain separation is handled in a slightly different way than simply configuring separate domains. When creating an application service, the application service is assigned to the user's domain. When manually adding a CI to an application service, you can choose only CIs that belong to the service domain. When manually adding connections to CIs to an application service, users must belong to the same domain as the application service. Refer to Pattern customization topic and MID Server configuration for Service Mapping for more context. The following topics provide operational information on how to use Service Mapping in deployments with domain separation: Enable traffic-based discovery for CI types or specific CIs Create or modify patterns Create entry point types for Service Mapping Enhance patterns without changing their identification sections Customize pattern operations Related topicsDomain separation On this page Send Feedback Previous Topic Next Topic
Domain separation and Service Mapping This is an overview of domain separation and Service Mapping. 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. OverviewSupport: Level 1Domain 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.In ServiceNow environments where domain separation is configured, customers can view or manage only application services in domains to which customers have access. How domain separation works in Service Mapping Because of the nature of patterns in Service Mapping, domain separation is handled in a slightly different way than simply configuring separate domains. When creating an application service, the application service is assigned to the user's domain. When manually adding a CI to an application service, you can choose only CIs that belong to the service domain. When manually adding connections to CIs to an application service, users must belong to the same domain as the application service. Refer to Pattern customization topic and MID Server configuration for Service Mapping for more context. The following topics provide operational information on how to use Service Mapping in deployments with domain separation: Enable traffic-based discovery for CI types or specific CIs Create or modify patterns Create entry point types for Service Mapping Enhance patterns without changing their identification sections Customize pattern operations Related topicsDomain separation
Domain separation and Service Mapping This is an overview of domain separation and Service Mapping. 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. OverviewSupport: Level 1Domain 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.In ServiceNow environments where domain separation is configured, customers can view or manage only application services in domains to which customers have access. How domain separation works in Service Mapping Because of the nature of patterns in Service Mapping, domain separation is handled in a slightly different way than simply configuring separate domains. When creating an application service, the application service is assigned to the user's domain. When manually adding a CI to an application service, you can choose only CIs that belong to the service domain. When manually adding connections to CIs to an application service, users must belong to the same domain as the application service. Refer to Pattern customization topic and MID Server configuration for Service Mapping for more context. The following topics provide operational information on how to use Service Mapping in deployments with domain separation: Enable traffic-based discovery for CI types or specific CIs Create or modify patterns Create entry point types for Service Mapping Enhance patterns without changing their identification sections Customize pattern operations Related topicsDomain separation
