Domain separation and Reporting
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- Reporting
Domain separation is supported in reporting and relates to report creation and administration. 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.
Activation
To activate the domain separation plugin, see Request domain separation.
How domain separation works in Reporting
- Reports created in the TOP domain are visible to users in the Joe's Company domain but not in the HR, CS, and IT child domains of Joe's Company.
- Reports created in either the IT, CS, or HR child domains aren’t visible to users in the other child domains, but they are visible to users in the parent Joe's Company domain.
- Reports created in the parent (Joe's Company) domain are available only to users in that domain, but not to users in the child domains.

If you create a report in one domain and copy it to another, the report structure remains the same, but the report data is adjusted for the domain. For example, an Active Incident report shows all active incidents to a user in the parent domain, but only IT incidents to a user in the IT domain.