Roles and Permissions
Every team member has exactly one role. Roles form a hierarchy — each role includes the access of the roles below it, plus more.
| Role | Level | Can also do everything a… |
|---|---|---|
| Owner | 4 (highest) | Administrator, Dispatcher, and Employee can do |
| Administrator | 3 | Dispatcher and Employee can do |
| Dispatcher | 2 | Employee can do |
| Employee | 1 | — |
This is why documentation for other modules (Jobs, Customers, Materials, and so on) usually only talks about “Dispatchers” and “Employees” — Owners and Administrators are always treated as Dispatchers for the purposes of what records they can see, on top of their team-management privileges described below.
What each role can do
Section titled “What each role can do”| Capability | Owner | Administrator | Dispatcher | Employee |
|---|---|---|---|---|
| View jobs, customers, assets, materials, etc. across the whole team | Yes | Yes | Yes | Only their own records |
| Create and edit operational records (jobs, customers, materials, etc.) | Yes | Yes | Yes | Own records only |
| View the team’s members and pending invitations | Yes | Yes | Yes | Yes |
| Invite new members | Yes | Yes | No | No |
| Resend or cancel a pending invitation | Yes | Yes | No | No |
| Change another member’s role | Yes | Yes (with limits, see below) | No | No |
| Remove another member from the team | Yes | Yes (with limits, see below) | No | No |
| Leave the team themselves | No (Owner can’t be removed) | Yes | Yes | Yes |
| Edit the team name or currency | Yes | No (view only) | No | No |
| Delete the team account | Yes | No | No | No |
Assigning roles
Section titled “Assigning roles”When inviting someone or changing an existing member’s role, the choices you’re offered depend on your own role:
- Owner can assign any role — Administrator, Dispatcher, or Employee.
- Administrator can only assign a role below their own level — Dispatcher or Employee. An Administrator cannot promote someone to Administrator or Owner.
- Nobody can make someone an Owner through an invitation or role change. Ownership only happens by creating the team in the first place.
Removing and editing members
Section titled “Removing and editing members”Only Owners and Administrators can edit another member’s role or remove another member from the team. A few extra rules protect the team from being left without leadership:
- You can’t edit your own role. Members can view their own membership details but must ask another Administrator or the Owner to change their role.
- You can always remove yourself (leave the team), regardless of your role.
- The Owner can never be removed from the team, by anyone, including themselves through this screen.
- An Administrator can only edit or remove members at a lower level than themselves — an Administrator cannot change or remove another Administrator’s role. Only the Owner can do that.
- The last Administrator is protected. If there’s exactly one Administrator and no Owner able to step in, that Administrator can’t be removed or demoted — someone else must be made an Administrator first.
When a member is removed (by someone else, not by leaving voluntarily), they receive a deactivation email letting them know their access has ended, along with contact information for the account Owner.
Owner-only actions
Section titled “Owner-only actions”A handful of actions are restricted to the Owner specifically, even Administrators can’t do them:
- Renaming the team or changing its currency
- Deleting the team account entirely
A note on visibility vs. team management
Section titled “A note on visibility vs. team management”The Dispatcher/Employee distinction described in other chapters (Jobs, Customers, Materials, Assets, and so on) is about visibility of operational records — which jobs or customers someone can see and edit. It’s separate from team management — inviting people, changing roles, and removing members — which is limited to Administrators and the Owner regardless of whether someone is a Dispatcher or Employee.