Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform administration
Table of Contents
Choose your release version
    Home Madrid Now Platform Administration Now Platform administration Platform security Domain separation Understanding domain separation Domain assignment

    Domain assignment

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Domain assignment

    By default, domain separation adds a domain field to tables and their extensions.

    You can also extend domain separation to any new tables you create by adding a sys_domain field to the table's dictionary definition. By default, the system only domain-separates platform and baseline application tables where appropriate.

    Warning: ServiceNow does not recommend domain-separating platform tables (any table with the sys_ prefix such as the Dictionary Entry [sys_dictionary] and Dictionary Entry Override [sys_dictionary_override] tables) because it can produce unexpected results.

    Each record is assigned a single domain.  That domain is stored in the sys_domain field. Several tables, by default, have the sys_domain column and are already domain separated. 

    The value of the sys_domain field contains the domain assigned to the record by any of the following:
    • Company to which the user belongs
    • Business rule when creating record
    • Module used when creating record
    • Form template used when creating record
    • Domain of the parent record
    • Domain assigned to User record
    • Domain of the user who creates it

    The system prevents the following tables from being domain separated:

    • Access Control [sys_security_acl]
    • Script Include [sys_script_include]
    • System Property [sys_properties]
    • Security Black/Whitelist Entities [sys_security_restricted_list]
    • Dictionary Entry [sys_dictionary]
    • Dictionary Entry Override [sys_dictionary_override]

    Assigning users to companies

    Administrators can quickly assign users to a domain by assigning them to a company. After users are assigned to a domain, records automatically inherit the user's domain.

    For example, assigning Bow Ruggeri to the ACME company automatically assigns him to the ACME domain. Assigning Don Goodliffe to the Initech company automatically assigns him to the Initech domain. Any records they create are automatically added to the appropriate domain.

    Figure 1. Adding a user to a domain by setting the company

    Using business rules to assign domains

    Administrators can use a business rule to automatically set a domain value when creating a record. The business rule must set a value in the sys_domain field. Administrators must ensure there is a sys_domain column available for the record's table.

    Using modules to assign domains

    Administrators can use the sysparm_domain URL parameter to automatically assign new records to a particular domain from a module. Administrators must create a module with an Argument value of: sysparm_domain=sys_ID of domain.

    Using form templates to assign domains

    Administrators can use a form template to automatically assign new records to a particular domain. Administrators must add the sys_domain field to the form and select a domain value. For example, setting the sys_domain field to TOP/ACME domain automatically assigns all records from this template to the TOP/ACME domain.

    Domain inheritance on tables

    By default, related records inherit the domain of the parent record. For example:

    • A change task record inherits the domain of the parent change request record.
    • A problem record inherits the domain of the parent incident record.

    Automatic domain assignment based on user domains

    If no other domain conditions apply, a record automatically inherits the domain of the user who creates it.

    Related concepts
    • Visibility domains and Contains domains
    • Domain scope
    • Domain query methods
    Related reference
    • Application support for domain separation
    • Installed with domain separation

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Domain assignment

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Domain assignment

      By default, domain separation adds a domain field to tables and their extensions.

      You can also extend domain separation to any new tables you create by adding a sys_domain field to the table's dictionary definition. By default, the system only domain-separates platform and baseline application tables where appropriate.

      Warning: ServiceNow does not recommend domain-separating platform tables (any table with the sys_ prefix such as the Dictionary Entry [sys_dictionary] and Dictionary Entry Override [sys_dictionary_override] tables) because it can produce unexpected results.

      Each record is assigned a single domain.  That domain is stored in the sys_domain field. Several tables, by default, have the sys_domain column and are already domain separated. 

      The value of the sys_domain field contains the domain assigned to the record by any of the following:
      • Company to which the user belongs
      • Business rule when creating record
      • Module used when creating record
      • Form template used when creating record
      • Domain of the parent record
      • Domain assigned to User record
      • Domain of the user who creates it

      The system prevents the following tables from being domain separated:

      • Access Control [sys_security_acl]
      • Script Include [sys_script_include]
      • System Property [sys_properties]
      • Security Black/Whitelist Entities [sys_security_restricted_list]
      • Dictionary Entry [sys_dictionary]
      • Dictionary Entry Override [sys_dictionary_override]

      Assigning users to companies

      Administrators can quickly assign users to a domain by assigning them to a company. After users are assigned to a domain, records automatically inherit the user's domain.

      For example, assigning Bow Ruggeri to the ACME company automatically assigns him to the ACME domain. Assigning Don Goodliffe to the Initech company automatically assigns him to the Initech domain. Any records they create are automatically added to the appropriate domain.

      Figure 1. Adding a user to a domain by setting the company

      Using business rules to assign domains

      Administrators can use a business rule to automatically set a domain value when creating a record. The business rule must set a value in the sys_domain field. Administrators must ensure there is a sys_domain column available for the record's table.

      Using modules to assign domains

      Administrators can use the sysparm_domain URL parameter to automatically assign new records to a particular domain from a module. Administrators must create a module with an Argument value of: sysparm_domain=sys_ID of domain.

      Using form templates to assign domains

      Administrators can use a form template to automatically assign new records to a particular domain. Administrators must add the sys_domain field to the form and select a domain value. For example, setting the sys_domain field to TOP/ACME domain automatically assigns all records from this template to the TOP/ACME domain.

      Domain inheritance on tables

      By default, related records inherit the domain of the parent record. For example:

      • A change task record inherits the domain of the parent change request record.
      • A problem record inherits the domain of the parent incident record.

      Automatic domain assignment based on user domains

      If no other domain conditions apply, a record automatically inherits the domain of the user who creates it.

      Related concepts
      • Visibility domains and Contains domains
      • Domain scope
      • Domain query methods
      Related reference
      • Application support for domain separation
      • Installed with domain separation

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login