Deactivating a driver
This article explains how to take a driver out of service in MobilityManager and what happens to their pool access and booking ability when you do. Drivers are deactivated rather than deleted, so historical bookings and audit records stay intact.
Deactivate, don't delete
A driver profile carries an active flag. When a profile is inactive, the record and its history remain in the tenant database, but the person is excluded from all live driver, pool, and booking operations. This preserves reporting and audit continuity while stopping the driver from taking new trips.
How a driver becomes inactive
There is no standalone "deactivate driver" switch on the profile itself. A driver is taken out of service through the user account and role management:
- Deactivate the user account. This prevents the person from signing in at all and is the most reliable way to stop bookings. Account deactivation requires user-management permission (typically SystemAdmin).
- Remove the Driver role if the person should keep other access but no longer drive. This removes their driver capability going forward.
Warning: Removing the Driver role stops new profiles from being provisioned, but an existing active profile can still be resolved for booking flows. To be certain a person can no longer book or drive, deactivate their user account.
What an inactive driver can no longer do
Once a driver profile is inactive, the system excludes it everywhere it matters:
- It no longer appears in the tenant driver list used by fleet managers.
- It cannot be assigned to a pool — attempts are rejected with "Cannot assign inactive driver to pool".
- It is dropped from pool membership listings.
- It resolves to no accessible vehicles, so no vehicle is bookable.
Reactivation
Driver deactivation is reversible. If you reactivate the user account, the profile's self-healing provisioning reactivates the matching driver profile automatically the next time it runs, restoring the person's shared-pool access. Any explicit pool assignments that were left in place also take effect again.
Data-erasure deactivation
When a person exercises their right to erasure, the GDPR pseudonymisation process also deactivates their driver profile as part of scrubbing personal data: it clears the name, email, phone, and licence fields and sets the profile inactive. This is a permanent, one-way action and is separate from an ordinary reversible deactivation.
Related
- How a driver profile is auto-created for a user
- Creating and editing a driver profile
- Removing a driver from a pool
- Viewing pool membership
