Manage Driver Access and Devices

Prepare a driver's user and device access before assigning live work. Device approval is not the same as creating a Driver, and a valid login is not proof that the user is linked to the right driver.

Prepare the person

Maintain an enabled User and active Driver with the correct Employee/user link and company context. Check the driver's licence and trip assignment. Missing or conflicting links can leave the app signed in but unable to show assigned work.

Expense claims need the employee and company context required by the claim process. Give users only the applicable business permissions; the scoped driver actions do not require making every driver a transport administrator.

Approve the device

An administrator or Transport Manager reviews Transport Mobile Device, its user, device identity and approval state. Check the actual person and phone before approving. A device requiring attention cannot be treated as approved merely because its owner still knows the password.

After correcting a device problem in Desk, the user can refresh the app's device/session state. If the session has expired, sign in again; an expired session is not an offline stock-posting allowance.

When a driver changes phones

Keep the previous device record for history and revoke its access when it should no longer be used. Review and approve the new device for the correct user; the current approval policy limits active device use rather than requiring you to delete historical transactions.

Before switching, synchronise pending proofs, attachments and requests wherever possible. Work saved only on the old phone is not automatically moved to the new phone. Confirm that the server has the submitted records before clearing app data.

When the physical phone changes owner

Use the administrator-only Reassign Device action, not an unaudited edit to the owner field.

1. Confirm all pending work has been synchronised and review any reported pending items.
2. Clear the previous user's local app data on the physical phone. The administrator's acknowledgement does not remotely erase the phone.
3. Select the new eligible user, provide the reason and confirm local data clearance in the reassignment dialog.
4. Complete reassignment and have the new user sign in. Review the new user's other device approval as the handover retires conflicting active access.

The handover records the change and resets owner-specific notification credentials. The previous user's login must not continue using the reassigned device. Cross-company reassignment and ambiguous/inactive driver links are restricted by the eligibility checks.

Revoke blocks access; Reassign Device changes who may use that physical device with an audit trail. They are not interchangeable with deleting a phone's history.

[Screenshot: Transport Mobile Device approval state and Reassign Device dialog showing new user, reason and local-data-clearance acknowledgement]

See Complete Work in the Driver App for routine refresh, offline queue and trip actions. Remote push delivery is disabled in the current application; do not rely on a push notification to tell a driver about assigned work.