Assets Access Control

On any database, schema, or dashboard folder, admins can now manage who can access it in Catalog by leveraging the "Manage access" interface:

Tables access control

1. Navigate to your database/schema page through the left menu

   
2. Click on the top right corner button "Manage access"

   

3. Then select the teams that should have access to the dataset

Dashboards access control

1. Navigate to your dashboard folder page through the left menu

2. Click on the top right corner button "Manage access"

3. Then select the teams that should have access to this folder and its subfolders

How does it work

Set the teams that should have access to the tables/dashboards in this dataset or folder. Then any user needs to be in at least one of those teams to be able to see and access the dataset and its tables.

For instance, any member of HR or Sales team can access this dataset's tables:

By default, any new dataset/folder is accessible to anyone in the company. When a dataset/folder access is given to only a few teams, any new asset in this perimeter will inherit the access parameters.

Hierarchical datasets interaction

Admins can define access rights at different levels in their stack, for instance at database and schema level.

The behavior is the following:

• By default a child dataset (a schema here) will inherit the parent configuration -> Sales team is the only one to be able to see the database assets, the child schema inherits it:

  
• You can then choose to modify this configuration which will override the database access rights. Here all the members of the frontend team and the sales team will access the assets in the schema. ⚠️They won't be able to consult other schema's assets because of the database level restriction.

  

• You can also completely remove the inherited team from the schema access rights, which will hide its assets from this team. For instance here:

  • The Frontend team will see the schema's assets but nothing else from this database.

  • The Sales team (that is the only one to have access to this database's asset) will be blind to this given schema's assets but will see all the other database's assets