Page History
| Multiexcerpt | ||
|---|---|---|
| ||
A role is a function a user performs either in the management of Magnolia or as a visitor of a Magnolia website. It reflects the actions and activities assigned to, required or expected of a user. Specific permissions are granted to enable the functions of a role. For example, the editor role is responsible for editing content displayed on the site. Permissions granted to this role allow the user to edit the content and submit it for review. The publisher role, on the other hand, is tasked with reviewing the content and publishing it from the author instance to the public instance(s). Roles have JCR Access Control Lists (ACLs) and Web access permissions. For both the JCR content and Web access you can define multiple ACLs per role. |
Access to resources is controlled by the roles set up in the Security app.
| Info |
|---|
Roles are also used when configuring App permissions. |
...
Web access
With the Web access tab, you can define URL permissions for access to every Magnolia resource. One ACL grants access to a path for Get or Get & Post or to Deny access. Typically, you need to at least deny the anonymous role access to AdminCentral.
...
On a public instance, deny the anonymous role access to AdminCentral and any members-only sections of the site.
| Info |
|---|
To configure web access for a new user with an
|
Site-aware ACLs
The Enterprise Edition allows you to manage multiple websites in a single Magnolia instance. You can control cross-site access in two ways:
...
Overview
Content Tools