How a driver profile is auto-created for a user
This article describes how MobilityManager automatically provisions a driver profile (Fahrerprofil) for a user, so you understand where driver records come from and why one may appear without anyone creating it by hand.
Why profiles are provisioned automatically
Booking and pool features need a tenant-scoped driver record, but the person's identity lives in the shared user account. To keep these in step, the system provisions a driver profile on demand instead of relying on someone to create it manually. This keeps booking flows working even if role assignment and tenant data drift apart.
When provisioning happens
A driver profile is created (or repaired) at several points:
- When the Driver role is assigned to a user for your tenant, a matching profile is created immediately.
- On first sign-in for users who authenticate through single sign-on (OIDC), a profile is ensured as part of login.
- Lazily, during booking-related actions, if an active profile is still missing the system will create one on the spot.
Conditions that must be met
Lazy provisioning only creates a profile when all of the following are true:
- The user holds the Driver role for the current tenant.
- The user account is active.
- A tenant context can be resolved for the user.
If the user does not hold the Driver role, no profile is created and driver features remain unavailable to them.
How the profile is filled in
The new profile copies details from the user account: first name, last name, and email. If the first name is blank, the email address is used as a fallback so the required name field is never empty. Names can also be derived by splitting the username when structured name fields are not available.
Self-healing (repair) behaviour
When a profile already exists, provisioning also repairs it rather than duplicating it. On each run it may:
- Reactivate the profile if the user account is active again.
- Update the stored email to match the user account.
- Backfill a missing first name or last name.
Note: There is only ever one profile per user per tenant. Repairs update that single record; they never create a second profile.
What provisioning does not do
Auto-provisioning creates the driver record only. It does not grant access to any non-shared pool. Every driver automatically has access to the shared car-sharing pool, but access to other pools still requires an explicit driver-to-pool assignment.
Related
- Creating and editing a driver profile
- Deactivating a driver
- The difference between shared pools and personal assignment
- Assigning drivers to a pool
