Domain separation for Platform Analytics dashboards
Summarize
Summary of Domain Separation for Platform Analytics Dashboards
Domain separation in Platform Analytics allows for the logical grouping of data, processes, and administrative tasks into separate domains. This feature enables control over user access to data, ensuring that users can only view and interact with information pertinent to their specific domain.
Show less
To activate domain separation, users must request the domain separation plugin. It is crucial that both domain separation and delegated administration are enabled for users in child domains to access dashboards in parent domains. Notably, users in child domains have read-only access to dashboards and cannot modify them.
Key Features
- Data Visibility: Only shared dashboards are visible to other users, ensuring domain boundaries are respected.
- Edit Permissions: Users can edit dashboards only within their domain; for instance, an HR domain user cannot edit a dashboard created in the parent domain.
- Domain-Specific Content: Dashboard data, including records, tabs, and widget containers, is subject to domain separation rules. Widget content visibility depends on its originating domain.
- Global Dashboards: Dashboards defined at the global level can be accessed by all users with whom they have been shared, ensuring broad visibility across domains.
Key Outcomes
Implementing domain separation allows ServiceNow customers to manage their analytics more effectively by ensuring that dashboard data remains confined to appropriate user groups. This structure enhances data security and integrity while providing clear visibility into domain-specific operations. Administrators are advised to avoid editing domain-separated dashboards from the global domain to prevent visibility issues. Always ensure you are logged into the correct domain when managing dashboards.
Domain separation is supported throughout Platform Analytics. 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
To activate the domain separation plugin, see Request domain separation.
Users in child domains cannot overwrite dashboards. Child domain users only have read access to dashboards.
How domain separation works in Dashboards
- Only dashboards that have been shared are visible to other users. See Share a responsive dashboard.
- Users granted edit permissions on a dashboard can only edit that dashboard if they are in the same domain as the dashboard. For example, a user who is in the HR domain cannot edit a dashboard created in the parent of the HR domain.
Dashboard data that is domain separated includes dashboard records, dashboard tabs, and widget containers. Widget content is governed by the domain separation that applies to the content itself. For example, an admin adds a report created in the HR domain to a dashboard in the IT domain. This report is not visible to users in the IT domain, although they can see the widget container.
- Joe's company
- Other companies in the TOP company
- All HR, CS, and IT child domains in those companies if it is shared with those users.