Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
You can control app access by specifying a role. Members of the role can see the app in the launcher and can start the app. With this mechanism you can provision an entire group of apps in one go or individual apps. You should provision apps only to users who actually need them. This ensures that the app launcher stays clean and users find apps quickly.
Here is a comparison what
editor roles see in the app launcher. The editor role only sees apps that are necessary for his work.
To grant permission to app group:
permissionsnode under the group in the app launcher layout.
Example: The Tools group is provisioned to the
superuser role only.
If the role doesn't exist, create it first in the Security app. If you need a role just for the purpose of provisioning apps, an "empty" role is enough. The role does not need any ACLs or permissions to site URLs. To grant additional users access, assign them to the role. You can add as many role properties as you need.
Advanced example: Use voters to include and exclude groups in a flexible way. The
info.magnolia.voting.voters.RoleBaseVoter class checks if the current user has access permissions by comparing user roles and configured roles. The configured roles can be allowed or denied.
This example denies (
not=true) permission to the
travel-demo-admincentral role. This saves the effort of listing all roles that are permitted.
To grant permission to an app:
permissionsnode under the app descriptor.
Example: The Groovy app is provisioned to the
scripter role only.
Action availability is the lowest level of app access you can configure by role. Actions define what a user can do with the app.
You can configure action availability at two levels:
Action availability is provided by ConfiguredAvailabilityDefinition . The node names are different from those used in granting permissions to apps and app groups.
In this example the Publish deletion action is granted only to