The Samsara Driver App is commonly used by drivers but can also be used by non-driving workers, such as safety supervisors, equipment operators, and field workers. Since these non-driving workers are not drivers, they do not use driver-related features like vehicle selection or Hours of Service (HOS).
To customize the Connected Workflows experience within the Samsara Driver App for non-driving workers, you can hide driver-specific features, also known as Worker Mode, and display only the Forms and Training tiles on on their app home screen. This creates a better user experience for the non-driving worker.
To hide driver features for a non-driving worker, perform the following workflow:
-
Assign a Forms license to the non-driving worker.
-
Select the Settings icon (
) at the bottom of your Fleet menu to view dashboard settings.
-
Select Driver > Add a driver.
If the user already exists in the driver list, select the more actions ( ••• ) menu, then click Edit.
-
Select Hide driving-related features in the Driver App.
-
Save your changes.
There are two ways that you can apply the setting to hide driver features for multiple non-driving users.
From the Samsara dashboard, you can add the Hide Driving Features option in bulk for users through a CSV file by performing the Add or Edit Drivers in Bulk workflow. When defining your user, ensure you include the Has Driving Features Hidden field. For more information on the Has Driving Features Hidden field, see CSV Format for Drivers in Manage Driver Accounts.
You can also add the Hide Driving Features option for users in bulk through the Samsara API. You can use the POST /fleet/drivers endpoint to create new drivers or workers, or the PATCH /fleet/drivers endpoint to update existing drivers or workers. For each endpoint, there is a boolean body parameter of HasDrivingFeaturesHidden which can be set to TRUE or FALSE. If you set the parameter to TRUE, it will hide driving related features. If the field is left blank, it will default to FALSE on the POST endpoint, and will not make any changes on the PATCH endpoint.
Comments
0 comments
Article is closed for comments.