> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/configuration/domains.md).

# Domains

Learn about how domains allow you to delegate access management and how Immuta enforces domain policies

Domains are containers of data sources that let you assign data ownership and access management to specific business units, subject matter experts, or teams. Instead of routing every governance decision through a central team, domains let the people closest to the data make access decisions for it, while central governance keeps oversight across the organization.

Within a domain, users are assigned domain permissions to complete the following actions:

* Manage policies
* Audit activity
* Manage identifiers
* Publish data products

Because these permissions are scoped to specific domains, users only have power over the data in the domains you assign them, not all data in your organization.

A data owner registers data in Immuta as data sources. A user with the `GOVERNANCE` permission creates a domain and assigns data sources to it, either manually or dynamically based on tags. A user with the `USER_ADMIN` permission then grants domain permissions to the users or groups who will steward that domain. From then on, those stewards can author policies, audit activity, manage identifiers, and publish data products for the data sources in their domain only. Global policies set by central governance continue to apply to every data source, regardless of domain.

## Domain data sources

Data sources can be assigned to domains based on business units in your organization or any other method that suits your business goals and policy management strategy. Data sources can be assigned to a domain one of two ways:

| Assignment method | How it works                                                                                                                                                                 | Best for                                                                                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Manual**        | The `GOVERNANCE` user selects each data source and adds or removes it through the UI or API. Nothing changes without user intervention.                                      | Small, stable sets of data sources that rarely change.                                      |
| **Dynamic**       | The `GOVERNANCE` user selects one or more table tags. Data sources with any of those tags are added to or removed from the domain automatically. Column tags cannot be used. | Large or growing data estates. Dynamic assignment scales better and needs less maintenance. |

