Articles in this section

Creating and editing a driver profile

Published:
Updated:

This article explains how a driver profile (Fahrerprofil, the tenant-scoped driver record) comes into existence in MobilityManager and how to keep its details up to date. Driver profiles are not created from a blank form; they are provisioned from the underlying user account and the Driver role.

What a driver profile is

A driver profile is a record inside your tenant database that represents one person who may book and drive vehicles. It is linked to a user account in the shared system database by a user ID, so one person has exactly one driver profile per tenant. Each profile holds:

FieldNotes
First name / Last nameMirrored from the user account; required
EmailKept in sync with the user account
PhoneOptional
Licence number / Licence expiry dateOptional flat fields, superseded by the structured Führerscheinkontrolle (driver's licence check)
ActiveWhether the driver takes part in pool and booking flows

Creating a driver profile

Because a profile is tied to a user, you create one by assigning the Driver role to an existing user account. This requires role-management permission (typically a SystemAdmin, or a FleetManager granted that permission).

  1. Make sure the person has a user account in your tenant.
  2. Assign the Driver role to that user.
  3. The system automatically creates the matching driver profile in your tenant, copying the name and email from the user account.
Note: There is no separate "add driver" form. If you assign the Driver role and a profile already exists, the existing profile is reused rather than duplicated.

Editing profile details

The name and email on a driver profile are owned by the user account and are synchronised automatically. To change them, update the user's first name, last name, or email in user management; the driver profile picks up the new email on the next sync and backfills any missing name fields.

Tip: For licence data, use the Führerscheinkontrolle (driver's licence check) profile rather than the flat licence-number field. The structured licence profile is the authoritative source and is what compliance checks rely on.

What editing does not change

Editing the profile does not change which pools a driver can use. Pool access is managed separately through driver-to-pool assignment. Similarly, deactivating a driver is handled through the user account rather than by editing profile fields directly.

Related

  • How a driver profile is auto-created for a user
  • Deactivating a driver
  • Assigning drivers to a pool
  • Viewing pool membership
AH
Written by Alexander Hagemann
Updated:
Access denied
Access denied