Organization

Users & Roles

Users can be created within the platform to give people access to vehicles, groups, and applications within the system. Users are always created with an email address and you have the option once you create them to send an email with instructions for how they can log in.

Roles is a new feature that simplifies user management by allowing administrators to create templates for user roles, making it easy to assign consistent access and permissions. This helps ease the management of multiple users across the platform.

Key Features

Customizable Templates Tailor roles to fit specific organizational needs.
Efficient User Management Save time by quickly assign users to roles, reducing manual efforts
Role Consistency Ensure uniform access and permissions across users.
Integration with the System You can use roles within the platform for triggers actions and report scheduling.

Setup and Configuration

To access the roles feature, navigate to the Organization section under "Users & Roles", create a new User.

Enter a first name and last name and under the "Access" option select "Role" (Note that the email address is automatically generated for roles based on the first and last name.

Configure the scopes and gateway functionalities or features for that role.

Finally, you can go back to the INFO section and select the users that will have this role applied.

Now any change you make to that role for the scopes or features will be reflected on all the users for that role.

Additional Notes

Users can belong to multiple roles, with the most permissive scope prevailing, in other words if a user belongs to two roles and one of them has the permission to create geofences but the other one doesn't the user will be allowed to create geofences.
A user can be assigned to a maximum of ten roles.

Devices

Segment Setup

Segment configuration is required to record an entity’s cycles. Each segment represents a single state—either working or resting. The working segment reflects active time within the cycle, while the resting segment represents downtime.

A work cycle corresponds to the entity’s workday and typically consists of two segments: one working segment and one resting segment.

The Hours of Service (segment setup) has the following parameters:

Maximum Working Time: The maximum number of hours an entity can work within a cycle. If this limit is exceeded, the entity is considered overworked and the cycle becomes invalid. Example: If the maximum working time is 8 hours, any work beyond 8 hours invalidates the cycle.
Minimum Rest Time: The minimum continuous rest required to create a rest segment. Once this threshold is met, the system ends the work segment and begins a rest segment starting from the time rest began. Example: If set to 4 hours, a vehicle that remains off or motionless (based on the configured signal) for at least 4 hours will trigger a rest segment.
Maximum Continuous Working: Time The maximum time an entity can work without interruption during a cycle. Exceeding this limit marks the entity as overworked and invalidates the cycle. Example: If set to 2 hours, working continuously beyond 2 hours without a break will invalidate the cycle.
Minimum Break Time: The minimum duration of rest required to qualify as a break. Example: If set to 0.25 hours, the entity must rest for at least 15 minutes for the period to be considered a valid break.
Enable Work Cycle Analysis Using Driving Time Only: Excludes break periods from work cycle calculations. Violations (overwork alerts) are based solely on active driving time, while breaks are still recorded for reference and analysis.
Partition Signal: Defines the signal used to determine when the entity is working or resting. Options include:
- moving: The vehicle is considered moving when its speed exceeds 3 mph and a valid GPS position is available.
- ignition: Indicates whether the vehicle is turned on or off.