{% hint style="info" %}
For the most hands-off setup, use tags that are applied automatically, such as [connection tags](https://documentation.immuta.com/saas/configuration/integrations/registering-a-connection/reference-guides/new-connections-reference-guide.md#tags) or tags from an external catalog. New data sources then land in the correct domain as soon as they are onboarded.
{% endhint %}

Once a data source is assigned to a domain (or multiple domains), users with a domain permission can start performing actions on those data sources.

See the [Create and manage domains guide](https://documentation.immuta.com/saas/configuration/domains/configure-domains.md) for instructions on creating a domain and adding data sources to it.

#### Dynamic domain assignment

See how data sources are assigned dynamically below.

<details>

<summary>Dynamic assignment process</summary>

Auto-assignment is implemented with many Immuta features and components:

1. A user with the `GOVERNANCE` permission creates a domain.
2. During creation, the user decides if data sources should be added [**dynamically**](#user-content-fn-1)[^1] or [**manually**](#user-content-fn-2)[^2]. The user picks dynamically in this example.
3. The tag(s) for dynamic assignment are selected by the user.
4. The domain is created; it has all the data sources that already exist with the selected tag(s).
5. New data sources are created through schema monitoring or object sync:
   1. Data sources created from object sync automatically get a tag from their [connection](https://documentation.immuta.com/saas/configuration/integrations/registering-a-connection/reference-guides/connections-overview.md#connection-tags).
   2. Immuta connects them to the external catalog, pulling in the appropriate tags.
6. Once the data sources get any of the domain assignment tags, they are automatically added to the domain with the selected, matching tag.
7. Tags may change on existing data sources:
   1. Updated by a user: If a user adds or removes the domain assignment tag from a data source, the data source will be added or removed from the domain automatically ([within a few seconds](#performance)).
   2. Updated in an external catalog: If changes come from an external catalog, those changes will be pulled into Immuta every 24 hours. Any changes to tags, and therefore domain assignment, will be enacted within that timeframe.

</details>

### Performance

Adding data sources to a domain, whether dynamically with tag assignment or manually using bulk actions, will take longer the more data sources you are adding. The following scenarios have been tested in order to provide a benchmark of the average time to complete the action.

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Scenario 1</strong></td><td>Add 1,000 data sources to a domain.</td><td><strong>&#x3C;1</strong> second on average</td></tr><tr><td><strong>Scenario 2</strong></td><td>Add 10,000 data sources to a domain.</td><td><strong>2</strong> seconds on average</td></tr><tr><td><strong>Scenario 3</strong></td><td>Add 100,000 data sources to a domain.</td><td><strong>30</strong> seconds on average</td></tr></tbody></table>

## Domain policies

Whether created within or outside a domain, Immuta policies enforce access as usual: users who meet the restrictions outlined in the policy applied to a data source may access that data source. However, domains restrict who can author policies that apply to data sources assigned to that domain. This policy management restriction gives organizations more control over how much power governance users have on data. Furthermore, it can make Immuta easier to use by allowing more people to author policies.

Users with the `Manage Policies` permission in a domain can set global policies to apply to those domains. In the example below, the domain policy manager can only apply global policies to the `HR` domain:

<figure><img src="https://1751699907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWBda5Pt4s8apEhzXGl7%2Fuploads%2Fgit-blob-93e53b6b9a0ae8a5341e14d8f37c9ced5bbe43e6%2Fdomains-policy-2.png?alt=media" alt=""><figcaption></figcaption></figure>

If that same user had the `Manage Policies` permission for the `HR` and `Marketing` domains, they could write global policies to apply to data sources within both of those domains. If that user had the `Manage Policies` permission on all domains in their organization or the global `GOVERNANCE` permission, they could set global policies to apply to all data sources.

When a data source is removed from or added to a domain, Immuta recomputes the policies that apply to the domain. Any policies associated with a domain will be added to or removed from a data source when it is added to or removed from the domain.

See the [Create and manage domains guide](https://documentation.immuta.com/saas/configuration/domains/configure-domains.md#protect-your-data) for instructions on authoring domain policies.

### Designing domain policies

When integrating domains to distribute policy management across your organization, data governance and access control must be applied horizontally (globally across data in your organization) and vertically (locally within specific domains or data products).

<figure><img src="https://1751699907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWBda5Pt4s8apEhzXGl7%2Fuploads%2Fgit-blob-d1c8ac1d1edfa419de2b9587cf2b5e9d58827810%2Fdomains-federated-governance.png?alt=media" alt=""><figcaption></figcaption></figure>

Global policies should reflect your organization's broadest principles, regardless of domain. Domain policies should be fine-grained and specific to the context or use case of that domain.

| Policy level | Authored by                                               | Applies to                                                     | Example                                                                                          |
| ------------ | --------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Global**   | Users with the `GOVERNANCE` permission                    | All data sources in the organization                           | Mask all PII across the organization.                                                            |
| **Domain**   | Users with the `Manage Policies` permission on the domain | Data sources in the domains where the user has that permission | Only show rows in the Sales table where the `country` column matches the user's office location. |
| **Local**    | Data owners                                               | A single data source                                           | Disable a domain policy that conflicts with a more relevant local policy.                        |

Since policies apply to domain data sources at multiple levels, there are instances in which two or three policies could apply to a single domain data source. Data owners can disable and enable policies that are most appropriate for their data source when a conflict occurs. For details about policy conflicts, merges, and policy conflict management, see the following pages:

* [Data policy conflicts](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/data-policies.md#policy-behavior-conflicts-fallbacks-and-lockout)
* [Merging ABAC subscription policies](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/section-contents/reference-guides/subscription-policies.md#merging-abac-global-subscription-policies)
* [Managing non-ABAC subscription policy conflicts](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/section-contents/reference-guides/subscription-policies.md#managing-non-abac-subscription-policy-conflicts)

## Identifiers in domains

Identifiers are grouped into domains with data sources, and when identification runs, a domain's identifiers are only checked against the data sources in that domain. Users with the `Manage Identifiers` permission can create domain-specific identifiers or add them from the reference identifiers. This lets stewards tailor identification to the unique data types, tagging standards, and risk levels in their domain (such as Finance, HR, or Clinical), and manage identification logic independently, without impacting global or unrelated domain logic.

Identification runs automatically when a data source is added to a domain with identifiers. Combined with dynamic data source assignment, this means new data sources are tagged as soon as they are onboarded. See the [Data identification reference guide](https://documentation.immuta.com/saas/configuration/tags/data-discovery/data-identification-reference-guide.md) for details.

## Domains in the Request app

Domains determine how data products are organized and published in the Request app. Users with the `Manage Data Products` permission on a domain can publish data products from that domain's data sources, and domain permissions can be used as a steward source in review flows. A well-structured domain model makes it easier for users to find and request the data they need.&#x20;

See [Setting up domains for data product management](https://documentation.immuta.com/saas/configuration/domains/setting-up-domains-for-marketplace.md) for details.

## Use cases

<details>

<summary>Delegate policy management by line of business</summary>

A large financial services firm has two business units with very different data: insurance data managed by actuaries and investment data owned by portfolio managers. Central governance wants each unit to manage policies for its own data without gaining access to the other unit's data.

This can be configured with domains:

1. **Create an `Insurance` domain and an `Investment` domain** as a user with the `GOVERNANCE` permission.
2. **Assign data sources dynamically** using a business unit tag from your external catalog, such as `Business Unit.Insurance` and `Business Unit.Investment`.
3. **Grant the `Manage Policies` domain permission** to the actuaries group on the `Insurance` domain and to the portfolio managers group on the `Investment` domain.
4. **Author domain policies** within each domain for that unit's specific access needs.

Each business unit governs its own data, while global policies, such as masking PII, continue to apply across both domains.

</details>

<details>

<summary>Organize domains by data platform with connection tags</summary>

A tech-focused organization has separate teams for Snowflake and Databricks: Snowflake is stewarded by platform admins and Databricks by a data science governance team. New tables are registered constantly through object sync.

This can be configured with domains:

1. **Create a `Snowflake` domain and a `Databricks` domain** as a user with the `GOVERNANCE` permission.
2. **Assign data sources dynamically** using each connection's [connection tag](https://documentation.immuta.com/saas/configuration/integrations/registering-a-connection/reference-guides/new-connections-reference-guide.md#tags).
3. **Grant the `Manage Policies` domain permission** to the platform admins on the `Snowflake` domain and to the data science governance team on the `Databricks` domain.

New data sources created through object sync automatically receive their connection tag and land in the correct domain, with no manual assignment.

</details>

<details>

<summary>Meet regional compliance requirements</summary>

A global enterprise must apply EU-specific compliance rules to data from its EMEA operations, and the EU data compliance team needs to show regulators who accessed that data.

This can be configured with domains:

1. **Create an `EMEA` domain** as a user with the `GOVERNANCE` permission.
2. **Assign data sources dynamically** using a region tag, such as `Region.EMEA`.
3. **Grant the `Manage Policies` and `Audit Activity` domain permissions** to the EU data compliance team.
4. **Author domain policies** for EU-specific requirements, such as masking additional fields considered personal data under GDPR.
5. **Use the domain's Audit tab** to review queries and policy changes when preparing for regulatory audits.

The compliance team enforces and audits regional rules without changing policies that apply to the rest of the organization.

</details>

<details>

<summary>Tailor identification for a clinical domain</summary>

A healthcare organization wants new clinical tables tagged as soon as they are registered. The [built-in identifiers](https://documentation.immuta.com/saas/configuration/tags/data-discovery/data-identification-reference-guide/improved-pack-built-in-identifier-reference.md) catch common data like Social Security numbers, but they don't recognize the organization's medical record number (MRN) format.

This can be configured with domains:

1. **Create a `Clinical` domain** and **assign data sources dynamically** using the clinical database's [connection tag](https://documentation.immuta.com/saas/configuration/integrations/registering-a-connection/reference-guides/new-connections-reference-guide.md#tags).
2. **Grant the `Manage Identifiers` domain permission** to the clinical data stewards.
3. **Add relevant reference identifiers** to the domain, such as the built-in Social Security number identifier.
4. **Create a domain-specific `MRN` identifier** with a regex criteria that matches the MRN format and applies an `MRN` tag.

</details>

## Audit

Users with the global `AUDIT` permission can see all audit events throughout Immuta. To scope this audit information to just a single domain, [users can be given the domain `Audit Activity` permission.](#audit-tab)

### Domain events

The following domain-related events are [audited](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md) and can be found on the [audit page in the UI](https://documentation.immuta.com/saas/govern/detect-introduction/index/how-to-guides/use-immuta-audit.md):

* [DomainCreated](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domaincreated-event): A domain is created.
* [DomainDataSourcesUpdated](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domaindatasourcesupdated-event): Data sources are assigned to or removed from a domain.
* [DomainDeleted](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domaindeleted-event): A domain is deleted.
* [DomainPermissionsUpdated](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domainpermissionsupdated-event): A domain-specific permission is applied to or removed from a user or group.
* [DomainUpdated](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domainupdated-event): A domain's details (name, description, settings etc.) are updated.

#### Data source assignment

The following events related to data source assignment are audited and can be found on the [audit page in the UI](https://documentation.immuta.com/saas/govern/detect-introduction/index/how-to-guides/use-immuta-audit.md):

* [DomainDataSourcesUpdated](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#domaindatasourcesupdated-event): Data sources are assigned to or removed from the domain.
* [TagApplied](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#tagapplied-event): A tag is applied to a data source or column, which could lead to a data source being added to a domain.
* [TagRemoved](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/uam-schema.md#tagremoved-event): A tag is removed from a data source or column, which could lead to a data source being removed from a domain.

### Audit tab

If a user has the domain `Audit Activity` permission on a particular domain, they can see domain-specific audit events in the **Audit** tab of the domain. The following domain activities are in that tab:

* **Domain**: Events from when the domain was created, permissions were updated, and the domain was updated.
* **Data sources**: Events from the data sources within the specific domain.
* **Policies**: Events for policies created, edited, or deleted that affect data sources within the domain.
* **Queries**: Events for user queries against data sources within the domain.

## Permissions

Domain permissions can be added to users or groups by a user with the `USER_ADMIN` Immuta permission. See the [Immuta users and permissions guide](https://documentation.immuta.com/saas/configuration/people/users-index/reference-guides/personas-and-permissions.md#permissions) for a list of global and domain permissions necessary to manage domains.

[^1]: **Dynamically** added data sources are based on selected tag(s). Every data source with any of the selected tags is added to the domain, and the domain will continually be updated to ensure every data source with those tags is in the domain. The data sources update automatically as necessary.

[^2]: **Manually** added data sources are picked by the domain owner. No changes will be made to the domain's data sources without user intervention.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.immuta.com/saas/configuration/domains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
