-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implicit Datasource Access for Dashboard RBAC #15632
Comments
Pretty sure this is implemented already. Have you tried enabling the feature flag |
You can find all the PRs related to this feature here: https://github.com/apache/superset/pulls?q=is%3Apr++dashboard_rbac |
Yes , this is implemented as mentioned here |
Thank you, that works like a charm! Also, what are the minimum required permissions for this to work without the access to explore other datasets or edit the charts? Tried Gamma, but that's more perms than needed. Before I close, can I ask where is the best, latest source of documentation for superset? I'd prefer referring to that in future, instead of trawling through the issue section or opening a ticket here unnecessarily :) Can this |
Documentation for this feature can be found here: https://superset.apache.org/docs/creating-charts-dashboards/first-dashboard#manage-access-to-dashboards info about the various feature flags can be found here: https://github.com/apache/superset/blob/master/RESOURCES/FEATURE_FLAGS.md |
Unfortunately, this feature breaks my dataset-based access. I can either use dashboard level OR dataset level. I've ran a db upgrade after setting the FF as well. What went wrong? (I am on 1.4.1) |
Same here! I cannot have dataset level and dashboard level. I got a Forbidden Access if both are set up |
Hi all, I have done some reading on Dashboard Access Control and I can conclude from what I gather, that Dashboard access can now be automatically added to roles based on what you set in the UI, courtesy of #12680
It is noted that [SIP-51] is closed via #12680, addressing half of the issue.
However, this does not yet address the datasource/dataset access control with respect to Dashboard Access. I found this comment by @amitmiran137
#12680 (comment)
Is there an issue/PR for this yet? Please point me to it if there is already one! :)
Use Case:
As mentioned in #10408 (comment)
Related issues:
[SIP-51]: #10408
#11198
#12910
#1799
#4127
#14260
etc.
The text was updated successfully, but these errors were encountered: