Predefined roles
Your workspace comes with a standard set of roles. These cover the most common responsibility levels and have sensible default permission sets:| Role | Summary |
|---|---|
| Super Admin | Full org access: settings, structure, members, broadcasts, rota, HR, hiring, finance, branding |
| Senior Manager | Broad broadcast, rota, and approval access across departments |
| Manager | Department-scoped broadcasts, rota management, and member approvals |
| Coordinator | Broadcast to their own department; view rota |
| Assistant | Draft broadcasts — requires Manager or above approval before sending |
| Weekly Paid Staff | Receive broadcasts; view own rota and calendar; manage subscriptions |
| Society or Club Leader | Broadcast to their society or club members only |
Custom roles
If the predefined roles do not map cleanly to your org’s structure, you can create custom roles with exactly the combination of permissions you need.Where to manage roles
All role management takes place at Admin → Roles (/admin/roles).
Creating a custom role
Go to Admin → Roles
Navigate to Admin → Roles (
/admin/roles) in the sidebar. You will see the list of all predefined and any previously created custom roles.Name the role
Give the role a clear, descriptive name that reflects the responsibility level it represents — for example, ‘Events Coordinator’ or ‘Finance Viewer’. This name is visible to admins when assigning roles to members.
Select permissions from the catalog
Browse the permission catalog and toggle on the keys this role should include. You can combine keys from different categories to build a precise permission set. See the Permission categories section below for an overview of available keys.
Permission categories
Permissions are organised into categories. Common examples include:| Category | What it controls |
|---|---|
members.view | View the member directory and individual profiles |
members.edit_roles | Assign and change roles for other members |
recruitment.* | Full access to the hiring hub, job listings, and pipeline |
org_admin | Access to Admin-level settings and configuration |
broadcasts | Compose, schedule, and send broadcasts |
rota | Create and manage rota shifts and approvals |
hr | Access to HR records, onboarding, and people data |
finance | Access to payroll, wagesheets, and finance settings |
compliance | Access to the compliance hub and gov monitor |
Per-member permission overrides
In addition to role-level permissions, you can add or remove specific permission keys for an individual member. This is useful when someone needs a single extra capability — or should have one removed — without warranting a whole new role. To manage a member’s individual permissions:- Go to Admin → Members (
/admin/members). - Select the member whose permissions you want to adjust.
- Open the Permissions tab on their profile.
- Add or remove specific permission keys as needed.
Permission overrides stack on top of the member’s assigned role. If you grant a key that is not in their role, they gain access to that feature. If you remove a key that their role includes, they lose access to it — regardless of the role assignment.
Assigning roles to members
To change a member’s role, go to Admin → Members (/admin/members), find the member in the list, and select Edit. Choose a role from the dropdown and save. The change takes effect immediately — the member’s navigation and available actions will update on their next page load.