Articles in this section

Configuring the driver-licence module

Published:
Updated:

This article walks fleet managers and administrators through the driver-licence module settings — enforcement mode, expiry reminder thresholds, the reminder run time, and the verification cycle and reminder thresholds.

Who can configure the module

Changing these settings requires the driverLicense:configure permission, held by the FleetManager and SystemAdmin roles. Settings are stored per tenant; if you have never saved them, sensible defaults apply.

Settings reference

SettingPurposeDefault
Enforcement modeHow booking enforcement reacts when a driver lacks the required licence class.SoftWarning
Expiry reminder thresholdsDays-before-expiry at which licence-class and CPC reminders are sent.90, 60, 30, 14, 7
Reminder execution time (UTC)The time of day the reminder jobs are scheduled to run.06:00
Verification cycle interval (days)How long after a successful check the next check becomes due.180
Verification reminder thresholdsDays-before-due at which drivers are reminded of an upcoming check.30, 14, 7

Enforcement mode

Enforcement mode must be either SoftWarning or HardBlock.

  • SoftWarning — bookings involving a licence mismatch are flagged but allowed to proceed.
  • HardBlock — a licence mismatch prevents the booking.

Expiry reminder thresholds

Provide between 1 and 10 threshold values. Each value must be between 1 and 365 days, and duplicates are not allowed. These thresholds drive the licence-class and CPC expiry reminders.

Reminder execution time

Set the run time as a UTC time of day (for example 06:00). This records when the daily reminder processing is intended to run for your tenant.

Verification cycle and reminder thresholds

The verification cycle interval must be between 30 and 730 days. The verification reminder thresholds determine how far ahead drivers are warned about an upcoming check.

Warning: Every verification reminder threshold must be smaller than the verification cycle interval. If any threshold is greater than or equal to the interval, saving fails with the message "Erinnerungsschwelle muss kleiner als das Kontrollintervall sein" (reminder threshold must be smaller than the check interval).

Related reference-data configuration

The same driverLicense:configure permission also governs the reference data that supports licence checks:

  • Vehicle and model licence requirements — the licence class required to drive a vehicle or every vehicle of a model, and whether CPC is required.
  • Country licence validity — per-country validity years and renewal rules for each licence class.
Note: The verification workflow itself (uploads, the queue, accept/reject, and reports) belongs to the licensed Führerscheinkontrolle module and only functions when the EnableFuehrerscheinkontrolle flag is enabled for your tenant. The settings above still apply to base licence data even when the module is off.

Related

  • Scheduling recurring checks and setting the interval
  • Reminders for upcoming and overdue checks
  • Who can upload versus who can verify licences
  • Generating a compliance report
AH
Written by Alexander Hagemann
Updated:
Access denied
Access denied