-
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
Trying to set "Granular" permissions after "Block" is broken #17763
Labels
Administration/Permissions
Collection or Data permissions
Priority:P2
Average run of the mill bug
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Milestone
Comments
flamber
added
Administration/Permissions
Collection or Data permissions
Priority:P2
Average run of the mill bug
and removed
.Needs Triage
labels
Sep 4, 2021
Permissions are generally already difficult enough by themselves, so this can add a lot more confusion. Giving P2. |
@nemanjaglumac I think is entirely an FE thing, Reza just assigned it to me because it was block-permissions-related. Closing as fixed by #17757 |
Fixed by #17757 |
This was referenced Dec 13, 2022
Merged
This was referenced Jan 11, 2024
This was referenced Feb 5, 2024
Merged
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Administration/Permissions
Collection or Data permissions
Priority:P2
Average run of the mill bug
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Describe the bug
Trying to set "Granular" permissions after "Block" leads to a table view that is greyed out.
Logs
N/A
To Reproduce
Steps to reproduce the behavior:
/admin/permissions/data/database/1
(Permissions page for "Sample Dataset")Refreshing doesn't help.
The workaround is to click on the "Administrators" group in the left sidebar, and then to again click on the "All users" group. This time the page is editable, but it still displays "block".
Expected behavior
The page should be editable immediately and it probably makes more sense to default the sections to "no self-service".
Screenshots
Included above.
Information about your Metabase Installation:
local dev, `master, b4a41be, H2, sample dataset
Severity
Since there is a workaround, probably just P3. Would need to wait for an input from the product to figure out what the default permission level for granular tables should be.
The text was updated successfully, but these errors were encountered: