GitHub user dosubot[bot] added a comment to the discussion: How read only user will add native filters in dashboard
<!-- Answer --> In Superset, the ability to add native filters to a dashboard is controlled by whether the user has edit permissions on that dashboard. This is managed by the `dash_edit_perm` flag, which is set to true for users who can edit the dashboard. By default, only dashboard owners or users with roles that grant dashboard edit permissions will have this flag enabled, and thus see the option to add or modify native filters. There is no separate, granular permission specifically for adding native filters—this action is tied to the broader dashboard edit permission. If your READ_USER role does not have edit access to the dashboard (i.e., is not an owner or does not have the "can edit" permission for dashboards), they will not be able to add native filters. The UI for editing filters is hidden for users without this permission, as determined by the `dash_edit_perm` flag in the dashboard state ([source](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/index.tsx), [source](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/nativeFilters/FilterCard/FilterCard.test.tsx)). To allow READ_USER to add native filters, you would need to grant them edit permissions on the dashboard. This typically means making them dashboard owners or assigning them a role with the "can edit" dashboard permission. There is currently no way to allow a user to add native filters without also giving them broader edit rights to the dashboard. If you want READ_USER to have this capability, review your custom role's permissions and consider adding the dashboard edit permission or making them dashboard owners. There is no single permission that enables only native filter editing without full dashboard edit rights. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/473b6a82-dd25-4540-b8af-9489471b4947?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/33598) GitHub link: https://github.com/apache/superset/discussions/33598#discussioncomment-13292939 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
