Roles and permissions in detail
How capability-based access works, and what each role can and cannot reach.
- Written for
- Administrators
- Reading time
- 1 min
- Last reviewed
- August 2, 2026
Every action in the platform is gated on a named capability, and a role is a fixed bundle of capabilities. The interface hides what your capabilities do not cover, and the API refuses it independently — so a link shared between colleagues does not become a way around a permission.
Areas capabilities are grouped into
- Trips and scheduling — viewing, creating, assigning, cancelling.
- Dispatch — the live board, reassignment, messaging.
- Drivers and vehicles — roster and fleet management.
- Inspections and maintenance — checklists and defects.
- Billing — payers, rates, claim generation, reconciliation.
- Events — camera and safety event review.
- Organization — profile, policy, users and roles.
Choosing between dispatcher and admin
Dispatchers can run the entire operating day. What they cannot do is change the rules the day runs under — cancellation and completion policy, rate tables, user roles. If someone needs to change those, they need admin; if they only need to run the day, they do not.
Related
Understanding the four roles
Getting started · 1 min · AdministratorsTenant admin, dispatcher, driver and mechanic — what each one is for, and how to choose.
Inviting and deactivating users
Account & organization · 1 min · AdministratorsAdding colleagues, changing a role, and the right way to handle someone leaving.