Users and content access
Administrators manage accounts in Users and editorial permissions in Content Access.
Create or maintain an account
- Open Users and select New user.
- Enter the requested account details and choose a role.
- Save and arrange email verification and secure credential delivery.
- Configure content access before asking the user to work on entries.
Use Edit user to change account details or role. Password actions include Reset password and Send password reset email. Manage sessions lists sessions; Revoke sessions removes active sessions. Ban prevents sign-in and Unban permits it again. Review selection carefully before bulk actions or deleting accounts.
Choose a role
| Role | Intended responsibility |
|---|---|
| Administrator | System configuration, user/access management, and emergency workflow actions |
| Content creator | Author content and submit drafts for review |
| Approver | Review and approve others' content |
| Publisher | Publish, withdraw, and schedule content |
| Managing editor | Review and publish without administrator configuration privileges |
Strict workflow still prevents self-approval. A role change can invalidate pending schedules. See review and publication.
Grant content access
- Open Content Access.
- Select the user, group, or content-type view appropriate to your change.
- Set type permissions to No access, View, or Edit; use Inherit to remove a direct user setting.
- Maintain group membership and any required entry exceptions.
- Save and check the displayed Effective access and its source.
Permission resolution for non-administrators follows this order:
- A direct entry setting, including an explicit denial.
- A direct user setting for the content type.
- The combined grants of the user's groups.
- No access when nothing grants it.
Edit includes viewing. A direct No access can override group access; Inherit allows fallback. An entry exception can make one entry visible even without broad type access. Administrators have system-level access independent of these editorial grants.
For an Articles team, create a group, add the intended editors, and grant Edit on Articles. Use direct exceptions only when necessary, then verify access with a representative non-administrator account.
The system group Existing Content Access preserves access during initialization for existing installations. Inspect its memberships and grants rather than assuming new accounts or new types automatically inherit them.