You are a security officer if you stand at the checkpoint - the barrier, the turnstile or the vehicle gate - and decide whether the person in front of you goes in. In EvTrack you do that with the EvTrack Guard app on an Android handset: you scan the visitor’s pass, check the person against it, and the app records the entry or exit.
Start here
- Get a handset that is registered and logged in. Your administrator registers the device and gives you an officer login - see Register the Device and Install the App.
- Know what your account allows. The ready-made Guards role holds the two permissions the app needs to scan: EvTrack Guard App: Allow Access Control (Scan RF/ID/QR/PIN) and Visitor Management: Add. With it you can log in to the web product too, but you will see only the Dashboard - your work is on the handset.
- Read what the app will ask you. Configure the Guard lists every question the app asks, and your administrator decides which are switched on.
At the checkpoint
Scan a pass
Scan the QR code on the visitor’s phone or badge, or their card. The app shows who the pass belongs to and whether it is valid now. Compare the photo with the person in front of you before you let them in.
When the app refuses someone
The app refuses a pass outside its visit window (it says the credential has expired or is not valid yet) and the pass of a cancelled visit, and it refuses to enrol someone who matches the watchlist. Do not override a refusal at the barrier: send the visitor to reception, or call the host. If the app itself is refused, see The Handset Is Refused After Login.
Someone without an invitation
Where your administrator has switched it on, you can enrol a walk-in on the handset and, if host approval at the checkpoint is on, wait for the host to accept - see Host Approval at the Checkpoint. Otherwise send them to reception.
Vehicles and drivers
Where your site records vehicles, the app asks for the plate and the driver, and can read plates automatically where a camera is fitted - see ANPR.
When something looks wrong
- Visits are recorded at the wrong place: Visits Are Filed at the Wrong Location.
- A setting your administrator changed has not reached the handset: Settings Do Not Take Effect.
- Anything else: tell your supervisor and your administrator; By Role lists who to ask.
What you do NOT need
- Inviting visitors or approving requests. Hosts and managers do that before the visitor arrives.
- The web product’s menus. Your account shows only the Dashboard there, by design.
- Setting up the app. Which questions it asks is configured centrally.