andy-clapson commented on issue #29171: URL: https://github.com/apache/superset/issues/29171#issuecomment-2542105632
> About the current state of things and whether it needs clearer documentation, doing a bit more thinking, I think today, for someone to use SQL Lab they **need access to the database connection**, which implies that they have access to everything inside that database connection. Now it's possible for someone to give access to a db connection and define schema-level AND dataset-level access, which I believe is disregarded since the database-access-level permission overrides that. Very much my $0.02 here. Docs could always be better for everything, everywhere, of course. But IMO it feels weird to spend time/effort expanding Superset's features to include controls for a SQL IDE, which is really just a user connecting to a DB, and up to the DBA and whatever permissions model is implemented at the organization. Feels outside the scope of a bi tool, certainly. I always thought of SQLLab as "cool, there is an IDE here I can use, that's nice to have". If the use case was to allow certain users ONLY access to existing Superset datasets, that would make a bit more sense. -- 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]
