Understanding the four roles
Tenant admin, dispatcher, driver and mechanic — what each one is for, and how to choose.
- Written for
- Administrators
- Reading time
- 1 min
- Last reviewed
- July 21, 2026
Access is capability-based. A role is a named bundle of capabilities, and every screen and action in the Console is gated on a specific capability rather than on a job title, which is what keeps permissions consistent between the interface and the API underneath it.
| Role | Typically | Carries |
|---|---|---|
| Tenant admin | Owner, operations manager | Everything in the organization, including users, billing and policy settings |
| Dispatcher | Dispatch and scheduling staff | Trips, scheduling, the live board, drivers, vehicles and messaging — but not organization settings or billing configuration |
| Driver | Field staff | Their own assigned work, through the driver app rather than the Console |
| Mechanic | Shop and maintenance staff | Vehicles, inspections and defects, without access to trips or billing |
Choosing a role for a new user
Give the narrowest role that covers the person's actual work. Tenant admin is not a seniority marker — it carries the ability to change billing configuration and operational policy for the whole organization, so it belongs with the small number of people who genuinely need those.
Related
Roles and permissions in detail
Account & organization · 1 min · AdministratorsHow capability-based access works, and what each role can and cannot reach.
Inviting and deactivating users
Account & organization · 1 min · AdministratorsAdding colleagues, changing a role, and the right way to handle someone leaving.