Domain separation terms

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain Separation Terms

    Domain separation in ServiceNow enhances efficiency, security, and performance for customer organizations. Understanding key terms helps customers configure their instances effectively.

    Show full answer Show less

    Key Features

    • Managed Domain: Administrators can manually select domains for users and records, overriding automatic assignments to customize application functions.
    • Process Tables: These tables indicate if delegated administration is in effect through the Overrides field, allowing admins to manage domain-specific policies.
    • Domain Types:
      • Customer Domain: Controls the user interface and data usage processes.
      • Process Domain: Defines specific processes and UI settings without including core user data.
      • Data Domain: Houses data relevant to multiple customers, shared without exposing customer-specific domains.
    • User Data: User records are created primarily in customer domains, with admin accounts in the global domain to facilitate administrative tasks.

    Key Outcomes

    By utilizing domain separation, ServiceNow customers can manage diverse organizational needs securely while maintaining performance. Domain managers can oversee user administration and application functionalities, whereas instance administrators handle overall process management, ensuring effective governance across domains.

    With a ServiceNow instance, you can improve efficiency, add greater security, and increase performance for your customer organizations. It's helpful to understand some of the most common terms as you create your configurations.

    Managed domain

    In a managed domain, the Managed domain field allows domain administrators to manually select a domain for the user, group, department, location, or CI record, rather than using the domain that is assigned automatically from the company record.

    If you want to change those properties, you can override them to further customize the functions of the applications in each of your domains.Manual override switch

    Process tables

    In process tables, if you see a value in the Overrides [sys_overrides] field, a process override record exists. That means that delegated administration, which is how administrators can set domain-specific policies, is in effect. Admins in the global domain can use the Expand/Collapse Domain Scope related link to see override records.

    Note:
    Reports are separated into domains and contain an Overrides field. To view all reports from the global domain, use the Expand Domain Scope related link.

    When you view process tables from a domain, you see only the relevant process records for the selected domain. When you view a process table from the global domain, the Expand Domain Scope related link is displayed to let you see all process records, including overrides. To view only the relevant process records for global again, use the Collapse Domain Scope related link.

    The domain scope feature is used only for process tables and causes the visibility of data on the table to shift in the opposite direction. For example, a record in the parent domain can be seen in the child, but a parent cannot see a child record. This allows the process to flow down to child domains.

    Overrides

    Types of domains

    Different types of domains can help you organize your processes and data and how they function in the application or feature.

    Customer Domain

    In the customer's domain is the user interface, as well as the process that controls how the data Is used.

    The ACME domain in the following image is a customer domain.

    Process Domain

    You create processes for how the data is used and what it does in the domain. These processes must have these attributes:
    • Specific processes and UI settings for a set of domains
    • No core data of any kind (such as specific user data).
    • The TOP domain in the following image is a process domain.

    Data Domain

    The data domain holds data that is relevant to multiple customers. That data can be shared without sharing the actual customer domains. Each customer has its own data domain and can access it.
    Note:
    This kind of domain is not common and can cause performance issues if overused. Consult with an SP architect before use.

    Example: The domain may hold tasks that ACME, Cisco, and the SP all need to interact with.

    The Default domain in the following image is a data domain.

    User Data

    User record data never belongs in the global domain or any of the process domains. Users are primarily created in customer domains and can on occasion be created in data domains.

    Admin accounts are special as they should not be used as everyday users of the instance and should be in the global domain to facilitate administrative functions.

    Figure 1. Domain hierarchy
    Domain hierarchy

    Lists, admin, global process

    Lists

    From the global domain, if you right-click any choice field’s label, select Configure Choices, and then add a new choice, the choice pushes automatically to all domain-specific lists for that field. If the new option is marked as Selected, it is added as active. If the new option is marked as Available, it is added as inactive.

    Instance Administration

    The instance owner’s administrators must handle all normal process creation, modification, and maintenance in a domain-separated instance. Individual domain managers can maintain some parts of data-driven processes. The types of domain managers maintain user administration, support group memberships, and locations, or manage applications that are designed with tenant administration in mind.

    Global process/parameters

    You can create and maintain the process that affect the global domain as well as set the parameters. These properties are common for all users of a domain-separated instance.

    Examples: System properties, dictionary overrides, sys_documentation (field labels), the data model (classes, CI types, and so on), tables and fields [sys_dictionary] (access can be restricted), indexing (text indexes as well as database), ACLs, installation exits, inbound actions, public pages, and interceptors.