Rbac on Databases for Datasets

[lordicecream]

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?

[dosubot[bot]]

Hello @lordicecream! I'm here to assist you with any bugs, questions, or contributions. Let's tackle this together!

I found a similar unsolved discussion titled "Give users database access but restrict the dashboards, charts and datasets they see" which might be relevant to your query ^[1].

Regarding your question, Apache Superset differentiates between permissions for SQL Lab access and dataset creation through specific permission sets. SQL Lab access is controlled by permissions like can_execute_sql_query and can_get_results, while dataset creation involves permissions managed through the dataset_after_insert method. This separation allows for configuring roles that can access SQL Lab without necessarily having access to create datasets ^[2][3].

However, I couldn't find specific configurations or examples in the Superset documentation that demonstrate restricting dataset creation while allowing SQL Lab access. You might need to customize the security manager to implement this specific access control requirement.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report}