mistercrunch opened a new issue #9576: [DISCUSS] chart and dashboard ownership
URL: https://github.com/apache/incubator-superset/issues/9576
 
 
   So currently, the security model assumes that each chart and each dashboard 
has one or many owners.
   
   Owners are the only people who can alter their objects, or expand the 
ownership of objects.
   
   Now dashboards are collections of charts, and when an owner wants to extend 
ownership to another person, we also grant ownership of the collection of 
charts in the dashboard. Every time a dashboard is saved, we make sure that all 
charts are owned by [at least] all the owners of the dashboard. 
   
   The idea is that it's confusing and unintuitive to own a dashboard, be able 
to change the layout, but not be able to change the charts. 
   
   ### Related shortcomings / thoughts
   * when saving a chart and adding it to the dashboard in the "save" modal, 
the ownership is not extended to that dashboard's owner. Note that typically 
the person will go and alter the layout and save the dashboard, which solves 
that issue. If we change that to fit the model, people might not understand the 
ownership implications of "adding to dashboard"
   * when people alter a chart, they might not know that this chart is in any 
or multiple dashboards, and can alter things beyond of their intended scope
   
   <img width="848" alt="Screen Shot 2020-04-17 at 4 40 43 PM" 
src="https://user-images.githubusercontent.com/487433/79621965-38a04c80-80ca-11ea-8d7e-a7534363f083.png";>
   
   
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

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

Reply via email to