Skip to main content
Domains help you organize your data assets by letting people see only the data they should care about. Domains can be set to fit existing definitions (e.g., using metadata from dbt, SQLMesh, or Coalesce Transform), or can have custom definitions built with the UI drop-down menu. Quickly filter down key data assets by domain to see what matters to you. Members of your workspace can only see data that belongs to domains they’re in, helping you keep things simple as you scale. title

​
Setting up a Domain

  1. Navigate to Settings → Domains and click Create
  2. Give your Domain a name and a description title
  3. Click the newly created domain and select data assets that belong to the domain. This can be Data Products or individual data assets title
  4. Add members to the domain by clicking Add Member. These members will belong to the domain and be able to see all the data assets you selected above. The member must already exist in the workspace for you to be able to add them. title

​
Working with subdomains

Subdomains are helpful if you have larger domains (e.g., Marketing) with clearly distinguishable areas (e.g., performance marketing, brand marketing). To set up one or more subdomains:
  1. Navigate to a domain
  2. Click Add sub-domain
  3. Name your subdomain, and select relevant assets and members.

​
Member roles in domains

  • Admin users can toggle between all domains, as well as see data across domains using the default ALL domain selector.
  • All other user roles will only see data for domains they belong to. Read more about user roles. In cases where no domain has been set, all users will be able to see all data.
You can select a member in the workspace, and click the three dots to set a domain as their default, which will make it their default data access each time they open the platform.

​
How does the domain impact access to data

Domains provide a limited view into the data ecosystem for a user. While the limits are intended to help them focus on the data they are interested in, they will still be able to access any data asset, including the lineage in and out of their domain of interest. Domains are not meant to implement data access controls. We recommend that these controls should be put directly in your data storage (e.g., your data warehouse).