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 capabilities
Table of Contents
Choose your release version
    Home Orlando Now Platform Capabilities Now Platform capabilities Knowledge Management Domain separation and Knowledge Management

    Domain separation and Knowledge Management

    • 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 separation and Knowledge Management

    This is an overview of domain separation and Knowledge Management. 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

    Domain separation works differently at different access levels of an application. In Knowledge Management, data, requester, and fulfiller access to knowledge bases are domain-separated.

    How domain separation works in Knowledge Management

    In Knowledge Management, the following rules apply:

    Data: At the data level of domain separation, data visibility is separated from one domain to another. Knowledge bases, user criteria, articles, categories, article feedback, article versions, article templates, and external sources are domain-separated in the base system.
    Note: The data in one domain cannot be seen in any other domain. For example, if you create a Knowledge Management article in Domain A using an article template from Domain B, the article is not visible in Domain A. Similarly, if you create a Knowledge Management article in the global domain using a template that is not in global, the article might not be visible in all the domains.

    Requester: Requester activities are supported within tenant domains. Users can search; view; comment; and rate articles of their domain, any child domain, and global domains, if feedback is enabled and the knowledge base settings grant them read-access to articles.

    • Users in the global domain can access articles in all the domains if read-access is granted at the knowledge base or article level.
    • Users in the parent domain can access articles in that domain, global, and all its child domains if read-access is granted at the knowledge base or article level.
    • Users in the child domain can access articles in that domain and the global domain if read-access is granted at the knowledge base or article level.

    Fulfiller: The application can be used by the Fulfiller within the tenant domains as a tenant domain-owned application. Users are allowed to author articles in knowledge bases of their domain, any child domain, and the global domain if the knowledge base has user criteria set up to grant contribute access.

    • Articles are automatically saved to the user’s current domain when the article is created.

    • If the glide.knowman.allow_edit_global_articles system property is enabled, users from a domain other than the global domain can check out and edit global articles. Otherwise, system administrators and users from a domain other than the global domain cannot check out global articles and are shown a warning message to that effect. Depending on their access, users can change their domain to the global domain to check out and edit the global articles.
    • Domains of versioned articles are maintained as per the latest article version's domain. This includes updating the domain for kb_version, kb_knowledge, kb_feedback, and sys_attachment tables.
    • If domains contain another domain: If domain A contains domain B, users with access to Domain A can author articles in Domain B by toggling the domain scope. To learn more about toggling domain scope, see Visibility domains and Contains domains.

    See Managing access to knowledge bases and knowledge articles to learn how to control contribute and read access to knowledge bases and knowledge articles.

    Use cases

    This image demonstrates a basic domain hierarchy that is available in the base system.

    Domain Separation Use Case

    Requester use cases

    User domain Knowledge base domain Read user criteria domain Article domain Result
    Global Global Global Global Can view, comment, rate articles.
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
    Parent domain (TOP) Global Global Global
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
    Child domain (TOP/ACME) Global Global Global Can view, comment, rate articles.
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)

    Fulfiller use cases

    User domain Knowledge base domain Contribute user criteria domain Article domain Result
    Global Global Global Global Can author, update, view, comment, rate articles.
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
    Parent domain (TOP) Global Global Global
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
    Child domain (TOP/ACME) Global Global Global Can author, update, view, comment, rate articles.
    Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
    Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
    MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)

    Known Issues

    • The following AQI tables are not domain separated:
      • AQI Checklist [kb_quality_checklist]
      • Checklist Question [kb_checklist_question]
      • Article Checklist Answer [kb_article_checklist_answer]
        Note: The Article Checklist Answer table does not contain the Order field. The application shows the list in a random order.
    • Comment provided by a user on an article is stored in article's domain instead of user domain.
    Related topics
    • 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 separation and Knowledge Management

      • 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 separation and Knowledge Management

      This is an overview of domain separation and Knowledge Management. 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

      Domain separation works differently at different access levels of an application. In Knowledge Management, data, requester, and fulfiller access to knowledge bases are domain-separated.

      How domain separation works in Knowledge Management

      In Knowledge Management, the following rules apply:

      Data: At the data level of domain separation, data visibility is separated from one domain to another. Knowledge bases, user criteria, articles, categories, article feedback, article versions, article templates, and external sources are domain-separated in the base system.
      Note: The data in one domain cannot be seen in any other domain. For example, if you create a Knowledge Management article in Domain A using an article template from Domain B, the article is not visible in Domain A. Similarly, if you create a Knowledge Management article in the global domain using a template that is not in global, the article might not be visible in all the domains.

      Requester: Requester activities are supported within tenant domains. Users can search; view; comment; and rate articles of their domain, any child domain, and global domains, if feedback is enabled and the knowledge base settings grant them read-access to articles.

      • Users in the global domain can access articles in all the domains if read-access is granted at the knowledge base or article level.
      • Users in the parent domain can access articles in that domain, global, and all its child domains if read-access is granted at the knowledge base or article level.
      • Users in the child domain can access articles in that domain and the global domain if read-access is granted at the knowledge base or article level.

      Fulfiller: The application can be used by the Fulfiller within the tenant domains as a tenant domain-owned application. Users are allowed to author articles in knowledge bases of their domain, any child domain, and the global domain if the knowledge base has user criteria set up to grant contribute access.

      • Articles are automatically saved to the user’s current domain when the article is created.

      • If the glide.knowman.allow_edit_global_articles system property is enabled, users from a domain other than the global domain can check out and edit global articles. Otherwise, system administrators and users from a domain other than the global domain cannot check out global articles and are shown a warning message to that effect. Depending on their access, users can change their domain to the global domain to check out and edit the global articles.
      • Domains of versioned articles are maintained as per the latest article version's domain. This includes updating the domain for kb_version, kb_knowledge, kb_feedback, and sys_attachment tables.
      • If domains contain another domain: If domain A contains domain B, users with access to Domain A can author articles in Domain B by toggling the domain scope. To learn more about toggling domain scope, see Visibility domains and Contains domains.

      See Managing access to knowledge bases and knowledge articles to learn how to control contribute and read access to knowledge bases and knowledge articles.

      Use cases

      This image demonstrates a basic domain hierarchy that is available in the base system.

      Domain Separation Use Case

      Requester use cases

      User domain Knowledge base domain Read user criteria domain Article domain Result
      Global Global Global Global Can view, comment, rate articles.
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
      Parent domain (TOP) Global Global Global
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
      Child domain (TOP/ACME) Global Global Global Can view, comment, rate articles.
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)

      Fulfiller use cases

      User domain Knowledge base domain Contribute user criteria domain Article domain Result
      Global Global Global Global Can author, update, view, comment, rate articles.
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
      Parent domain (TOP) Global Global Global
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)
      Child domain (TOP/ACME) Global Global Global Can author, update, view, comment, rate articles.
      Parent domain (TOP) Parent domain (TOP) Parent domain (TOP)
      Child domain (TOP/ACME Child domain (TOP/ACME Child domain (TOP/ACME
      MSP domain (TOP/MSP) MSP domain (TOP/MSP) MSP domain (TOP/MSP)

      Known Issues

      • The following AQI tables are not domain separated:
        • AQI Checklist [kb_quality_checklist]
        • Checklist Question [kb_checklist_question]
        • Article Checklist Answer [kb_article_checklist_answer]
          Note: The Article Checklist Answer table does not contain the Order field. The application shows the list in a random order.
      • Comment provided by a user on an article is stored in article's domain instead of user domain.
      Related topics
      • 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