7 permissions "RowLevelSecurityFiltersModelView" don't exist but documentation mentions them

[xavier-GitHub76]

Bug description

7 permissions "RowLevelSecurityFiltersModelView" don't exist in Superset 4.0.2
but documentation mentions them.

https://github.com/apache/superset/blob/master/RESOURCES/STANDARD_ROLES.md

Screenshots/recordings

No response

Superset version

4.0.2

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.

[dosubot]

The discrepancy you're observing between the documentation and the actual implementation of permissions for RowLevelSecurityFiltersModelView in Superset 4.0.2 might be due to a few reasons. The RowLevelSecurityFiltersModelView is implemented as RLSRestApi in the codebase, and it includes permissions for CRUD operations and other functionalities ^[1]. However, the permissions matrix in the STANDARD_ROLES.md file might not have been updated to reflect the current state of the codebase.

Additionally, the RowLevelSecurityFiltersModelView is listed under ADMIN_ONLY_VIEW_MENUS, indicating that its permissions are intended for admin users only ^[2]. This could explain why certain permissions are not available to other roles as mentioned in the documentation.

If the permissions are indeed missing, it could be an oversight in the documentation or a feature that hasn't been implemented yet. It might be helpful to check the test suite for RowLevelSecurityFiltersModelView to verify the expected behavior and permissions ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[rusackas]

Indeed, that markdown file was an earnest attempt at being correct at the time, but is almost certainly in need of updating/maintenance. Whilst we wait to have versioned documentation (it's coming!) do we have any volunteers to update the docs with a PR?

[xavier-GitHub76]

PR is created
#33670