Users and permissions

For account admins: who can sign in, and what they can do on each website.

Adding users

Go to Account → Users → New user and enter their name, email and a starting password.
Choose Account admin for full control, or Standard user for permission-based access.
For standard users, open Access to give roles and permissions.

Roles and permissions

Roles are presets (Editor, Author, Viewer) given on all websites or on one website.
Individual permissions are a grid of module × action (e.g. Posts × Publish), each set to inherit, allow or deny, per website. A deny always wins.
The actions are view, create, edit, delete, publish, approve and manage.

Bugs and ideas

Platform super admins decide who can read and send bug reports and ideas: tick Can use feedback when editing a user. Users who have it show a Feedback badge in the users list. Account admins don't see this setting. See Getting started for how reporting works.

Welcome email

Platform super admins can email a new user their sign-in details: Send welcome email on the user's page, on their access page or in the users list. You see the email first and can add a personal note. It contains the sign-in link, their email address and a new temporary password, asks them to change it and to turn on two-factor authentication, and explains bug reports if they can use feedback. Passwords are never stored, so sending makes a new temporary password: any password set before stops working and the user is signed out everywhere. You can send it again at any time; the user's page shows when it was last sent.

Modules

Each website can switch features on or off (Account → Websites → Modules): posts, pages, navigation, events, FAQ and more. A switched-off module disappears from the admin and its API stops answering, without deleting anything.

Package limits

Your package sets limits on websites, users, storage, monthly API requests and custom content types. When a limit is reached you'll see a message, and can ask to upgrade.