Feature
Keyfobs: control who can start which vehicle
In a delivery fleet the same vehicle is used by different couriers across shifts. Keyfob management makes access an administrative action: issue, block or reassign a fob in the panel, and the vehicle follows.
Access control
Fob blocked · shift ended
What keyfob management does
- Assign a keyfob to a courier, and the courier to a vehicle or a pool.
- Block a lost or stolen fob immediately, without recovering the vehicle first.
- Reassign fobs between shifts as couriers rotate.
- Keep a record of who held which fob and when.
- Offboard a courier and remove their access in one action.
How it works
Step 1
Register the fobs
Fobs are imported or added per hub and held in the group they belong to.
Step 2
Issue to a courier
The fob is assigned in the panel together with the courier record and hub.
Step 3
Shift starts
The courier uses their fob on the vehicles their group allows.
Step 4
Something changes
Loss, theft or an ended contract: the fob is blocked in the panel in seconds.
Step 5
History remains
Assignment history stays on the courier and the fob for later checks.
Who uses it
| Role | What they use it for |
|---|---|
| Hub lead | Daily issuing and collection of fobs |
| Operations manager | Blocking access after incidents or offboarding |
| Fleet owner | Reducing unauthorised and off-shift use |
| HR / admin | Clean handover records per courier |
Data you get out
- Fob register per hub with current holder.
- Assignment and block history per fob and per courier.
- Offboarding record showing access was removed.
- CSV export and API access.
Related modules
User management holds the courier records behind each fob, Zone Guard flags vehicles leaving where they belong, and Control Tower is where you notice a vehicle moving when it should not.
Frequently asked questions
Related
See it on your own fleet
Book a 30-minute walkthrough. We open the panel with your vehicle types, hubs and countries in mind — no slides.
Book a demo