These vehicles were added to inventory automatically when they were scanned at the gate, rather than being entered by a person. They behave like any other vehicle. This list is a record, not a task list.

Most recent gate activity first. Vehicles with no movements follow, by barcode.

Choose the simulated current scanner here, outside the scan workflow.

Prototype-only user directory. Demo credential fields are not secure production passwords. Permissions shown here are planning controls only; production roles require AWS-backed authentication and server-side authorization. Drivers are operational records, not application login accounts.

When a location's override is on, a driver whose badge is scanned there can leave without a daily authorization, as long as the driver is active, the license is current, and nobody revoked the driver's authorization today. A typed employee # is never covered; it still needs a Fleet Lead or above. Every exit the override allows is recorded as a location override, not as authorized.

Only the Admin sees this tab, and the shared records accept a switch change from the Admin's login only. Every change is confirmed and recorded.

While you are getting everything into the system. When a location's collecting mode is on, a gate phone there accepts a driver number it does not know and adds that driver to the list (with a number and no name, marked "New driver (name needed)"), and an OUT does not ask for a Fleet Lead or an authorization. Everything is still recorded. It does not change what happens to a driver who is on the list and marked inactive, or whose license has expired. Turn it off when you are ready to enforce the checks, and every check is back as it was.

Only the Admin sees this tab, and the shared records accept a switch change from the Admin's login only. Every change is confirmed and recorded. A phone takes the change within about five minutes.