This is an overview of domain separation and Live Feed. Domain
separation allows you to 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.
Domain separation in this
application is supported at the Data only level, meaning it
supports the data security model of separating visibility of data from one domain to
another. To learn more, see Application support for domain
Parent and child domains define the live feed content that can be viewed and shared with
- 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
- 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
- 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