Bug description
I have created on role with few of the role permission. referring that i am able to apply rls . But while opening the chart in designer mode i getting error:
even the url is not generating full: Role i Testing url is : {url}/explore/?viz_type=big_number_total&datasource=77__table
for admin: {url}/explore/?form_data_key=X5dLX9ezsyc&viz_type=big_number_total&datasource=77__table&datasource_id=77&datasource_type=table
Where as for that table i have given the access:
please confirm what exact permission i am missing
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] 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.
Comment From: dosubot[bot]
The incomplete URL and missing dataset access for your custom role are almost certainly due to missing granular permissions. For designer mode and chart exploration, the custom role needs explicit access to the dataset (datasource_access), the database (database_access), and the schema (schema_access). If any of these are missing, Superset's backend will not return the necessary dataset metadata, which leads to incomplete URLs and errors like missing dataset_id or slice_id parameters [source].
To resolve this, go to Security > Roles, edit your custom role, and ensure it has:
- datasource_access on the specific dataset,
- database_access on the relevant database,
- schema_access on the relevant schema (if your database supports schemas).
Also, recent changes added chart-level RBAC, so if you’re on the latest version, check if the chart itself has role restrictions [source].
If you’re still seeing issues after updating permissions, check the Superset backend logs for any SupersetSecurityException or permission-denied errors—these will tell you exactly which permission is missing. RLS rules can further restrict data but won’t substitute for these access permissions.
Once the correct permissions are in place, the explore URL and dataset access should work as expected.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
