What it is
A Role is a named bundle of permissions assigned to a User. Each Role decides what the User sees, edits, and acts on across web and mobile. One user can hold several roles at once. Their access is the sum of everything those roles grant. Tread ships with eight operational roles and four specialty roles. The biggest risk a role protects against is rate visibility — a field user sharing customer billing rates is a trust problem you cannot undo, so pick the right role up front.Roles at a glance
Permission matrix
“Yes” means the role has the permission by default.
* Foreman and Driver rate visibility is limited. See the next section.
Some companies run with Foreman approvals, job edits, or site creation switched off. If a Foreman is missing a “Yes” from this table, ask your implementation lead whether it’s disabled for your account.
Specialty roles
Stack these on top of another role when needed.Rate visibility
A dedicatedview_rate permission controls rate access. Tread enforces it on the server. Users without it get no rate values in any response, and rate fields stay hidden on web and mobile.
- Drivers see their own pay rate. Customer rates stay hidden from them. Do not strip the driver rate to be safe; drivers expect to see what they earn.
- Foremen see the hauler rate so they can manage trucking in the field. Nothing else.
- Dispatcher rate visibility is always on. There is no per-company toggle. If a person must not see rates, use a role without rate access.
Choosing a role
Common pitfalls
Related
- Connected Ecosystem: how Roles map across Customer, Vendor, and Driver
- Rates, Add-Ons & Fuel: how rates work
- Onboarding: Users: step-by-step User and Role setup