MihailGershkovich commented on issue #2148:
URL: 
https://github.com/apache/incubator-superset/issues/2148#issuecomment-633149315


   We are just starting to use superset, and I hope I will be able to promote 
it in our company.
   Probably my request is already resolved and I was just not able to find how 
to approach it, but in case it is not:
   
   Sorry for another comment on a closed request, but do you plan to implement 
it for other DBMS aswell? I'd like to see this feature for postgres, so that we 
can leverage features like access rights on tables, row and column level 
security or policies. It would be even nicer, if something like "set role" 
would work.
   Example: we limit the access to transactional data based on role membership 
(including inherited). Imagine, I belong to roles x, y, z and y is member of z. 
And we have a head of department y, and an analyst in department z, which 
belongs to y.
   Then I can see transactional data and build statistics on all of them. 
However if I want to share my dashboards with head of department y and analyst 
of department z, I will have to copy them over and setup connections or build 
filtered dashboards for them. Otherwise they would see to much info (they would 
have access to confidential information and receive wrong statistics).
   Now imagine head of department y wants to see stats and data for department 
z (he is allowed to), thus he would have to worry about his filters, etc. or he 
would need to have access to another set of dashboards, instead of changing his 
roles.
   BR


----------------------------------------------------------------
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]



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

Reply via email to