Superset DB roles access filters #35635
-
I configured role and granted access to 2 datasets. They appear in DB. Query I used: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The query you used checks row-level security filter associations, but Superset's actual dataset access for roles is managed through PermissionView and ViewMenu tables, which link roles to dataset permissions. After you remove access to a dataset for a role, you should confirm that the relevant PermissionView entries (and their associations in ab_permission_view_role) for that dataset and role are deleted—this is what truly removes access in the database. Your query may show outdated results if row-level security filter records weren't cleaned up or if they're not directly tied to permission removal. For accurate verification, check that the role no longer has a datasource_access PermissionView for the dataset in question, and that there are no ab_permission_view_role links between the role and that PermissionView. More details on this mechanism are in the Superset security manager code here. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
The query you used checks row-level security filter associations, but Superset's actual dataset access for roles is managed through PermissionView and ViewMenu tables, which link roles to dataset permissions. After you remove access to a dataset for a role, you should confirm that the relevant PermissionView entries (and their associations in ab_permission_view_role) for that dataset and role are deleted—this is what truly removes access in the database. Your query may show outdated results if row-level security filter records weren't cleaned up or if they're not directly tied to permission removal. For accurate verification, check that the role no longer has a datasource_access Permissi…