alderson59 opened a new issue #15632:
URL: https://github.com/apache/superset/issues/15632


   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 
https://github.com/apache/superset/pull/12680
   
   It is noted that [SIP-51] is closed via 
https://github.com/apache/superset/pull/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
   
   https://github.com/apache/superset/pull/12680#issuecomment-770337622
   > we plan in a follow-up PR that user will be given temporary read access to 
all of the datasets within a dashboard as was mentioned in the development 
milestones in #10408
   
   Is there an issue/PR for this yet? Please point me to it if there is already 
one! :)
   
   
   Use Case:
   - Create a user role that has read-only access to dashboards, without access 
to the individual records in the underlying data (i.e. nothing shows up on 
Datasets menu)
   - Successful implementation would look like this: a user role could be set 
to have ONLY access to Dashboards, and not any datasets in the menu, yet 
dashboard is still able to render charts without permission errors.
   - This limits the user to accessing only what is set up for them via the 
Dashboard.
   - Filtering access should still be available.
   
   
   As mentioned in 
https://github.com/apache/superset/issues/10408#issue-664324346
   > Airbnb and probably other orgs are fully dependent on dataset level access 
- they would not handle an extra dashboard level permission
   > In our org we will have hundreds of dashboards that will be based on the 
same dataset
   > Therefore there is no way to manage dashboard access for specific 
dashboards for specific users
   
   
   Related issues:
   [SIP-51]: https://github.com/apache/superset/issues/10408
   
   https://github.com/apache/superset/issues/11198
   https://github.com/apache/superset/issues/12910
   https://github.com/apache/superset/issues/1799
   https://github.com/apache/superset/issues/4127
   https://github.com/apache/superset/issues/14260
   etc.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to