Config Access and Permissions

Config access controls which data source configs each user can work with. This determines what data connections they can create and, by extension, which widgets and dashboards they can see.

Required role: Admin

How access works

• Admins have access to all configs automatically. No grants needed.
• Members can only use configs that an admin explicitly grants them.
• View-Only users can view artifacts but don't create connections, so config access doesn't apply to them directly. However, they can only see widgets and dashboards built with configs that are accessible to the organization.

Granting access

1. Go to Organization Settings → Users tab.
2. Find the member you want to configure.
3. Check the data source configs they should have access to.
4. Save.

The member can now create data connections that use those configs.

Cascading visibility

Access cascades through the data model:

1. Data connections — A member can only see connections that use configs they have access to.
2. Widgets — A member can only see widgets whose data connections are all accessible to them. If a widget uses even one inaccessible connection, the entire widget is hidden.
3. Dashboards — A member can only see dashboards whose widgets are all accessible. If a dashboard contains even one inaccessible widget, the entire dashboard is hidden.

This means granting access to a config automatically opens up all the connections, widgets, and dashboards that use it.

Removing access

Uncheck a config from a member's access list. They'll immediately lose visibility of any connections, widgets, and dashboards that depend solely on that config.

Tips

• When a new member joins, grant them access to the configs they need right away. Without access, they'll see an empty platform.
• If a member reports they can't see a widget or dashboard, check that they have access to all the configs used by that artifact's data connections.
• The Observatory is a good place to check which configs a connection uses.