Roles and tiers
Understand who can do what and how plan tier affects available modules.
Roles decide what a user can do. Plan tier and feature controls decide which modules are available to the organization.
Access is effective only when all three checks pass:
- The user's role can open or change the feature.
- The organization's plan includes the parent feature or subfeature.
- The feature is enabled for the organization.
Roles
| Role | Best for | Typical access |
|---|---|---|
| Worker | Field employees | Worker dashboard, own timecards, certifications, toolbox talks, documents, messages, notifications, and time-off requests |
| PM | Project managers | Admin dashboard, job sites, certifications, compliance monitoring, toolbox talks, messages, pending approvals, and calendar when enabled |
| Superintendent | Field operations role, where enabled | PM-style access plus admin timecard list/detail visibility |
| Admin | Company operators | Full organization administration, workers, settings, reports, timecard management, PTO review, worker punch-in, and billing-sensitive operations |
| Dev | Site Secure operations | Internal support access, cross-organization diagnostics, dev admin portal, view switching, and test controls |
Give users the narrowest role that fits their job. Upgrade access only when the person needs the additional responsibility.
Plan tiers
Each tier inherits the tiers below it.
| Tier | Limits | Included parent modules |
|---|---|---|
| Minimal | 10 workers, 3 job sites, 3 certs per worker, 1 custom talk per month, basic push notifications | Timecards, certifications, toolbox talks, job sites, messages, phone auth, basic incident management |
| Essential | 25 workers, 5 job sites, unlimited certs and custom talks, standard push notifications | Minimal plus time off |
| Pro | 50 workers, 10 job sites, all push notifications |