hscabral opened a new issue, #30839: URL: https://github.com/apache/superset/issues/30839
### Bug description There is a scenario here that seems to be a permission bug. I have **one** Database connection, where I have **multiple schemas**. The schemas are identical in structure, but differ in data, of course. I create Gamma users, and I create Gamma roles for different schemas. **Gamma_A** and **Gamma_B**, let's say. The only permission for each of these roles is `schema access on [DB].[db_conn].[schema_A]`, etc. In my use case, I need these Gamma users with access to SQL Lab. In it, the single schema assigned to the Gamma_A role is the only one that shows in the schema dropdown - this is correct. However, in the SQL query window, **if I change the schema name in my SQL, I'm able to access the tables in other schemas**. Example: `SELECT * FROM schema_a.projects` and `SELECT * from schema_b.projects` work equally. This Gamma user, however, only was assigned schema access on schema_a. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.10 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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]
