Data Domains

Dataedo Data Domains help you organize your data assets according to technical structure and IT management perspectives, mirroring how your data infrastructure is actually built and maintained. This section presents practical use cases of Data Domains, demonstrating the benefits of this technically-focused approach to data asset organization.

Access

Data Domains are represented with a circular icon, to help differentiate them from Business Domains. You can find them by navigating to the Data Governance>Domains section of Dataedo.

Use cases

Imagine your organization has multiple ETL pipelines. Each pipeline handles a distinct set of source systems and transformations. By creating Data Domains for each pipeline — such as "Customer Data Pipeline," "Transaction Data Pipeline," and "Product Data Pipeline" — your data engineering team can easily manage and document the assets that belong to each technical workflow. New engineers joining the team can quickly understand the data flow and dependencies by exploring these organized, pipeline-specific domains.

Partial permissions for external vendors

Now imagine you've engaged an external data integration vendor to build and maintain a specific ETL pipeline that loads third-party data into your warehouse. You want to give them access to the pipeline components they've built, while restricting access to sensitive internal assets in other parts of your infrastructure.

A good solution would be creating an Area within a Data Domain where only the technical assets related to that vendor's pipeline are linked. If the vendor was given access to that Area, they would be able to view and modify only the objects linked to that Area and its children, but would not be able to access other elements in your Data Domain. This protects your core data infrastructure while enabling the vendor to perform their contracted work.