How to Configure Driver Profiles in Samsara
Quick Summary
A driver profile is more than a name and a login. It stores license details, Hours of Service exemptions, carrier information, and app permissions that determine what a driver can see and do once they open the Samsara Driver App. Setting these fields up correctly from the start prevents compliance headaches later, whether that means a missing DOT number on an inspection screen or a driver who cannot select the right vehicle. This guide walks through how driver profiles work in Samsara and how to configure them properly.
Since driver profiles are one piece of a much larger fleet management system, it helps to understand the platform they belong to. Samsara – GPS Fleet Tracking Software provides the dashboard, mobile app, and compliance tools that driver profiles connect into, and it offers useful context before working through the configuration steps covered in this article. With that framing established, let’s look at what actually goes into building a driver profile.
What Is a Driver Profile, and Why Does It Matter?
What information does a driver profile actually store?
A driver profile in Samsara holds the identification and compliance information required for a driver to operate legally and log in to the Samsara Driver App. At minimum, this includes the driver’s name, license number, and the state or province where that license was issued, since these fields are required rather than optional. Beyond the basics, the profile also stores login credentials, Hours of Service settings, and carrier details, which together determine both how the driver experiences the app and how their data appears in compliance reports.
Why can’t a driver account move between organizations?
It’s worth knowing upfront that a driver account only exists within the organization where it was created. If a driver switches employers, or if your company restructures across multiple Samsara organizations, the driver profile does not transfer automatically. Consequently, moving a driver between organizations requires creating a new profile rather than migrating an existing one, so it’s worth planning driver structure carefully before large-scale rollouts.
Who can create and edit driver profiles?
Driver profile management happens from the Fleet Settings menu, and it is generally restricted to administrators. Full Admins, along with users granted specific driver management permissions, can add new drivers, edit existing profiles, and deactivate accounts as needed. Because driver profiles touch compliance-sensitive fields like carrier overrides and Hours of Service exemptions, most fleets limit this access to a small group of trusted administrators. Restricting this permission also reduces the chance of accidental changes to fields like Home Terminal Timezone, which directly affects how HOS logs are timestamped and could create compliance discrepancies if changed carelessly.
How Do You Create a New Driver Profile?
What are the basic steps to add a driver?
Creating a driver profile from the dashboard follows a short, consistent sequence:
- Select the Settings icon at the bottom of the Fleet menu.
- Navigate to Organization, then select Drivers.
- Click + Add a driver to open the driver creation form.
- Enter the driver’s name, along with any additional identification details you want to collect.
- Set a unique username and an initial password for Driver App login.
- Save the profile to activate it.
What password requirements should you keep in mind?
Password strength matters more here than it might for a typical account, since drivers use these credentials daily to log Hours of Service and complete compliance workflows. If an administrator has enabled Stronger Device Passwords, passwords must be at least eight characters. For better security regardless of that setting, Samsara recommends using at least ten characters, mixing uppercase and lowercase letters, adding numbers and symbols, and avoiding common words or personal information. When a password meets these recommendations, the dashboard displays a Strong indicator to confirm it.
What happens if a username is already taken?
Usernames must be unique across your organization, so if the dashboard rejects a username during setup, another driver has likely already claimed it. You can search for the conflicting username under Active Drivers or Deactivated Drivers within the Drivers settings page to identify who holds it. This is a common snag with common names, so building a simple naming convention in advance, such as first initial plus last name, avoids repeated conflicts as your fleet grows.
What Key Settings Should You Configure in Every Profile?
How do Hours of Service settings affect a driver’s experience?
Several settings determine how a driver’s Hours of Service logs behave, and they matter significantly for compliance. The table below summarizes the core options available.
| Setting | What It Controls |
|---|---|
| ELD Exempt | Excludes the driver from ELD-related HOS violation notifications |
| ELD Personal Conveyance | Allows off-duty driving in an unladen vehicle for non-work purposes |
| ELD Yard Moves | Allows on-duty, non-driving movement without counting toward drive time |
| ELD Day Start Hour | Sets what time a new HOS day begins for that driver |
| Home Terminal Timezone | Determines the timezone used specifically for HOS log timestamps |
Why does carrier information matter at the driver level?
DOT inspections require carrier information, such as the company name, address, and DOT number, to display correctly on any device presenting Hours of Service logs. Most fleets set this once at the organization level, but Samsara also allows a driver-specific override when a driver operates under different carrier information than the rest of the fleet. If you apply an override, it takes priority over both the fleet-wide setting and any vehicle-level override. For this reason, double-check these fields for drivers who operate under leased authority or a different carrier arrangement.
How does the platform handle cross-border driving?
Fleets that regularly send drivers across the US-Canada border have an additional layer to configure. The system automatically calculates Hours of Service violations according to the ruleset for the country where the driver currently operates. It also accounts for any enabled exemptions. Within minutes of entering Canada, the app automatically switches to the driver’s pre-selected Canadian ruleset. By default, the app uses Canada South Cycle 1, but administrators can switch a specific driver to Cycle 2. This automatic switching removes the need for drivers to manually adjust settings mid-route, which reduces the chance of a compliance gap during cross-border trips.
How do vehicle and asset restrictions work?
Fleet administrators can restrict which vehicles or assets a driver sees and can select within the Driver App, using tag-based assignment fields in the profile. If this field is left blank, the driver can view and select any vehicle or asset across the organization, which is not ideal for larger fleets where drivers should only interact with their assigned equipment. Applying the correct tags here also affects what appears on the driver’s in-app map, since only vehicles and assets within their assigned tag will be visible there.
How Do You Manage Drivers at Scale?
When should you use bulk driver management instead of adding drivers one by one?
Adding drivers individually works fine for small fleets or occasional new hires, but larger onboarding efforts call for a faster approach. Samsara supports bulk driver management through a CSV template, which becomes especially useful when onboarding dozens of drivers at once or updating shared fields, such as a home terminal address, across many profiles simultaneously.
What does the bulk upload process look like?
The general workflow for bulk edits follows these steps:
- Navigate to Organization > Drivers within Fleet Settings.
- Select More Actions, then choose Upload CSV.
- Download either the existing drivers list or a blank template, depending on whether you’re editing current profiles or creating new ones.
- Make your changes in the CSV file and save it.
- Upload the file and preview the proposed changes before confirming.
- Review any errors flagged during the preview, correct them, and retry if needed.
- Select Finalize Changes to apply the updates.
It’s worth noting that the Export or Download CSV option is meant for viewing driver data only. Using it as the basis for a bulk upload can introduce formatting errors, so always start from the dedicated upload template instead.
How do you deactivate a driver who leaves the fleet?
Deactivating a driver preserves their historical records rather than deleting them outright, which matters for compliance reporting. Before deactivating anyone, confirm the driver has no active session in the app and has signed out successfully. From the Active Drivers list, open the More Actions menu next to a driver’s name and select Deactivate to complete the process. The driver’s historical Hours of Service data remains available in reports for as long as needed.
Can Driver Profiles Be Managed Through the API?
Why would a fleet automate driver management?
Fleets that run their own HR or dispatch systems often want to keep driver records synchronized automatically instead of entering the same information manually in two places. Samsara’s API supports creating, updating, and deactivating drivers programmatically, which lets a company’s existing systems push changes directly into Samsara without an administrator repeating the same data entry by hand.
How does synchronization typically work?
Two common patterns keep driver data in sync. The first involves periodically polling the driver list endpoint and comparing results against your own records, which works well for systems that check in on a schedule rather than reacting instantly. The second approach uses webhook events that fire whenever someone creates or updates a driver in Samsara. External systems then receive near real-time notifications instead of waiting for the next polling cycle. Many integrations also store an external identifier alongside the Samsara driver ID, which makes matching records between the two systems considerably more reliable over time.
Conclusions
Configuring a driver profile in Samsara goes well beyond entering a name and issuing a password. Getting the Hours of Service exemptions, carrier overrides, and vehicle restrictions right from the start keeps compliance reporting accurate and gives each driver an app experience that matches their actual role. Fleets managing a handful of drivers can comfortably use the standard one-by-one form, while larger operations benefit from bulk CSV uploads or API-driven synchronization to keep hundreds of profiles current without manual rework. For a broader look at how driver data connects to the rest of a fleet’s tracking, safety, and compliance tools, Samsara – GPS Fleet Tracking Software remains a useful resource alongside the configuration steps outlined here.
Frequently Asked Questions
No. A driver account is only active within the organization where it was originally created and cannot be transferred to a different one. If a driver needs an account in a new organization, you’ll need to create a fresh profile rather than migrate the existing one.
Deactivating a driver does not delete their historical records. The data remains accessible in the Samsara dashboard, and the driver’s name continues to appear in Driver HOS reports for time periods when they were active, even after deactivation.
Not necessarily. Most fleets configure carrier information once at the organization level, and it applies to all drivers by default. A driver-level override is only needed when a specific driver operates under different carrier details, such as a different DOT number or address, than the rest of the fleet.
