> 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/designing-a-domain-structure.md).

# Designing a Domain Structure

Learn how to plan a domain structure that matches how your organization owns and governs data

A domain structure determines who governs which data in Immuta. Each domain defines a set of data sources and the users who can author policies, audit activity, manage identifiers, and publish data products for them. Because of this, the way you divide your data into domains is also the way you divide governance responsibility across your organization.

There is no single correct structure. The right one reflects how your organization is already divided and who knows each set of data best. This page walks through the decisions that shape a domain structure.

For details on how domains work, see the [Domains reference guide](https://documentation.immuta.com/saas/configuration/domains.md). When you're ready to set up domains, see [Create and manage domains](https://documentation.immuta.com/saas/configuration/domains/configure-domains.md).

## Start with how your organization works

Most domain structures mirror an existing organizational structure, because the teams that already own a business area are usually the ones best positioned to govern its data. Before creating domains, look at how your organization is divided and where knowledge of the data sits:

* How is your business divided today: by product, function, region, or platform?
* What data does each team use and manage?
* Who knows each set of data well enough to make access decisions for it?
* Which data is naturally grouped by who accesses it and how?

The answers point you toward a domain model, and they also identify the people who will become your domain stewards.

## Choose a domain model

Most organizations base their domains on one of four models. Each one assigns governance to a different kind of team, so the best fit depends on where ownership of your data already sits.

| Model                      | Domains align to                                                                 | Consider this model when                                              |
| -------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Line of business**       | Business units or product lines, such as `Retail Banking` or `Insurance`         | Business units own their data and have different access requirements. |
| **Department or function** | Internal functions, such as `HR`, `Marketing`, or `Finance`                      | Governance responsibilities already sit with functional teams.        |
| **Region**                 | Geographic or regulatory boundaries, such as `North America` or `EMEA`           | Data is subject to jurisdiction-specific regulations, such as GDPR.   |
| **Data platform**          | Technologies or environments, such as `Snowflake`, `Databricks`, or `Production` | Platform teams manage governance and permissions for their platform.  |

For example, a pharmaceutical company running clinical trials in several countries might choose regional domains, such as `US Trials` and `EU Trials`, so that regional coordinators can author the masking and subscription policies each jurisdiction requires. A state government might instead choose departmental domains, such as `Transportation`, `Education`, and `Health`, because each department is accountable for its own records.

For step-by-step examples of how each model is configured, see the [Domains use cases](https://documentation.immuta.com/saas/configuration/domains.md#use-cases).

## Combine models where responsibilities overlap

You don't have to commit to a single model. A data source can belong to multiple domains at the same time, so you can layer models when different teams are responsible for different aspects of the same data.

For example, a data source with financial data from EU customers could belong to both a `Finance` domain and an `EU GDPR` domain. The finance team governs how the data is used internally, and the compliance team governs how it meets regulatory requirements. Policies from both domains apply to the data source, alongside any global policies. A retail bank could take a similar approach: central governance applies a global PCI masking policy to all data, while stewards of the `Retail`, `Corporate`, and `Wealth` domains each add subscription policies for their line of business.

When policies from multiple levels apply to the same data source, Immuta merges or resolves them according to the policy type. See [Designing domain policies](https://documentation.immuta.com/saas/configuration/domains.md#designing-domain-policies) for how global, domain, and local policies work together.

Overlapping domains also apply to identification. Because a domain's identifiers only run against the data sources in that domain, you can create one domain that contains all data sources for organization-wide identifiers, and separate business domains with identifiers specific to their data. See the [Data identification reference guide](https://documentation.immuta.com/saas/configuration/tags/data-discovery/data-identification-reference-guide.md) for details on how identifiers are evaluated.

## Plan the tags that define each domain

Once you know what each domain should contain, decide how data sources will get there. Data sources can be assigned to a domain manually or dynamically. Dynamic assignment uses tags and scales better, but it is only as reliable as the tags behind it, so plan your tags before you create your domains.

Hierarchical tags let you scope domains broadly or narrowly from the same tag structure. For example, with tags like `Region.NorthAmerica.US`, you can assign data sources to a `North America` domain using the parent tag and to a `US` domain using the child tag. Tags can come from users, from an external catalog, or from Immuta itself.

[Connection tags](https://documentation.immuta.com/saas/configuration/integrations/registering-a-connection/reference-guides/new-connections-reference-guide.md#tags) require the least upkeep. Immuta applies them automatically to every data source registered through a connection, based on where the table lives in your data platform, and object sync keeps them current. This makes them a good fit for platform or environment domains, or for domains that map to a specific database or schema.

## Decide who governs each domain

A domain structure is only as effective as the people responsible for it. Before you create domains, leadership and the users who will act as domain stewards should agree on what each domain covers and who is responsible for it. Document which decisions the central governance team keeps and which ones move to domain stewards.&#x20;

Grant each steward only the domain permissions that match their responsibilities. In the state government example, each department's stewards might only need the `Audit Activity` permission, which lets them use the domain's Audit tab to produce records for public records requests without also managing policies. For the full list of global and domain permissions, see Immuta users and permissions.

It also helps to have a clear data inventory before you start. Knowing what data you have and where your sensitive data is makes it easier to decide which domains need stricter policies and which identifiers each domain needs.

### Keep your structure current

Your domains need to change as your data and organization change. New data sources need the right tags to land in the right domain, so define who applies those tags when data is onboarded, or rely on connection tags where possible. Domain policies should be reviewed regularly to confirm they still reflect each domain's access requirements, and new stewards need to be introduced to their permissions and responsibilities.

Larger changes, such as a reorganization or a new data platform, are a good time to revisit the structure itself. Because dynamic assignment is driven by tags, you can often restructure domains by changing the tags they use rather than reassigning data sources one by one. To track changes to domains and their data sources over time, see the domain audit events.


---

# 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/designing-a-domain-structure.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.
