Attendance Kiosk - Zayeen Documentation

Used By

Employees, front desk operators, HR, and attendance admins

shared operational kiosk

camera, active kiosk device, work schedule, and browser permissions

When attendance is handled from one shared device at an entrance gate, lobby, store, warehouse, or project site.
When the regular employee attendance page is not suitable because many employees use the same device in sequence.
When the process requires a proof photo or a face verification step before check-in or check-out is saved.

Prepare schedules in Work Hours List and holidays in Holiday List.
Make sure employee master data is complete and the employee ID used in the field is consistent.
Create at least one device in Attendance Kiosk Device.
If the device uses face verification, complete face registration first in Face Enrollment.
Open the kiosk page with the ?deviceid=... query so the device is preselected automatically.

Open People & Payroll / Attendance / Attendance Kiosk.
Make sure the kiosk device is selected. If not, select the correct device for that location.
Type the employee ID manually or scan a QR code if the device supports camera scanning.
Press the ID check or scan action until the employee name and attendance status appear.
When the status is ready, press Start Check-In or Start Check-Out.
Read the verification instruction shown above the camera panel. The live preview keeps only the face frame so the preview stays clear.
When the camera is ready, align the face to the guide frame. Smile, blink, or move slightly when the selected verification mode asks for a liveness action.
Press Take Photo only when the capture state is ready. For face_api and webhook modes, verification continues automatically after the proof photo is captured.
If successful, the attendance is saved, the Done button appears, and the kiosk starts a 30-second auto reset countdown.

Mode	Description	Best For
photo_only	The device captures a proof photo only. No face template matching is performed.	Simple kiosk rollout where a proof image is enough.
face_api	Face matching is performed directly in the browser using the employee enrollment template.	Sites that want browser-based face verification without a dedicated recognition server.
webhook	The proof image is sent to an external face engine through device configuration.	Companies that already have their own recognition service or a third-party engine.

The kiosk now uses only the deviceid query parameter. Older tenant or device aliases are ignored.
If no deviceid is provided, the page forces the user to choose a device from the list.
The Change Device action and leaving the kiosk page are protected by the device admin PIN.
The attendance cancel action on the kiosk requires both an admin PIN and a reason, because it is intended for supervised correction on a shared device.
Device master data can show additional HTML information on the kiosk side panel, such as branch notices, queue instructions, or internal reminders.
If face verification fails, the proof image is not kept for that attendance attempt.
For a face mismatch result, the kiosk does not immediately force the finish countdown, so the user can retry right away.
After success, the kiosk hides the blocked-verification banner so the final confirmation state is easier for employees to understand.

Verification cannot start: check whether the employee is actually inside an active check-in or check-out window.
Face verification never passes: check whether the employee already has an active face template and whether browser camera permission was granted.
QR scanning does not appear: enable Scan ID With Camera in the kiosk device setup.
Employees cannot check out: check whether an open check-in record exists for that employee.
Users keep changing the device: review and protect the admin PIN in the device master.

Face Enrollment to build employee face templates.
Attendance Kiosk Device to configure verification mode, admin PIN, and camera scanning.
Employee Attendance for personal device attendance, not the shared kiosk flow.