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:
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.
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 for instructions on creating a domain and adding data sources to it.
Dynamic domain assignment
See how data sources are assigned dynamically below.
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.
Scenario 1
Add 1,000 data sources to a domain.
<1 second on average
Scenario 2
Add 10,000 data sources to a domain.
2 seconds on average
Scenario 3
Add 100,000 data sources to a domain.
30 seconds on average
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:

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

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.
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:
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 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.
See Setting up domains for data product management for details.
Use cases
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.
Domain events
The following domain-related events are audited and can be found on the audit page in the UI:
DomainCreated: A domain is created.
DomainDataSourcesUpdated: Data sources are assigned to or removed from a domain.
DomainDeleted: A domain is deleted.
DomainPermissionsUpdated: A domain-specific permission is applied to or removed from a user or group.
DomainUpdated: 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:
DomainDataSourcesUpdated: Data sources are assigned to or removed from the domain.
TagApplied: A tag is applied to a data source or column, which could lead to a data source being added to a domain.
TagRemoved: 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 for a list of global and domain permissions necessary to manage domains.
Last updated
Was this helpful?

