Driver Portal Access: Rights, Password and Driver Block
Overview
Every driver can log in to the driver portal (WebRes) with their own credentials (article 19) – there they reserve pool vehicles and report back mileage, fuel receipts, damages and tyre changes. You manage access, portal rights and the driver block (Fahrersperre) in the driver file.
Resetting the password
The "Kennwort zurücksetzen" (Reset password) action (in the header of the file or the button in the Details block) opens a dialog in which you enter a new password twice. There is no display of the old password – forgotten passwords are always set anew. During the driver import, initial passwords can also be supplied column by column (article 50).
To log in, drivers select "Als Fahrer anmelden" (Log in as driver) on the start page; depending on the system configuration they choose their name from a list or enter their personnel number or e-mail address.
The "Rechte" tab
| Setting | Effect |
|---|---|
| "Auf welche Pools hat der Fahrer Zugriff?" (Which pools can the driver access?) | Multiple selection of the vehicle pools whose vehicles the driver may reserve in the portal |
| "Fahrer ist WebRes Disponent?" (Driver is a WebRes dispatcher?) | The driver receives dispatcher functions in the portal (reservation manager) |
| "Keine Rundmail" (No circular mail) | The driver is excluded from circular mails |
Important: you save changes on this tab with the Save button of the tab – this saves the pool assignment, dispatcher flag, circular-mail setting and the block status together.
Driver block
You set the block via the "Fahrer sperren" (Block driver) action (or "Sperre aufheben" / Lift block) in the header, or via the "Fahrer ist gesperrt?" (Driver is blocked?) checkbox in the Kontakt block. When blocking, FMWeb documents automatically:
- "Gesperrt seit" (Blocked since) – pre-filled with the current date (adjustable)
- "Gesperrt durch" (Blocked by) – the user carrying out the action (display only)
The block only takes effect once the file is saved. A blocked driver
- receives no more automatic e-mails (driving licence, HU/UVV, tyre change reminders etc. – the skip is traceable in the e-mail diagnostics, article 07),
- no longer appears in the driver login list of the driver portal and is hidden from the WebRes driver lists,
- is no longer offered in the driver selection lists of the backoffice.
The driver file itself remains fully intact and editable; when the block is lifted, the date and user are removed again.
Frequently asked questions
What is the difference between "gesperrt" (blocked) and "inaktiv" (inactive)? Both exclude the driver from the portal login list and from e-mails. The driver block (Fahrersperre) is intended as a deliberate, documented measure (with "seit" / since and "durch" / by), e.g. when a driving entitlement has been withdrawn; Inaktiv marks drivers who have left.
A driver sees no vehicles in the portal. Check the pool assignment on the "Rechte" tab as well as the client's WebRes settings (article 19).
Who may block a driver? Any user with drivers.edit. The backoffice permissions themselves are managed via roles (article 18).
Related articles
