User Permission Guide
User permissions give you control over who can access, edit, and manage important information in your organization. Setting the right roles ensures data accuracy, stronger security, and smoother collaboration across your team.
System Roles
Administrator
Description | Manage all organization data, settings, and users. |
Who should this be | Typically a company champion or senior leader who is accountable for the overall relationship with OnStation. |
Tip: Keep this limited to one or two people at most.
User Manager
Description |
Allow users within that group to manage all users, groups, licenses, and trainings within the organization. |
Who should this be | HR staff, office admins, or team leads handling onboarding. |
Note: User managers can continue to make other groups, but will not be allowed to make other groups with administrative permissions.
Project Manager
Description | Can manage organization projects, project submissions, and tags. |
Who should this be | Field or office project managers. CEIs or supervisors who monitor project progress. Ideal for those coordinating multiple crews or reporting back to the DOT. |
Integration Manager
Description | Can manage organizations’ integrations. |
Who should this be |
IT staff or tech-savvy project engineers. Anyone responsible for connecting OnStation to tools like Trimble, FleetWatcher, or HCSS |
Data Manager
Description | Will be managing organization forms, flags, and location data. |
Who should this be | Quality control staff, inspectors, or engineers. Team members responsible for data integrity, documentation, and reporting. |
Safety Manager
Description | Can manage the organization's safety features, like Active Worksite™. |
Who should this be | Safety coordinators, superintendents, or site foremen. Ideal for those responsible for worker safety and traffic control on the jobsite. |
User Roles
-
Form Reader – allows users to read forms only.
-
Form Writer – allows users to create, edit, and save forms.
-
Location Data Reader – allows users to read material density and density test data.
Warning: The user permissions will only be inherited based on that user's license type.
Note: A data license is still necessary to manage the data for the organization within the portal.
Best Practices for Assigning Permission Classes
- Limit Administrators. Keep this role to a small number of trusted individuals.
- Pair classes when needed. For example, a Project Manager may also be a Data Manager if they handle documentation.
- Review regularly. As people change roles or leave the organization, check that permission classes are still aligned.
- Plan for redundancy.