Team Settings: custom roles

Last updated: June 17, 2026

Roles (Settings → Team → Roles) are saved permission configurations assignable to members. Built-in Admin = Access Everything (cannot be modified). + New Role: name + permissions (same groups/scopes as per-user: All/Assigned/Yes/No, Direct Sales + School permissions). Assign at creation or via pencil edit; override per user afterward.

Roles are saved permission configurations you can assign to team members, so you don't have to set every permission individually for each person.

How to access

Settings → Team, then scroll to the Roles list.

Built-in Admin role

Every account has an Admin role ("Access Everything"). It grants full access and cannot be modified.

Create a role

  1. In the Roles list, click + New Role.
  2. Enter a Role name.
  3. Set the permissions for the role (see below).
  4. Click Save.

To edit or delete a custom role later, hover over it in the Roles list and use the pencil or bin icon.

Setting permissions

The role editor uses the same permission options as an individual team member. Permissions are grouped by area — agency-side under Direct Sales (Students, Bookings, Proposals, Invoices, Sales, Schools, Reporting, Payments, Settings, Agency Connections, Inventory, inviting users) and school-side under School permissions (Agency Portal, Enrollments, School Connections, Inventory, Offerings, School Insights).

Each permission is set with a scope:

  • All — all records in that area.
  • Assigned — only records assigned to the member.
  • Yes — allowed (for permissions that aren't record-based).
  • No — not allowed.

Assign a role

  • Assign at team member creation (when adding the new user).
  • Reassign anytime: hover over the team member, click the pencil icon, and change the Role.
  • After assigning a role, you can still override individual permissions for that one person on their Edit Team Member screen.

Why roles help

Different team members need different access — for example, counselors with full student access but no admin settings, finance staff with payments and reports, or junior staff with limited create and edit. A role captures one of these patterns once, so you can apply it to many users instead of configuring each person by hand.