can read on Row Level Security / can read on RowLevelSecurity

[xavier-GitHub76]

Bug description

There are 2 permissions:

• can read on Row Level Security
• can read on RowLevelSecurity

I haven't tested whether the 2 are useful, but 'can read on RowLevelSecurity' could be replaced by 'can read on Row Level Security'.

So permissions for Row Level Security could be :

• menu access on Security
• menu access on Row Level Security
• can read on Row Level Security
• can write on Row Level Security

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.

[dosubot]

There is a functional difference between the two permissions: 'can read on RowLevelSecurity' is tied to the UI view, while 'can read on Row Level Security' is used for the API. This separation allows for distinct permission policies for UI and API access, so replacing one with the other could unintentionally change access controls. This kind of naming inconsistency has caused issues in other parts of Superset before, especially during upgrades, and usually requires careful migration if you want to unify them source. If you want to consolidate these permissions, you’ll need to consider both the UI and API use cases and ensure proper migration to avoid breaking access for users source.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[rusackas]

We suspect both are indeed needed... to consolidate these would be a breaking change and require a migration. We could consider this for the next major release.