--- sourceDocument: Xanadu Platform Analytics sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Grouping domains in Performance Analytics domain configurations # Grouping domains in Performance Analytics domain configurations {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Instead of configuring Performance Analytics for the domains of a specific user, create a reusable domain configuration. Select domains that are visible to a group of users, or filter domains directly. Domain configurations let you define hierarchical relationships and aggregate scores across multiple domains. Note: Performance Analytics domain configurations are enabled with the Performance Analytics -- Domain Separation Support plugin. For more information about plugins, see [Activate a Plugin](https://www.servicenow.com/docs/access?context=t_ActivateAPlugin&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US). Associate these domain configurations with specific data collection jobs and dashboards to provide relevant scores to users. At the same time, maintain your Performance Analytics records, such as indicators, breakdowns, and their sources, in the global domain. Important: Regardless of whether a domain configuration is used, the Run as user always determines the domain context of where the data collection Job runs. Only Performance Analytics administrators with access to all the domains in a configuration can edit a data collection job that has a domain configuration applied to it. ## Required approach {#pa-domain-separation-msp__section_mgw_gqq_qpb} Only the Global approach to Performance Analytics with domain separation supports domain configurations. For more information, see [Approaches to Performance Analytics with domain separation](https://servicenow-prod.fluidtopics.net/a~5UO5UTtbrEfPqhcK1yxg "When using Performance Analytics with domain separation, you can collect domain-specific scores. You can use global or domain-specific Performance Analytics table records or even a combination of both."). ## Data tables, process tables, and Run as user {#pa-domain-separation-msp__section_run-as-user-table-access} The Run as user always determines the domain context of where the data collection Job runs. If you are collecting scores only on data tables such as Incident \[incident\], set an administrator from the global domain as the Run as user. This user, and the data collector running under them, has full visibility of all data table records. A different approach is needed if you are collecting scores on a process domain. It is common practice to define process records such as business rules and SLAs on a process domain. In this case, a Run as user who is a global administrator has visibility only to global domain records of these tables. This limitation also impacts scores collected through [database views](https://servicenow-prod.fluidtopics.net/KzO1fGsm6GUEygdn1yjLBA#gloss-database-view "A database view defines table joins for reporting purposes. For example, a database view can join the Incident table to the Metric Definition table. This view can be used for an indicator source."), for example if a join is made to an SLA table like contract_sla. In such cases, set a user with explicit visibility into the relevant process domains as the Run as user. ## Collection, roll-up, and aggregation options {#pa-domain-separation-msp__section_mjc_mly_z4b} The Domain Configuration record provides flexibility in the way domain records contribute to scores. Prior to the availability of the Domain Support plugin, records in child domains would "roll up" and contribute to the score of a parent domain. The Domain Support plugin provides additional options for how records in child domains should be handled: * Select whether to collect scores from individual child domains. * Select whether to roll up scores from child domains into the parent domain score. You can roll up child domain scores with or without also collecting the individual scores. * If you roll scores from child domains up to the parent domain, select whether to roll up all child domains or only the ones that the domain configuration explicitly includes. * Select whether to sum all collected individual domain scores into an aggregate score. This score is stored in a separate domain. {#pa-domain-separation-msp__ul_c5c_nq5_dpb} The following table shows the scores that are collected for different configurations with a parent domain and three child customer domains. The table also shows aggregate values. {#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__3}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__6}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__12}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__13}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__14}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__21}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__22}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__29}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__36}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__43}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__50}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__57}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__64}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__71}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__78}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__85}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__92}{#pa-domain-separation-msp__table_jyn_3qy_z4b__entry__99} | Configuration | Parent Domain: MSP ||||| | | Configuration | Child domains: Customers ||| MSP contains customers || | | Configuration | A | B | C | MSP | Customers | Aggregate | | Data ||||||| | New incident records | 30 | 100 | 50 | 20 | 0 | - | | Results ||||||| | No aggregate options | - | - | - | 20 | - | - | | No aggregate options + Aggregate | - | - | - | 20 | - | 20 | | Collect Children | 30 | 100 | 50 | 20 | 0 | - | | Collect children + Aggregate | 30 | 100 | 50 | 20 | 0 | 200 | | Collect Children + Roll up only selected domains (A and C) | 30 | 100 | 50 | 100 | 80 | - | | Collect children + Roll up only selected domains (A and C) + Aggregate | 30 | 100 | 50 | 100 | 80 | 200 | | Collect Children + Roll up all child domains | 30 | 100 | 50 | 200 | 180 | - | | Collect Children + Roll up all child domains + Aggregate | 30 | 100 | 50 | 200 | 180 | 380 | | Roll up only selected domains (A and C) | - | - | - | 100 | - | - | | Roll up only selected domains (A and C) + Aggregate | - | - | - | 100 | - | 100 | | Roll up all child domains | - | - | - | 200 | - | - | | Roll up all child domains + Aggregate | - | - | - | 200 | - | 200 | |:-:|:-:|-|-|-|-|-| [Table 1. Example of domain configurations for a single parent domain with three children] {#pa-domain-separation-msp__table_jyn_3qy_z4b} ## Domain configuration records {#pa-domain-separation-msp__section_h2c_3my_z4b} The Performance Analytics -- Domain Separation Support plugin adds the Domain Configurations \[pa_domain_configurations\] table to your instance. The details of each domain configuration are stored in one of these records. ## Transferring records between instances {#pa-domain-separation-msp__section_o24_nnx_m2b} Use update sets to transfer domain configurations between instances. If the domain configuration has Collect aggregate enabled, also transfer the aggregation domain separately. For more information, see [Transfer domain configuration with score aggregation](https://servicenow-prod.fluidtopics.net/ZZST78KzvAXXFC70epAWPw "To transfer between instances a Performance Analytics domain configuration that is set to aggregate scores, transfer both the configuration and the aggregation domain."). * **[Create a domain configuration](https://servicenow-prod.fluidtopics.net/M8QRTb~oK2LmbvG7~fE0Hw)** Create a domain configuration to define which domains to collect scores from and how to store scores within the domain hierarchy. * **[Associate a domain configuration with a data collection job](https://servicenow-prod.fluidtopics.net/zjhXm9Za7J9w8OsEs8aE9A)** To collect Performance Analytics indicator scores from the domains specified in a domain configuration, associate that domain configuration with a collection job. * **[Associate a domain configuration with a dashboard](https://servicenow-prod.fluidtopics.net/BC5uDm4jUXcrbSZvfTXLJA)** Display a domain picker on a dashboard to enable users of that dashboard to view scores from specific domains. * **[Transfer domain configuration with score aggregation](https://servicenow-prod.fluidtopics.net/ZZST78KzvAXXFC70epAWPw)** To transfer between instances a Performance Analytics domain configuration that is set to aggregate scores, transfer both the configuration and the aggregation domain.