You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have multiple database connections available on Superset, and we would like the option to not restrict using a particular Database connection for datasets as that could inevitably lead to charts and dashboards this flooding our db.
We would like users to only be able to see that Db connection in sqllab for some adhoc queries here and there.
I found a similar discussion titled "Rbac on Databases for Datasets" which is currently unsolved. You can view it here[1].
Regarding your question, Superset allows you to configure database connection visibility for specific user roles or groups. You can achieve this by creating custom roles and assigning permissions to those roles for specific databases. This way, users with these roles will only see the database connections they have access to in SQL Lab. You can manage these permissions through the roles and permissions settings in Superset [2].
Hi Team,
We have multiple database connections available on Superset, and we would like the option to not restrict using a particular Database connection for datasets as that could inevitably lead to charts and dashboards this flooding our db.
We would like users to only be able to see that Db connection in sqllab for some adhoc queries here and there.
Is there some way this can be done already?
Originally posted by @lordicecream in #32248
The text was updated successfully, but these errors were encountered: