Replace existing permission methods with human readable aliases
What does this MR do?
Replaces existing permission methods with human readable aliases
Are there points in the code the reviewer needs to double check?
no
Why was this MR needed?
described in the subject
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the style guides -
Branch has no merge conflicts with master
(if you do - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #20944 (closed)