Roles

​

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 You can assign these predefined roles directly to members without any additional configuration.

​

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. Click ‘New role’ Select New role to open the role creation form. 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. Choose a badge colour Pick a colour for the role chip shown in Admin → Users (All members). You can change or clear it later when editing the role. 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. Save and assign to members Save the role. It will immediately appear in the role selection list when editing a member’s profile. Go to Admin → Users , select a member, and assign the new role from their profile.

​

Archiving a role

Open a role from Admin → Roles and choose Archive role.

• If nobody is assigned, confirm archive. The role leaves the active list and can no longer be assigned.
• If people are still on that role, choose a replacement role first. Campsite moves them, then archives the old role. Their access updates to the replacement role’s permissions.
• Org admin cannot be archived. Other unused system roles (for example CFO) can be archived by an organisation admin when they are not needed.

Archiving is soft delete: the role is hidden from day-to-day assignment, not hard-deleted from history.

​

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 The full catalog of available permission keys is visible in the role creation and edit form within Admin → Roles.

​

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:

1. Go to Admin → Users (/admin/users).
2. Select the member whose permissions you want to adjust.
3. Under Adjust this person’s permissions, review the checkboxes. Permissions already included in their assigned role appear selected and labelled as included in the role. Changing the role in the editor updates that preview before you save.
4. Use Give extra access or Restrict access for exceptions on top of the role.

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. Organisation admins keep full effective access through the org admin role (and related admin gates). Role permission checkboxes on Admin → Roles should reflect that broad grant set.

​

Assigning roles to members

To change a member’s role, go to Admin → Users (/admin/users), 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.

​

How permissions shape the sidebar

The sidebar only lists pages the member can actually open. Sections such as Admin, HR, Manager, and Finance appear when the member holds at least one permission for that area, and each link inside a section is shown only to members whose permissions allow that page. If a link is missing, grant the matching permission key on the member’s role or as an individual override.