Company Admin: your first week
As the Company Admin you set Roudiy up for everyone else. Do it in the order below: each step uses what the one before it created. Groups come before invites, because most invites are tied to a group. Vehicles come before kits, because a kit is paired with a vehicle. Most companies finish the list in a few sittings during the first week.
-
Sign in and secure your account
Sign in at app.roudiy.com with your ELD platform account. Right after accepting your invitation you land on Company profile. Later, opening app.roudiy.com opens Company profile while your company is in onboarding and the Dashboard after that; signing in on the sign-in page directly opens Fleet View. You can always reach the profile through Settings → Company profile. Your account can change everything in the company, so turn on two-step verification: open the account menu (your initials, top right) → Security and click Enable. From your next sign-in, Roudiy asks for a 6-digit code sent to your email.
-
Fill in the company profile and time zone
Go to Settings → Company profile and check the company name, USDOT and MC numbers, address and home terminal time zone. The time zone matters more than it looks: safety scores are calculated every Monday in the company time zone, and until it is set the Scores page shows Set the company time zone to enable weekly scores. Reports, exported files and IFTA days also use it.
-
Create groups
Groups are your terminals or branches, for example Dallas North and Dallas South, nested up to 5 levels. They limit what dispatchers and safety managers see, so a dispatcher in Dallas North sees only Dallas North trucks. People in a parent group also see its subgroups. You can put vehicles and drivers in groups now or when you add them.
-
Invite your team
Invite each colleague with a role and a group, or Entire company. The invitation is valid for 7 days; they sign in with their ELD platform account or set a password. Give compliance managers Entire company access, because only company-wide users can generate the IFTA report. Access changes reach a user within 15 minutes, and the company always keeps at least one active Company Admin.
-
Create custom roles, if you need them
The four system roles are fixed. If someone needs a mix, duplicate a system role and change it. For example, the Dispatcher role cannot take camera snapshots; a “Dispatcher + snapshots” custom role can. Permissions marked Sensitive, such as driver-facing video, deserve a second look before you grant them.
-
Add vehicles and drivers
Add each truck with its Unit # (for example TRK-101), VIN and plate. Fill in GVWR and Axles: a truck over 26,000 lb or with 3 or more axles is IFTA-qualified, and a truck without these values shows Missing GVWR/axles and is left out of IFTA. Then add drivers with name, phone, CDL number and license state. Drivers do not sign in to the dashboard; you add them so trips, events and scores are linked to a person. For a large fleet, import both lists from CSV.
Add a vehicle · Import vehicles · Add a driver · Import drivers
-
Check the kits in Device Hub
Kits are installed by Roudiy, and the installer pairs each kit with its truck. Open Fleet → Device Hub and check that every kit is Active, shows the right vehicle and has green camera chips. If a kit is paired with the wrong truck, unpair it and use Pair to vehicle; only vehicles without a kit are listed. While a kit is unpaired, no new GPS data is recorded for that vehicle.
-
Assign drivers to vehicles
Open a truck in Fleet View and, on the Live tab, click Assign driver. A truck has one driver at a time and a driver has one truck. Without a driver, trips and events are recorded as unassigned and do not count in any driver’s score, so assign before the trucks roll.
-
Decide on camera and privacy
Go to Settings → Camera & privacy. Choose which roles may see driver-facing (CH2) video, or hide it for everyone; Company Admins always see it. Choose whether saved videos record audio (new videos only) and which cameras upload video for each event type. Tell your drivers what you decided.
-
Review the safety settings
Settings → Safety decides which ADAS and DMS events the cameras detect for the whole fleet. Agree on it with your safety manager: too many event types flood the Inbox, too few miss real risk. For different settings on some trucks, use AI profiles.
-
Review the default alert rules and add your own
Two rules exist from the start; you can edit or switch them off, but not delete them: Critical and high severity safety events (to Company Admins and Safety Managers, in-app and email) and Kit offline for 24 hours (to Company Admins, in-app and email). Add rules for what else your team must hear about, such as phone-call events for Safety Managers. Company Admins and Dispatchers already get an in-app notice for every new fault code, without a rule. Each recipient gets alerts only for the groups they can see.
-
Show the team the Fleet Dashboard
Walk your team through the sidebar, the notification bell and the page each role works in most: Fleet View for dispatchers, the Safety Inbox for safety managers, IFTA for compliance managers. Then send each of them the path for their role.