Roles and permissions
Every membership in an organization carries a set of roles that determines which console modules you see and which actions you can take in them. This page collects the canonical names for every operational role — every later page in this documentation links back here when it describes who a module is for.
Who this is for
Mainly organization administrators who assign roles to new and existing members, and anyone who wants to understand why their console shows the modules it does.
Operational roles
- Driver — completes vehicle inspections (DVIR), sees their own route and jobs, logs fuel and expenses, checks their own hours of service and safety score, and messages dispatch. Sees only their own data.
- Technician — works the service-order queue and parts, sees fault-code context, and documents repairs with photos and a sign-off.
- Dispatcher — the live map, route planning and optimization, assigning jobs to drivers, messaging drivers, and trip visibility.
- Safety manager — reviews safety events, manages scores and driver coaching, runs reward programs, and assembles incident packages.
- Compliance officer — oversees driver hours of service and tachograph data, reviews violations, handles IFTA, and keeps the compliance calendar and audit exports.
- Maintenance manager — preventive-maintenance schedules, work orders, parts and inventory, purchase orders, and the shop/vendor network.
- Finance controller — total cost of ownership, fuel and energy spend with fraud detection, reports and exports, subscription and billing.
- Fleet manager — broad read/write access across assets, drivers, maintenance, fuel, and dashboards — the widest operational role, a step short of an organization administrator.
- Executive — org-wide dashboards, KPIs, and ESG, read-only, with no edit access.
- Organization administrator — organization settings, sites and groups, users and memberships, integrations, API clients, billing, and data export/residency.
Roles combine — a single user can hold several at once under the same membership (a small carrier owner, for example, might be a fleet manager, finance controller, and organization administrator all at once), and their set of roles can differ between the organizations they belong to.
How roles shape module visibility
A role decides both whether a module appears in navigation and which actions are available inside it. A dispatcher, for example, sees and works the dispatch module, while a compliance officer focuses on the compliance module — neither necessarily gets edit access outside their own area. The driver role carries an extra restriction to their own records (a driver sees only their own inspections and routes, for instance) — the technician role has no such restriction and sees the shop's full work-order queue, not just jobs assigned to them.
A separate role is the platform administrator — it operates outside any organization, supports and maintains the Transpira platform itself, and isn't part of any single membership. This is a rare role for the team running the platform, not for fleet users.
Behind the scenes
Whoever creates a new organization automatically receives the organization administrator and fleet manager roles. Every invitation creates a membership with the roles the inviter chose, and every role change is written to an audit log.
A second, independent dimension of access is location scope — see Sites and scoping: a role decides what you can do, while site scope decides where (which branches or depots).