Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
Magnolia 5.4.9+. The Permissions app is deprecated. The functionality has been moved to the Security app.
The Permissions app tells you what groups and roles are assigned to a given user. The app is useful for permission reporting, auditing and troubleshooting why a user cannot access the resources they should. You can access the app at Tools > Permissions.
The Permissions app is a 4.5 legacy app installed by the UI AdminCentral module. The Tools app group that this app belongs to is only available to the superuser
role. This is configured in the app launcher layout. The app is configured at Configuration > /modules/ui-admincentral/apps/permissions
.
Node name |
---|
modules |
ui-admincentral |
apps |
permissions |
The Permissions app queries the users
, usergroups
and userroles
workspaces. It does not store any content, just reads existing nodes.
Efficient security control can be complex:
The Permissions app allows you to see a complete list of all roles and permissions in one place.
To use the app:
Example: The Permissions app reports the permissions of the demo-project-editor
role in the website
workspace as follows:
Role: demo-project-editor Read/Write permission in the workspace website with path /demo-project Read/Write permission in the workspace website with path /demo-project/* Read only permission in the workspace website with path /$ Read only permission in the workspace website with path /$/*
These permissions are granted using ACLs. Below you see how ACLs are granted in the Security app. The two ACLs granted to the demo-project-editor
role are in fact stored as four rules in the repository. Each rule is translated into one or more regular expression patterns. This is why the Permissions app reports four permissions.
The app also reports Web access permissions. You can see them as uri
workspace in the report.