Groups and access
Two questions: what and where
Section titled “Two questions: what and where”Every time someone opens a page in Roudiy, two questions decide what they get:
- What may they do? That is the role: view the map, review safety events, generate IFTA reports, manage users.
- For which part of the fleet? That is the group: Dallas North, Dallas South, or the entire company.
Keeping the two apart means you do not need a separate “Dallas North Dispatcher” role. You give the Dispatcher role and pick the Dallas North group.
What each role may see and do. System roles are fixed; duplicate one to start a custom role.
System roles come with Roudiy and cannot be changed:
| Role | Typical job | Default reach |
|---|---|---|
| Company Admin | Sets up the company, users, groups and settings. | Entire company |
| Dispatcher | Watches trucks, trips and live video. | Their groups |
| Safety Manager | Reviews safety events, coaches drivers, follows scores. | Their groups |
| Compliance Manager | Prepares IFTA reports and fuel purchases. | Their groups |
Custom roles are your own. Duplicate a system role, then add or remove permissions, for example a dispatcher role with fewer permissions. A company can have up to 50 custom roles. The full list of permissions per role is in Roles and permissions.
Sensitive permissions
Section titled “Sensitive permissions”Three permissions are marked Sensitive because they touch privacy or the hardware:
- video.driver_facing: see the driver-facing camera (CH2).
- devices.command.dangerous: send commands such as a reboot to a kit.
- safety.events.confidential: see events marked confidential.
Give them only to people who need them.
Groups and subgroups
Section titled “Groups and subgroups”Terminals or branches, nested up to 5 levels. They limit what dispatchers and safety managers see.
Groups usually mirror how your company is organised: a terminal, a region, a customer account. Vehicles and drivers belong to groups. Groups can contain subgroups, up to 5 levels deep.
- Your companyEntire company
- TexasLevel 1
- Dallas NorthLevel 2
- Dallas SouthLevel 2
A parent’s users also see its subgroups. Deleting a group does not delete anything else: Vehicles and drivers stay, only group membership is removed. Users whose only access was that group then see the whole company, so check their access after you delete a group.
Access rows: role + group
Section titled “Access rows: role + group”A user’s access is a list of access rows. Each row is one role in one group, or in Entire company. A permission in a row applies in that group and all its subgroups.
Examples:
| User | Access rows | Result |
|---|---|---|
| Owner | Company Admin · Entire company | Every Company Admin permission, in every group. |
| Dallas North dispatcher | Dispatcher · Dallas North | Sees and works only Dallas North trucks. |
| Regional safety lead | Safety Manager · Texas | Reviews events in Dallas North and Dallas South. |
| Two-hat user | Dispatcher · Dallas South, Safety Manager · Dallas North | Dispatches in South, reviews safety in North. |
Rules that keep access safe:
- A user has 1 to 20 access rows, and at least one of them uses a system role.
- The company always keeps a company-wide Company Admin. At least one active Company Admin is required.
- Some work needs company-wide access, for example only company-wide users can generate IFTA reports.
When changes take effect
Section titled “When changes take effect”Access changes apply to users on their next sign-in refresh (up to 15 minutes). If you remove someone’s access, plan for up to 15 minutes before it disappears from their screen. Deactivating a user works the same way: they are signed out, and access ends within 15 minutes on all services.
Users and invitations
Section titled “Users and invitations”People join by invitation. A user is Invited, Active or Deactivated. An invite is valid for 7 days; resending it cancels the old link. They sign in with their ELD platform account or set a password. Drivers are not users: they never sign in.