This is an overview of domain separation and Event Management. Domain
separation enables 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.
Support level: Basic
- Business logic: Ensure that data goes into the proper domain for the application’s
service provider use cases.
- The application supports domain separation at run time. This includes domain
separation from the user interface, cache keys, reporting, rollups, and aggregations.
- The owner of the instance must set up the application to function across multiple
tenants.
Use case: When a service provider (SP) uses chat to respond to a tenant-customer’s
message, the client must be able to see the SP's response.
How domain separation works in Event Management
When domains are separated in Event Management, users can
only see and manage alerts and events in their own (tenant) domain.
A domain column is present for Event Management tables
that are provided in the base system. The column displays the name of the domain
to which the event or alert belongs.
Note:
If the domain column does not display in the list, click 
(Update Personalized List) and add the required column. In
addition, you can add a column that displays the domain path.
For information about domain separation limitations in
Event Management, see Configure Event Management domain separation.
