Roles and permissions

Custom roles, the permission matrix, geographic scope and recipient caps.

Open Settings › Roles to see every role in your organisation, its permissions and who holds it.

Built-in and custom roles#

Built-in roles (Owner, Campaign manager, Communications officer, Regional coordinator, Finance officer, Volunteer, Polling agent, Read-only analyst) are read-only. To tailor access, choose Create custom role:

1. Give the role a clear name, for example "Ward comms".
2. Tick permissions in the permission matrix. You can only grant permissions you already hold.
3. Set Maximum recipients per send without approval.
4. Give a reason and save.

You can later archive a role, restore it, or delete an archived role that nobody uses.

Permissions are granular#

Permissions are specific actions, for example sending, approving sends, building audiences, replying in the inbox, viewing reports, exporting reports or managing users. Combine only what the job needs.

Two permissions do not exist in any campaign role: revealing raw contact details and exporting raw contact details. Supporters' numbers stay sealed whatever role someone has.

Geographic scope comes from the assignment#

A role says what someone can do; their assignment in Settings › Users says where. The same "Ward comms" role can be given to one person for Ward A and another for Ward B, and each sees only their own ward.

Recipient caps#

The recipient cap on a role is the largest send that person can release without approval. Above it, a colleague with approval permission must release the send. This works alongside your organisation's approval policy; whichever is stricter applies.