Skip to main content

Data Domains Overview

Data Domains provide an organizational layer above individual data products, enabling domain-level ownership, governance tracking, and cross-space portfolio management. They let you group related assets by business function — such as "Sales", "Finance", or "Customer" — regardless of which space hosts them.

Why Data Domains?​

Spaces provide isolation, but real-world data ownership cuts across spaces. A Chief Data Officer needs to see all "Finance" data in one place, assign accountability to a domain leader, and measure governance health across the portfolio. Data Domains make this possible.

Benefits include:

  • Clear accountability — Every domain has an owner responsible for its governance posture
  • Portfolio management — See all products in a domain across spaces, with governance metrics
  • Approval routing — Domain owners are automatically suggested as approvers for access requests to their domain's assets
  • Hierarchical organization — Nest sub-domains under parent domains for fine-grained structure

Key Concepts​

Domains​

A Data Domain is an organization-level entity representing a business function. Each domain has a name, description, optional icon, and a designated owner.

Ownership​

The Domain Owner is the primary accountable person. Owners appear as suggested approvers for access requests to products within the domain. Ownership can be transferred at any time.

Stewards​

Stewards are additional team members who help manage the domain. They can be assigned the owner or steward role. Unlike the primary owner, stewards can be added or removed without affecting the domain's core accountability.

Product Assignment​

Products are assigned to domains via a many-to-many relationship. A single product can belong to multiple domains, and a domain can contain products from different spaces. This cross-space capability is key for portfolio views.

Domain Hierarchy​

Domains support parent–child relationships, allowing you to organize a top-level "Finance" domain with sub-domains like "Accounts Payable", "Treasury", and "Tax". The hierarchy is exposed via a tree endpoint for client-side rendering.

Getting Started​