Reference

Groups

Every permission group in your agency at a glance — the four built-in groups, the ones you have made, and how to create a new group from scratch, a template or a clone.

A group is a named bundle of permissions. People belong to groups, and what someone can do is the combination of everything their groups grant. Open the list from Organization → People & access → Groups; the tab appears for people with Manage groups. Select a card to open the group, where you change its permissions and members.

Groups are how you give access — not the role field on a person's profile, which is a display hint only. See how access works for the model.

The group cards

Each card shows:

the group's colour and name, with a System badge on the four built-in groups;
its description, or "No description";
how many members it has and how many permissions it grants;
a Default badge on the group people join when an invitation or access code names no group (normally Operator).

The built-in groups

Every agency starts with four system groups:

Group	What it is for
Operator	No permissions. Members read published guidance in the operator app. The usual group for access-code joiners.
Author	Create content, edit it, and submit it for review.
Reviewer	Everything Author has, plus publishing, second approval, unpublishing, deleting content and managing taxonomy.
Admin	Every permission, including managing users, groups, settings, branding, billing and access codes.

A system group's name and permissions are locked: the database refuses to rename it, change what it grants, or delete it. If you need a variation — say, reviewers who cannot delete — clone the system group and change the copy. Open a group to see exactly what it grants in your agency.

Create a group

New group at the top right appears for people with Manage groups; the database refuses to create a group for anyone else. It opens a dialog with:

Field	What it does
Name	Required — Create group stays disabled until it has one.
Description	Optional; shown on the card.
Start from a template	Read-only Reviewer (Publish and Unpublish), Contributor (Create content and Edit content) or Taxonomy Editor (Manage taxonomy). A template replaces the current ticks; Clear unticks everything.
The permission checklist	Every permission, sorted into Content, Taxonomy and Administration, each with a line saying what it allows.

A template is only a starting set of ticks. The Read-only Reviewer template ticks Publish and Unpublish alone, but publishing and unpublishing also need Edit content to take effect (see Permissions) — tick it too, or make sure the group's members get it from another group.

Select Create group. A confirmation naming the group appears and its card joins the list, with no members yet. Add people from the group's Members tab, from a person's page, or in bulk from Users (opens the admin console).

Clone a group

On any group's page, Clone opens the same dialog already filled in: the name with "copy" added, the description, and the group's permissions. Change what you need and select Create group. Only the permissions are copied — the new group starts with no members. Cloning a system group is the way to get an editable version of it. Because of the rule above, a clone of Admin keeps its permissions only if you hold every one of them.

States

While the groups load, grey placeholder cards appear. If the list cannot be loaded, a red message above it gives the reason. The list is never empty: the four built-in groups always exist.