Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

What it is

A Role is a named bundle of permissions assigned to a User. Tread ships with five core roles: Admin, Dispatcher, Foreman, Driver, and Ticket Approver. Each Role decides what the User sees, edits, and acts on across web and mobile.

Why it matters

Roles protect the data that should not leak. The biggest is rate visibility — Drivers must never see Customer billing rates. Get that wrong once and trust with the customer is gone.

How Tread models it

RolePrimary surfaceSees
AdminWebEverything in their Company
DispatcherWebOrders, drivers, equipment, no payables/receivables by default
ForemanWeb + mobileTheir jobs, their drivers, ticket approvals
DriverMobileTheir assignments, their tickets, no rates
Ticket ApproverWebApproval queues, no settlement controls
  • Permissions — fine-grained toggles inside each Role. Settle Receivables, edit Rates, view Customer info, approve Timesheets.
  • Scope — Roles can be scoped to a Department, Site, or Project. A Foreman on Site A does not see Site B.
  • Custom Roles — Admins can create new Roles for billing leads, owners, or specialized approvers.

Rate Visibility Matrix

Drivers do see their own pay rate. They do not see customer rates. This is a common misconception — Admins sometimes lock down the Driver Role too tight, then drivers can’t confirm their pay on a load.
RoleCustomer rateDriver-pay rate (own)Vendor-pay rateFuel surcharge schedule
AdminYesYes (all drivers)YesYes
DispatcherOptional toggleOptional toggleOptional toggleYes
ForemanNoNoNoNo
DriverNeverYes — own onlyNoNo
Ticket ApproverYesYes (all drivers)YesYes
  • Driver-pay rate (own) — the driver sees their own per-load or per-hour rate on each assignment. They never see another driver’s rate or the customer’s billing rate.
  • Customer rate — only the Roles that need to bill or quote should see this. Default to no for new custom roles.
  • Optional toggle — the permission is off by default; an Admin can enable it per role.

Common pitfalls

Drivers must never see customer billing rates. A national hauler had a rate-visibility leak where customer pricing surfaced on a driver-facing screen. The feature was pulled the same day and the trust hit lasted longer than the fix. Before go-live, log in as a Driver test user and walk every screen. If you see a customer rate, the Role is wrong.
Don’t strip the driver’s own pay rate to “be safe.” Drivers expect to see what they earn per load. Removing it generates support tickets and erodes trust. The fix is targeted: gate customer rates, keep driver-pay-self visible.
Spin up a test User per Role before go-live. Log in as each one and confirm what shows up. Five minutes here saves a customer-trust incident later.