[GitHub] [incubator-superset] mistercrunch commented on issue #7961: Dashboard Security

[GitBox <gi...@apache.org>]

mistercrunch commented on issue #7961: Dashboard Security
URL: https://github.com/apache/incubator-superset/issues/7961#issuecomment-519364682
 
 
   Per-dashboard permissions is likely to get implemented in the future, meaning you could have access to a certain dashboard, but not to the underlying datasource(s), and couldn't go and "explore" deeper from the dashboard.
   
   It's also likely that we'll implement row-level security in the future, which would force certain predicates (aka filters) based on perms.
   
   The reason why it is the way it is currently is:
   * we wanted a [somewhat] simple security model
   * we wanted users to be able to drill in or explore deeper and answer their own questions as a core flow
   
   Currently all perms (datasource, database, schema) are implemented as different types of FAB (flask app builder) permissions that can be composed into FAB roles.  In the future, we *may* want to overload FAB roles to have to many-to-many relationships to these other models, to get a more comprehensive / structured roles management form.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org