Domain separation in Live Feed

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 in Live Feed

    Domain separation in Live Feed allows ServiceNow customers to logically segregate data, processes, and administrative tasks into distinct domains. This separation controls user access and visibility to Live Feed content based on domain hierarchy, enhancing data security and governance. Users in parent domains can access content in their own and all child domains, whereas users in child domains are restricted to their own domain’s content.

    Show full answer Show less

    Key Features

    • Domain Hierarchy and Visibility: Parent and child domains define which users can view and share Live Feed content. Parent domain users have broader visibility across child domains, while child domain users have confined visibility.
    • Enablement and Upgrade: Domain separation for Live Feed is available from the Eureka release onward. Upgrading adds a sysdomain column to Live Feed tables, assigning existing records to the global domain to support domain separation without data loss.
    • Application Visibility Control: Administrators can control whether Live Feed is visible in the application navigator per domain and whether users can follow feeds and view content from records.
    • Posting and Sharing: Child domain users can post, reply, delete messages, attach files/links, and rate content only within their domain. Parent domain users can perform these actions across their domain and all child domains, with messages in child domains retaining child domain visibility.
    • Content Viewing: Users view and filter Live Feed content strictly within their accessible domain scope. The "My Feed" feature reflects messages, teams, and hashtags pertinent to the user’s domain.
    • Hashtag Management: Hashtags are domain-specific. Child domain users manage hashtags solely within their domain. Parent domain users can access and manage hashtags across their domain and child domains.
    • Teams Management: Teams are domain-separated. Child domain users can join and invite users within their domain. Parent domain users can join teams in their domain and child domains. New teams are created in the user’s domain or the domain of an associated record, ensuring domain consistency.
    • Email Notifications: Subscription to email notifications is limited to users and teams within the subscriber’s domain.

    Practical Implications for ServiceNow Customers

    Enabling domain separation in Live Feed empowers organizations to maintain strict data segregation and compliance across departments or business units. Administrators have granular control over Live Feed application visibility and user interactions based on domain hierarchy. Users experience consistent Live Feed functionality tailored to their domain access, ensuring relevant collaboration without exposing data outside permitted boundaries.

    When implementing domain separation, consider the domain assignment of teams and records to maintain appropriate visibility and access. Additionally, understand that notifications and hashtag usage are confined to domain contexts, supporting secure and structured communication.

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

    Overview

    Support: Level 2

    Parent and child domains define the Live Feed content that can be viewed and shared with other users.
    • A user in a parent domain can see users and content within their domain and within all child domains that are lower in the domain hierarchy.
    • A user in a child domain can see users and content within their domain but cannot see the parent domain or other child domains at the same level in the domain hierarchy.

    Enable domain separation for Live Feed

    Domain separation for the Live Feed application is available starting with the Eureka release. For users upgrading to Eureka, a sys_domain column is added to existing live feed-related database tables. For existing database records, the value of the sys_domain field is set to empty (global). This allows the domain separation feature to work with existing Live Feed records.

    Show or hide the Live Feed application for a domain

    The administrator can Live Feed visibility for a domain. This includes:
    • Displaying Live Feed in the application navigator.
    • Following a document feed for a record.
    • Viewing Live Feed from a record.

    Use Live Feed with domain separation

    All of the Live Feed features are available to users within a domain and work the same way, with some exceptions to visibility.
    • Posting and sharing content
      • Users in a child domain can interact with other users in the same domain. This includes posting and replying to messages, deleting messages, attaching files and links, and rating content.
      • Users in a parent domain can interact with other users in the same domain and with users in any child domains. Messages that are added to child threads by parent users are given the visibility of the child domain, not the parent domain.
    • Viewing content
      • Users in a child domain can view content that resides within their domain. This includes filtering by feed, sorting, searching, and viewing older messages.
      • Users in a parent domain can view content that resides within their domain and within any child domains.
      • My Feed shows messages, teams, and hashtags based on the user's domain. Showing another user's feed only shows posts visible in the current user's domain.
    • Using hashtags
      • Hashtags are separated by domain. Users in a child domain can use all of the hashtag functions within their domain. This includes tagging messages, viewing available hashtags, changing hashtag names, and searching and filtering by hashtag.
      • Users in a parent domain can use all of the hashtag functions within their domain and can see hashtags in any child domains.
    • Using teams
      • Teams are separated across domains. Users in a child domain can join and follow teams within their domain, and can invite other users within their domain to join teams.
      • Users in a parent domain can join and follow teams that belong to their domain or to any child domains.
    • Exceptions to teams
      • New teams are created in the user's domain. However, if the team has a record associated with it, the team is created in record's domain.
      • New threads in an existing team are created in the domain of the existing team.
      • When a user is creating a new team from a document, if the document domain is not empty or global, the team domain needs to be changed to be the document's domain.
      • For a document-generated team, when the domain of the document changes, the domain of all related Live Feed records changes as well.
    • Subscribing to email notifications

      Users can subscribe to email notifications from users and teams within their domain only.