CIS-SP: Certified Implementation Specialist - Service Provide

In ServiceNow, domain visibility determines whether users from one domain can access records from another domain. To grant domain visibility to a user, you can:

AAssociate a visibility domain to one of the user's roles: This allows any user with that role to see records in the associated visibility domain1.

EAssociate a visibility domain to one of the user's groups: Groups grant their members the visibility domains of the group, which means when a user is part of a group, they inherit the visibility domains associated with that group1.

It's important to note that when a user leaves a group, they lose the group's visibility domains, and the use of visibility domains should be done thoughtfully as excessive use can slow performance2. Moreover, the domain hierarchy should be optimal to prevent performance issues2.

The options B, C, and D are not standard practices for granting domain visibility according to the ServiceNow documentation and best practices. Specifically, associating a visibility domain directly to a user record or setting the visibility domain's parent to the user's domain are not mentioned as recommended methods3421.

The TOP domain in ServiceNow's domain separation model serves as the core data domain and the parent domain for the mapping diagram. This is because the TOP domain is typically owned by the service provider and has control over all other sub-domains within the instance1. It is the highest level in the domain hierarchy and is responsible for the global rules, processes, and administrative tasks that affect all sub-domains1. The instance administration is given to the global and top domains, with the global domain setting the overarching rules and the top domain managing the specifics for each sub-domain1.

Domain separation in ServiceNow is a mechanism to separate data, processes, and administrative tasks into logical groupings called domains. This allows for control over several aspects of this separation, including absolute data segregation between business entities, customization of business process definitions, user interfaces for each domain, and maintenance of some global processes and global reporting within a single instance2.

In summary, the TOP domain's primary purpose is to act as the core data domain, providing a foundation for domain separation and ensuring that the service provider can effectively manage and control the entire domain structure within the ServiceNow instance.

Visibility in ServiceNow can be granted to users through Group Membership and Role.

* Group Membership: Users can be assigned to specific groups, and these groups can be granted visibility to certain records or functionalities within ServiceNow. This method allows for efficient management of user permissions based on their group affiliations.

* Role: Roles define a set of permissions that can be assigned to users. By assigning roles to users, administrators can control what users can see and do within the platform. Roles are a fundamental part of access control in ServiceNow.

* ServiceNow User Criteria and Access Control

* ServiceNow Group Management

In ServiceNow, domain separation allows for the partitioning of data, processes, and administrative tasks into distinct domains within the same instance. When it comes to business rules, if a business rule exists in the parent domain and another non-overriding business rule exists in the child domain, both rules will be executed for the child domain1.

This behavior is part of the domain hierarchy logic, where the child domain inherits the properties and rules of its parent unless explicitly overridden. Since the business rule in the child domain is non-overriding, it does not cancel or replace the parent domain's rule. Instead, it adds to the logic that will be processed when the conditions for the business rule are met.

Therefore, when an action occurs that triggers the business rules, the system will first run the business rule from the parent domain followed by the business rule from the child domain. This ensures that the foundational logic set by the parent domain is always applied, while still allowing for additional, domain-specific customizations in the child domains2.

It's important to note that this behavior can be controlled and configured according to the needs of the organization, and understanding the implications of domain inheritance is crucial for proper domain separation management in ServiceNow3.

Delegated administration in ServiceNow allows tasks and approvals to be temporarily handled by another user. This functionality is particularly useful in scenarios where the primary user is unavailable, ensuring that workflows and processes continue without interruption. It helps maintain efficiency and continuity in service management by allowing designated users to take over specific responsibilities temporarily.

* ServiceNow Product Documentation on Delegated Administration1

* ServiceNow Knowledge Base on Delegated Approvals and Tasks2