- Issue created by @TolstoyDotCom
- π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
I also wonder if we could do some route lookups and list paths the permission would grant you access to
- π³πΏNew Zealand quietone
@tolstoydotcom, I think this is a duplicate of #1765576: Redesign Permissions Page β . Can you confirm?
- πΊπΈUnited States TolstoyDotCom L.A.
The two issues are related, but I don't think this is a duplicate: the other issue is about how to present the info, this issue is about giving more info. As with art, I know what UX I like but I can't draw a crooked line so I'm perfectly willing to let others handle that aspect of things. No matter what it ends up looking like, the permissions page is going to need more info if anyone expects regular users to use it. Regular users are going to need much more detailed explanations of what various things do.
And, there needs to be some sort of structure rather than confronting them with dozens of permissions from one module. Field UI has 28 permissions and Node has 42. That's going to overwhelm people and dividing the permissions into sections would make it easier for newer users. One of the node permissions is "Bypass content access control"; regular users aren't going to understand what that means, the side-effects, etc etc without a detailed explanation and examples.
In that case I think this issue needs a title update to more clearly indicate its scope. Additionally, you should comment at #1765576: Redesign Permissions Page β to alert the followers of that issue of the existence of this issue.