Domain separation and responsive dashboards
Summarize
Summary of Domain separation and responsive dashboards
Domain separation in ServiceNow enables you to segregate data, processes, and administrative tasks into logical domains, controlling user access and visibility accordingly. This capability extends to dashboard creation and administration, allowing multiple tenants or departments to securely manage and view dashboards within a single instance. To enable this, the domain separation plugin must be activated.
Show less
Important considerations include that users in child domains can view dashboards in parent domains only if both domain separation and delegated administration are enabled. Child domain users have read-only access to dashboards and cannot overwrite them.
How Domain Separation Works in Dashboards
- Only dashboards explicitly shared are visible to users outside the creator’s domain.
- Edit permissions on dashboards are restricted to users within the same domain as the dashboard; a user cannot edit dashboards created in a different domain.
- Domain separation applies to dashboard records, tabs, and widget containers; however, widget content visibility depends on the domain of the content itself. For example, reports created in one domain are not visible to users in another domain, although the widget container appears.
- Dashboards created at the global (parent) level are visible to all users with whom they are shared, spanning parent and child domains.
- Administrators should avoid editing domain-separated dashboards from the global domain, as changes may not be visible to users within separated domains. Always ensure you are logged into the correct domain when editing.
Practical Implications for ServiceNow Customers
This domain separation functionality allows organizations to maintain data privacy and governance across multiple tenants or departments within a single ServiceNow instance, especially when managing dashboards. It supports use cases such as requiring different behaviors or visibility rules per tenant (e.g., making comments mandatory on record closure for one tenant but not another).
By understanding and applying domain separation in dashboards, customers can ensure secure, domain-aware dashboard administration that respects organizational boundaries and user roles.
Domain separation is supported in dashboard 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.
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.