---
sourceDocument: Brazil Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Approaches to domain separation

# Approaches to Performance Analytics with domain separation {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Approaches to Performance Analytics with domain separation

When using Performance Analytics with domain separation in ServiceNow, you can collect and manage domain-specific performance scores and records.
This capability allows organizations with multiple domains to tailor analytics data collection and visualization according to domain contexts, ensuring appropriate data visibility and management across global and child domains.
Show full answer Show less  

## Global Approach

The global approach centralizes Performance Analytics records---such as indicators, breakdowns, and widgets---in the Global domain while applying domain separation through domain-specific data collection jobs. These jobs run in the context of a specified "Run as user," which determines the domain scope for data collection. Scores are stored in the domains from which they are collected, and users only see data for domains they have access to.

* Domain configurations can be associated with data collection jobs for managing complex domain groupings and score rollups.
* Only users with the **paadmin** role in the relevant domains or global users with **paadmin** can modify these jobs.
* This approach is the default for Platform Analytics Solutions and requires global domain separation support.

## Domain-Specific Approach

This approach allows each domain to manage its own Performance Analytics records independently. Domain users with the **paadmin** role can create and edit records only within their domain, while users in child domains can read but not edit parent domain records.

* Domain-specific copies of indicators and other records must be created to apply domain-specific conditions or customizations.
* The "Insert and Stay with Relations" UI action facilitates copying indicators or breakdowns along with their related data between domains.
* Data collection jobs must be created per domain to collect scores for domain-specific indicators.
* Domain users cannot modify Performance Analytics system properties; only global **admin** or **paadmin** roles can.

## Hybrid Approach

The hybrid approach combines elements of both global and domain-specific methods. Foundational Performance Analytics records (like indicator sources, buckets, and breakdown sources) are maintained in the global or parent domain, while domain administrators manage higher-level records (indicators, widgets) within their own domains.

* This approach is recommended only after successfully implementing either the global or domain-specific approach.
* It enables reuse of foundational components globally while allowing domain-tailored analytics on top.

## Copying Records Between Domains

To facilitate reuse and migration, ServiceNow provides the PADomainUtils API, enabling administrators to move or copy Performance Analytics records across domains efficiently. This supports flexible management of analytics components in complex domain-separated environments.  
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.

## Global approach and collecting domain-specific scores

You 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://www.servicenow.com/docs/SAYEkH1d7Qjsj7I4aT4WVg#gloss-data-collector "A scheduled job that collects data from one or more indicator sources to produce indicator scores.").

To 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://www.servicenow.com/docs/GPdHL4oL_qC~s6c5OyukQg "Schedule a data collection job to regularly collect Performance Analytics indicator scores and snapshots.").

You 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://www.servicenow.com/docs/vbbl4utppjDUCe7MgX3qpw "To collect Performance Analytics indicator scores from the domains specified in a domain configuration, associate that domain configuration with a collection job.").

The 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.

If 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://www.servicenow.com/docs/TQ4E3cZ2j1z2vN_soX2UVg "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.").

Only 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.

By default, Platform Analytics Solutions use the global approach.  
Note:  
Domain configurations require a global approach to domain separation. For more information, see [Grouping domains in Performance Analytics domain configurations](https://www.servicenow.com/docs/TQ4E3cZ2j1z2vN_soX2UVg "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.").

## Domain-specific approach

By 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.

You 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.

You 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.

To collect scores, create a new data collector job associated with the domain-specific
indicators.  
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.

## Hybrid approach

A 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.  
Note:  
The hybrid approach is an advanced option. Implement either the global or domain-specific approaches successfully before attempting to use a hybrid approach.  
When 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:

* Bucket groups
* Buckets
* Scripts
* Breakdown sources
* Indicator sources
* Filters
* Breakdowns
* Managed sources
* Manual breakdowns
* Breakdown mappings
* Breakdown relations
{#pa-domain-configurations__ul_ygw_ycf_ht}

## Copying Performance Analytics records between domains

You 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.