How do I configure roles and permissions for my workforce?
The RIVET platform has 5 permission options. Admin users can add or edit roles with any permission level, and change role names and colors.
The following default roles set at default permission levels:
|Default Role||Permission Level||Permission Description|
|Admin||Admin||Manage Organization with the ability to add staff users and all roles.|
|Scheduler||Scheduler||Create Jobs and Workers and assign/schedule workers to jobs.|
|Project Manager||Project Leader||View/edit all jobs they are assigned to, with the ability to add/edit/remove placeholder positions for their jobs.|
|N/A (Create new role)||Project Scheduler||View/edit all jobs they are assigned to, with the ability to add/edit/remove workers and placeholder positions for their jobs.|
|Foreman||Field Leader||Has access to: Assigned Job Pages and all job page features, plus the ability to update the job's status. Does not have the ability to view Job Start and End Dates without customization..|
|Worker||Worker||Has access to: See their own schedule, see assigned Job Pages with the Job Feed, and edit Job Tasks. Does not have the ability to post to Job Feed, view the Job End Date or view the Job Roster without customization.|
Roles have additional configurations related to jobs:
- Roles can be made schedulable, which enables worker with the role to be scheduled on jobs. This is the default for Field Leader and Worker roles.
- Roles can be included as default on all new jobs to make composing your standard Job Roster easier.
Can roles be deleted?
- All roles can be deleted except for the admin role.
- In order to delete a role, you must migrate all impacted workers and job assignments to a new role. This can be done right in the role manager as shown below:
The RIVET platform has 5 permission options. Admin users can add or edit roles with any permission level, and change role names and colors. Depending on the size of your organization, you may want to customize permission and roles to allow other team members more or less access.
Larger organizations tend to have more roles. The back office typically has more access to features in RIVET, however there is often a need for a customization to permissions. For example, if you would like the Safety Team to have access to Manage Org to input certifications, but you want to hide financials, custom permissions can be administered. Easily customize back office access by connecting with the CS team. The field also tends to have a worker permission that keeps them focused on the job schedule, location, and any communication that is job specific.
Mid-size organizations tend to configure their roles and permissions in a similar manner. Back office typically has more access within the tool whereas the field has access to their job and job details.
Small-sized organizations or divisions either configure their field with the worker role or they will allow more access. For example, if you would like the field to see or message the job roster this permission can easily be applied to override the default permission setting.