Introduction
By June 2026, Motive is going to move to a self-service authentication model for all users (including drivers). This update removes the burden of password management from Fleet Admins and gives drivers direct control over their own security.
What is going to change?
- For Admins: Admins will no longer create or manage passwords for drivers. Whether they add drivers via the Dashboard, CSV, API, or Directory Sync, they must provide a unique email or mobile number for each account.
- For Drivers: Drivers will now set up and manage their own credentials. They can use secure, modern login methods like magic links and self-service password resets, significantly reducing lockouts and the need for admin intervention.
Note:
|
- More sign-in options for drivers: Drivers can now log in using any of three methods:
- Password: Set by the driver during account setup. Drivers with existing passwords can continue to log in as they do today
- Magic link: One-tap login link sent to the driver's email or phone
- One-time password (OTP): A 6-digit code sent via email or SMS, ideal for shared tablets or kiosks where using a magic link on a separate device isn't practical
Why are we making this change?
Motive is committed to providing enterprise-grade security while reducing the administrative burden on your fleet. This transition focuses on three key areas:
- Enhanced security and accountability: Relying on shared passwords or accounts without contact information creates significant security gaps. By requiring unique identifiers, we ensure that every individual accessing the Motive platform is verified, protecting your fleet's sensitive data.
- Driver empowerment and autonomy: Drivers no longer need to wait for an admin to reset a forgotten password. With verified contact info, they gain access to seamless, self-service tools like magic links and instant password resets, keeping them on the road and productive.
- Reduced administrative overhead: Managing driver credentials manually is time-consuming and prone to error. Moving to a "Contact-First" model automates the authentication lifecycle, eliminating the need for admins to handle password-related support tickets or manual credential distribution.
Rollout Plan or Feature Go-Live date?
Tentative Launch Date: 06/30/2026
FAQs
What is changing in how drivers log in to Motive?
Drivers are transitioning to a secure, self-service login model that replaces admin-managed passwords with verified email or mobile-based authentication.
Can drivers still use their existing passwords after this change?
Yes. Drivers with existing passwords can continue to log in as they do today. No action is needed for currently active driver accounts.
What information do I need to provide when creating a driver?
You'll need to provide either an email address or a mobile number (or both) for each of your existing and new driver accounts.
My drivers use shared tablets. Will this still work?
Yes. OTPs are designed specifically for shared or kiosk-style devices. Drivers can enter a code sent to their email or phone without needing to click a link from a second device.
What if a driver doesn't have an email address?
For drivers without an email address, you can use their mobile phone number for secure authentication via SMS-based magic links or one-time passcodes (OTPs).
As a fleet admin, can I still reset a driver's password for them?
You can send a secure password reset link to the driver's contact method from their profile in the Fleet Dashboard. You will no longer set driver passwords directly; only the driver creates and knows their own password.
We use SSO for driver login. Does anything change for us?
No. If your fleet relies solely on Motive SSO for drivers, no passwords are required during account setup, and your authentication flow is unchanged.
I use the API / bulk import / Directory Sync to create drivers. What do I need to do?
Before June 30, 2026, update your workflows to remove any password fields and ensure a valid email address or mobile number is included for each driver. After launch, driver creation will fail if passwords are included or contact info is missing.
.
Share this with others