You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:02:31 UTC
Re: [D] Restrict Report or Individual Page in Report based on user persona [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Restrict Report or Individual Page in Report based on user persona
<!-- Answer -->
Superset supports restricting access to entire dashboards and reports using role-based access control (RBAC) with the DASHBOARD_RBAC feature flag, so you can assign permissions to user groups for specific dashboards or charts [PR 30380](https://github.com/apache/superset/pull/30380). For data-level restrictions, row-level security (RLS) lets you filter data by user roles [schemas.py](https://github.com/apache/superset/blob/master/superset/row_level_security/schemas.py).
However, Superset does not currently support restricting access to individual dashboard tabs (pages) within a report based on user persona or roles. There is no built-in way to use a custom database table to dynamically control access at the page/tab level [issue 32060](https://github.com/apache/superset/issues/32060).
A common workaround is to split your report into multiple dashboards (e.g., one for the summary page, one for the detail page) and assign access to each dashboard according to user roles. For true page-level access control, custom development would be needed—this would require changes to both the frontend and backend, and likely a Superset Improvement Proposal (SIP).
For more details, see the discussion on dynamic tab selection and access control [issue 32060](https://github.com/apache/superset/issues/32060).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=252bcf5f-e877-4819-ade7-57bc771f49b0) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35533#discussioncomment-14607548
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org