You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/11/29 16:34:32 UTC

[GitHub] [superset] rusackas commented on issue #22236: feature req - no sharing of database connections

rusackas commented on issue #22236:
URL: https://github.com/apache/superset/issues/22236#issuecomment-1330926134

   This isn't a typical flow, but I think I understand your desire. Essentially, you're sharing a Superset instance, but not sharing any of the database connections. This means there would be no collaboration with shared datasets, dashboards, charts, alerts/reports, etc. On the one hand, this vastly reduces the collaborative intent of Superset, but on the other hand, I can see some valid use cases to let people work independently with private information. 
   
   Do you think you would want people to be able to override this, and enable other individuals to share databases (or datasets) with other users, or do you want this to be some sort of permanent-lock where access would be completely barred to others (e.g. a "private" checkbox in the datasource modal)?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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