-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: Add meta data to roles and privileges #2162
Comments
@bwaidelich, would love to read your thoughts on this. |
I think it's a great idea without top much risk involved! |
I second that assessment by Bastian :) That makes so much sense and should be painless to implement! |
If implanted I suggest them being used/displayed in a cli context/command. Can we make that? |
bwaidelich
added a commit
that referenced
this issue
Dec 14, 2020
This builds upon the work started with #2166 and * Fixes the Policy schema * Adds label & description to the "magic" base roles * Adds CLI commands in order to make use of the metadata within Flow Usage: ./flow security:listRoles --include-abstract ./flow security:describeRole Neos.Flow:Everybody Related: #2162
Merged
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When lots of roles (targeting lots of privileges) are defined, managing them and assigning them to users in the Neos backend gets quite complicated and error prone. The major issue is, that we only have the role identifier (somehow truncated) to be displayed in the backend module.
Having two additional (optional) configuration options, label and description for both configuration types would make things much clearer.
Example:
The result in Neos could be something like this, when clicking on the ℹ️ icon:
The text was updated successfully, but these errors were encountered: