{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":35817,"path":"now-intelligence/performance-analytics/pa-domain-configurations.md","title":"Approaches to Performance Analytics with domain separation","bundle":null,"doc_type":null,"release":"australia","body":"\n# Approaches to Performance Analytics with domain separation\n\nWhen 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.\n\n## Global approach and collecting domain-specific scores\n\nYou can keep all Performance Analytics records, such as indicators, breakdowns, and widgets, in the Global domain. In this case, you apply domain separation through domain-specific [data collection jobs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/performance-analytics-glossary.md).\n\nTo configure a data collection job to be domain-specific, add a **Run as** user to the job. The **Run as** user determines the domain context of where the data collection job runs. For more information, see [Create or schedule a data collection job](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/t_CreatASchedDataCollJob.md).\n\nYou can also specify a domain configuration. Domain configurations are part of the Performance Analytics plugin for domain support, intended to help with complex domain management. For more information, see [Associate a domain configuration with a data collection job](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/associate-domain-config-dc-job.md).\n\nThe data collection job collects scores against facts table records in the Global domain. The job also collects scores against records in the domains of the **Run as** user. The job stores the scores in the domain it collected them from. In data visualizations, a user sees only scores from domains they have visibility into.\n\nIf you specify only a **Run as** user, scores from all child domains are rolled up to the parent. If you also specify a domain configuration, more options are available. For more information about options for collecting and rolling up child domain scores, see [Grouping domains in Performance Analytics domain configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/pa-domain-separation-msp.md).\n\nOnly users with the pa\\_admin role who are members of one of the domains that the job collects scores for can modify domain-separated data collection jobs. Global users with pa\\_admin can modify any job.\n\nBy default, Platform Analytics Solutions use the global approach.\n\n**Note:** Domain configurations require a global approach to domain separation. For more information, see [Grouping domains in Performance Analytics domain configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/pa-domain-separation-msp.md).\n\n## Domain-specific approach\n\nBy using domain-specific Performance Analytics records, you can grant the pa\\_admin role to domain users to create their own domain-specific components. Users, including administrators, can create and edit Performance Analytics records only within their domain. Users in child domains can read but not edit Performance Analytics records in a parent domain.\n\nYou must create a domain-specific copy of a Performance Analytics record to use it in that domain. For example, to add a domain-specific condition to an indicator source, you must create a copy of the indicator and indicator source in that domain.\n\nYou can quickly copy an indicator or breakdown and related data from a different domain. Use the **Insert and Stay with Relations** UI action on the Indicator or Breakdown forms. Any breakdowns, breakdown exclusions, or time series exclusion relationships are also copied. Any associated scheduled jobs are copied only if the **Run as** user for that job is the current user.\n\nTo collect scores, create a new data collector job associated with the domain-specific indicators.\n\n**Note:** Domain users cannot set Performance Analytics properties that begin with `com.snc.pa`. Only users with the admin or pa\\_admin roles in the global domain can see or set these properties.\n\n## Hybrid approach\n\nA hybrid approach keeps reusable, foundational Performance Analytics records such as indicator sources within the global domain or a parent domain. At the same time, administrators in other domains create domain-specific higher-level Performance Analytics records such as indicators and widgets.\n\n**Note:** The hybrid approach is an advanced option. Implement either the global or domain-specific approaches successfully before attempting to use a hybrid approach.\n\nWhen using a hybrid approach, foundational records should be managed only within the global domain or a parent domain. All other Performance Analytics records, such as widgets and indicators, should be managed separately within each child domain. The following record types are considered foundational records:\n\n-   Bucket groups\n-   Buckets\n-   Scripts\n-   Breakdown sources\n-   Indicator sources\n-   Filters\n-   Breakdowns\n-   Managed sources\n-   Manual breakdowns\n-   Breakdown mappings\n-   Breakdown relations\n\n## Copying Performance Analytics records between domains\n\nYou can reuse Performance Analytics records in multiple domains. The PADomainUtils API provides functionality that enables administrators to move or copy Performance Analytics records between domains.\n\n**Parent Topic:**[Domain separation and Performance Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/now-intelligence/performance-analytics/c_PAWithDomainSeparation.md)\n\n"}}