-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restricting and unrestricting access to a table results in the DB-level permission still being "Granular" #20436
Comments
Seems like this is the same as #16253, closing in favor of that |
@alxnddr This is actually a backend bug (i.e. it should be replacing the individual permission paths for each table with a general one for the DB). As far as I can tell, the frontend will do the right thing when the backend is fixed. |
…in the DB-level permission still being "Granular" #20504
@alxnddr I take it back, this does seem to be a frontend issue. On the second request, the frontend is sending a graph that looks like this (in part):
It should be sending a graph that looks like this, if it knows that all tables have unrestricted access:
|
Describe the bug
If you restrict data access to a single table in a database, and then change it back to unrestricted, the data access level in the UI for the entire database will display as "Granular" even though access to all the tables is unrestricted.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Data access to the DB should go back to 'Unrestricted'
Information about your Metabase Installation:
Current master
Severity
Minor, but probably blocking some work for an upcoming project so serious in that regard.
The text was updated successfully, but these errors were encountered: