-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Tailor Permissions get grouped by name and not by parent navigation #5804
Comments
This is an interesting use case. We may need to add |
I don't so much need the blueprints to share a single permission, I just need to be able to identify them. At the moment, one has to give a user the permission, log in as them and check if the one selected is the right one. In the screenshotted example it would be much more obvious if tags are listed under the heading |
Ok, based on this:
|
I have multiple tailor items named
Tag
. These are all grouped together in the permissions backend, even though they have differentuuid
,handle
andnavigation.parent
options set.Shouldn't the permission be grouped by the name of the parent item?
The text was updated successfully, but these errors were encountered: