Domain separation and Knowledge Management

  • Release version: Australia
  • Updated March 12, 2026
  • 4 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 and Knowledge Management

    Domain separation in Knowledge Management allows ServiceNow customers to logically segregate data, processes, and administrative tasks into distinct domains. This separation controls data visibility and access, ensuring that users see only the information relevant to their domain or authorized domains. It supports multi-tenant environments by enabling separate management within a single ServiceNow instance.

    Show full answer Show less

    How Domain Separation Works in Knowledge Management

    • Data Level Separation: Knowledge bases, articles, templates, categories, feedback, versions, and external sources are domain separated. Data created in one domain is not visible in another unless specifically shared or accessible.
    • Requester Access: Users can search, view, comment, and rate articles within their domain, child domains, and the global domain if read access is granted. Access rules differ depending on whether users belong to global, parent, or child domains.
    • Fulfiller Access: Article authorship and editing are domain-aware. Users can create or modify articles in their domain, child domains, and the global domain if they have contribute permissions. Editing global articles from non-global domains requires enabling a specific system property or switching domain scope.
    • Domain Scope Management: Users with access to a parent domain can author articles in contained child domains by toggling domain scope, facilitating flexible content management within hierarchical domain structures.

    Support and Configuration

    The application follows standard support levels for domain separation, requiring instance owners to configure core business logic and data parameters for each tenant. This enables tailored processes such as domain-specific mandatory comments on records.

    Known Limitations

    • Some AQI tables (e.g., kbqualitychecklist, kbchecklistquestion, kbarticlechecklistanswer) are not domain separated, which may affect checklist visibility and ordering.
    • User comments on articles are stored in the article’s domain rather than the user’s domain, impacting comment data segregation.

    Practical Implications for ServiceNow Customers

    By implementing domain separation in Knowledge Management, customers can:

    • Maintain strict data isolation between tenants or business units within a single ServiceNow instance.
    • Control read and contribute access to knowledge bases and articles based on domain membership and user criteria.
    • Enable multi-tenant content authoring and management while preserving domain security boundaries.
    • Configure domain-specific business rules to meet diverse organizational requirements.

    Understanding these domain separation mechanisms helps customers ensure proper visibility, governance, and management of knowledge content across their ServiceNow environment.

    Domain separation is supported in Knowledge Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Standard

    • Includes all aspects of Basic level support.
    • Application properties are domain-aware as needed.
    • Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
    • The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.

    Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.

    For more information on support levels, see Application support for domain separation.

    Overview of domain separation

    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 a domain A using an article template which is not in domain A, the article will not be 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 knowledge base and/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 knowledge base and/or article level.
    • Users in the child domain can access articles in that domain and the global domain if read access is granted at knowledge base and/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 will be 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.

    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.