Who can upload versus who can verify licences
This article explains the difference between uploading a licence and verifying it, and which roles and permissions are required for each action in the Führerscheinkontrolle module.
Two distinct responsibilities
The Führerscheinkontrolle deliberately separates the person who submits a licence from the person who confirms it. A driver (or someone acting for them) uploads the licence documents; a fleet manager reviews and decides the outcome. This separation keeps the audit trail meaningful — the verifier is a distinct, authorised reviewer.
Permissions that control each action
| Permission | Allows |
|---|---|
driverLicense:view | View your own licence profile and your own verification status; read licence-class reference data. |
driverLicense:manage | Read and edit any driver's profile; view the compliance dashboard, another driver's verification status, and verification history. |
driverLicense:configure | Change module settings, vehicle/model licence requirements, and country validity reference data. |
licenseVerification:upload | Upload the front and back of a licence to create a verification request. |
licenseVerification:verify | Review the queue; accept, reject, or record a manual check; trigger a verification cycle. |
licenseVerification:report | View the compliance report summary and generate exports. |
Default role assignments
- Driver — holds
driverLicense:viewandlicenseVerification:upload. A driver can view their own profile and submit their own licence, but cannot verify anyone or see colleagues' profiles. - FleetManager — holds all six driver-licence permissions, so a fleet manager can upload, verify, configure, and report.
- SystemAdmin — holds all six permissions as well.
Note: These are the defaults for the built-in system roles. You can create custom roles and assign any subset of these permissions to match your organisation's separation-of-duties needs.
Uploading versus verifying at a glance
- Uploading creates a Pending request and does not confirm anything on its own. Anyone with
licenseVerification:uploadcan do it. - Verifying (accept, reject, or manual check) is the decision step that updates the driver's verification dates and writes the audit entry. It requires
licenseVerification:verify.
Module licensing still applies
Holding the right permission is necessary but not sufficient: the verification actions live in the licensed Führerscheinkontrolle module. If the EnableFuehrerscheinkontrolle flag is off for your tenant, these endpoints return a LICENSE_CAPABILITY_DISABLED error regardless of permission. Base licence data (profiles and the dashboard) stays available.
Related
- Uploading a driving licence for verification
- Performing a verification: accept, reject, or manual check
- Configuring the driver-licence module
- What the Führerscheinkontrolle is and why it is required
