Drivers
Manage driver profiles, calendars, and availability in Sixième Étoile — onboarding, vehicle assignment, calendar events, and single-session enforcement.
Overview
The Drivers module (section H) manages all driver records for the organisation. Drivers are the human resource layer of the dispatch engine: their availability, assigned vehicle, and compliance status determine whether they can be assigned to missions.
Driver List (H-01)
The driver list shows every driver registered under the organisation with:
- Name and profile photo
- Status:
Available,On mission,Off duty,Inactive - Assigned vehicle: default vehicle registration plate and category
- Last known position: city or zone from the last GPS ping (driver app)
- Compliance badge: green (
Compliant), amber (Expiring soon), or red (Non-compliant)
Use the filter bar to narrow by status, vehicle category, or compliance state. The + New driver button opens the onboarding form.
Driver Detail (H-02)
The driver detail view has four sections:
Personal Information
Full name, date of birth, email, phone number, home address, emergency contact, and internal notes.
Professional Information
- VTC professional card number (
carte professionnelle) and expiry date - Driver's license number and expiry
- Social security number (optional, for payroll integration)
- Employment type: employee or independent contractor
Assigned Vehicle
The primary vehicle currently assigned to this driver. An operator can reassign by selecting a different vehicle from the fleet. The previous assignment is recorded in the vehicle's history log.
Statistics
- Completed missions (last 30 days / all time)
- Revenue generated (CA HT)
- Average passenger rating
- Average punctuality score (on-time arrival percentage)
Driver Onboarding
To add a new driver:
- Click + New driver from the driver list.
- Fill in personal and professional information.
- Upload compliance documents on the Documents tab (see Driver Compliance).
- Assign a default vehicle.
- Click Activate to make the driver available for dispatch.
The driver receives an email invitation with a link to install the driver mobile app and set up their account.
Driver Calendar (H-03)
The driver calendar displays mission assignments and availability blocks in a weekly view. It is built on top of DriverCalendarEvent records which have the following fields:
| Field | Type | Description |
|---|---|---|
organizationId | string | Owning organisation |
driverId | string | Driver this event belongs to |
startAt | datetime | Event start (UTC) |
endAt | datetime | Event end (UTC) |
type | enum | See event types below |
notes | string | Optional free-text note |
Calendar Event Types
| Type | Meaning | Dispatch impact |
|---|---|---|
VACATION | Paid holiday | Driver excluded from all assignment |
OFF | Day off (non-paid) | Driver excluded from all assignment |
UNAVAILABLE | Driver unavailable for any reason | Driver excluded from all assignment |
TRAINING | Professional training day | Driver excluded from all assignment |
MAINTENANCE | Driver performing vehicle maintenance | Driver excluded from all assignment |
All five types cause the dispatch engine to treat the driver as unavailable during the event window. When you create a new mission assignment that overlaps with an existing calendar event, the dispatch engine shows a conflict warning before confirmation.
Creating availability blocks
- In the driver calendar, click an empty time slot or drag across a range.
- Select the event type from the dropdown.
- Add an optional note (reason, location, etc.).
- Click Save.
The block appears immediately in the calendar and is visible to other operators. Mission assignments already confirmed for overlapping windows are not automatically cancelled — a warning is displayed, and the operator must resolve the conflict manually.
Single Driver Session (FR399)
A driver can only have one active app session at a time. This prevents data integrity issues that would arise if the same driver were logged in on two devices simultaneously (for example, two phones accepting mission notifications independently).
When a driver tries to log in on a second device while an active session exists on another device:
- The driver app shows a warning: "An active session exists on another device."
- The driver can choose to terminate the existing session and continue on the new device.
As an operator, you can also force-disconnect an existing driver session from the driver detail view:
- Open the driver's detail (H-02).
- Click the Active session panel in the top-right.
- Click Force disconnect.
- Confirm the action in the dialog.
The driver is immediately logged out on their device and must re-authenticate. Use force-disconnect when a driver has lost their phone, is unable to log out themselves, or when troubleshooting app issues.