> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Domain

> How to use Domains and Sub-domains to organize data assets by business area and assign accountability in Prizm.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Domain",
            "description": "How to use Domains and Sub-domains to organize data assets by business area and assign accountability in Prizm.",
            "url": "https://docs.dqlabs.ai/architecture/semantics/domain",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

A **Domain** represents a top-level business area — Finance, Sales, Customer, Human Resources, Supply Chain. Domains set the accountability boundary: they determine who owns data quality SLAs, who stewards assets, and how quality scores are grouped across the platform.

**Sub-domains** refine ownership within a domain. Finance might contain sub-domains for Accounts Receivable, Accounts Payable, and FP\&A — each with its own steward and quality targets.

## Cardinality rules

| Entity                 | Domain assignment                                                                                        |
| ---------------------- | -------------------------------------------------------------------------------------------------------- |
| **Asset (table/view)** | 0–1 domain — the area where it *lives or serves value*                                                   |
| **Attribute (column)** | 0–1 domain — can differ from the table's domain; represents where the *meaning* of that field originates |
| **Data Product**       | Exactly 1 owning domain                                                                                  |
| **Application**        | 0–many domains (with relationship type: owner \| contributor \| consumer)                                |

A single table can have a different domain than some of its attributes. For example, `customer_orders` lives in the **Sales** domain, but its `customer_id` attribute belongs to the **Customer** domain, and `payment_status` belongs to **Finance** — because stewardship of each field's meaning comes from a different team.

## How to create a Domain

<Steps>
  <Step title="Navigate to Semantics → Domain">
    Click **Semantics** in the top navigation bar, then select **Domain**.
  </Step>

  <Step title="Add a Domain or Sub-domain">
    Click **+ Add Domain** to create a top-level domain, or select an existing domain and click **+ Add Sub-domain** to nest one underneath it.

    <Frame>
      <img src="https://mintcdn.com/dqlabs/Qsn1uj9FNsBus5LS/images/image-110.png?fit=max&auto=format&n=Qsn1uj9FNsBus5LS&q=85&s=92b3178c5067065543f3e39f8163defe" alt="Image" width="2488" height="1204" data-path="images/image-110.png" />
    </Frame>
  </Step>

  <Step title="Fill in the details">
    | Field           | Required | Notes                                                              |
    | --------------- | -------- | ------------------------------------------------------------------ |
    | **Name**        | Yes      | Use the business area name as it appears in your org               |
    | **Type**        | Yes      | Domain or Sub-domain                                               |
    | **Description** | No       | What this area covers and who it serves                            |
    | **Owner**       | No       | The team or individual accountable for data quality in this domain |
  </Step>

  <Step title="Save">
    Click **Save**. The domain appears in the list and is immediately available as a facet in the Asset catalog.
  </Step>
</Steps>

## Domain list

The Domain page shows all domains and sub-domains with:

| Column     | Description                                                 |
| ---------- | ----------------------------------------------------------- |
| **Name**   | Domain or sub-domain name                                   |
| **Type**   | Domain or Sub-domain                                        |
| **Score**  | Average data quality score across all assets in this domain |
| **Alert**  | Number of active alerts on assets in this domain            |
| **Issue**  | Number of open issues on assets in this domain              |
| **Action** | Edit or delete                                              |

## Assigning a domain to an asset

Open any asset's detail page → right-side panel → **Domain** field → search and select. A domain can also be assigned in bulk from the Asset catalog using the multi-select action menu.

## Use cases

**Quality accountability by business area** — view average quality scores grouped by domain on the Quality Score page. Identify which business area has the most degraded data and assign the right steward.

**Scoped access control** — grant a team access to all assets in the Finance domain without listing every table individually. Domain membership drives RBAC resource scoping.

**Impact analysis** — when a pipeline fails, filter Issues by domain to see which business area is affected and notify the right owner.

**Sub-domain granularity** — large domains like Finance often need distinct ownership per function. Sub-domains (Accounts Receivable, FP\&A) let each sub-team own their slice while rolling up scores to the parent domain.

<Tip>
  Use the Asset catalog's Domain filter to audit which assets have no domain assigned — these are the most likely to be unowned and under-monitored.
</Tip>