Attendance Kiosk Device
Attendance Kiosk Device is the master form used to define kiosk identity, location, verification mode, admin PIN, and supporting options used by the attendance kiosk page.
Used By
HR admins, IT admins, and kiosk owners
Data Type
master data
Search Keys
ID, Name, Employee Group, Location
When to Use This Form
- When the company creates a new kiosk device for a branch, lobby, gate, store, or warehouse.
- When the verification mode must change from
photo_onlytoface_apiorwebhook. - When admins need to manage the PIN used to protect change-device and exit actions on the kiosk page.
Before You Start
- Decide where the kiosk device will be placed and whether it belongs to one permanent location or a temporary shared location.
- Choose the correct verification mode: proof-photo only, browser face API, or an external webhook engine.
- If webhook mode will be used, prepare the technical engine parameters that must be stored in Engine Config.
Setup Workflow
- Open People & Payroll / Settings / Attendance Kiosk Device.
- Create one record for each kiosk device or kiosk location that should be tracked separately.
- Fill in the device name, employee scope, and location so users can identify it during device selection.
- Choose the Engine Provider that matches the attendance flow you want to run.
- Set the Admin PIN used to protect device changes and kiosk exit.
- Enable camera scanning if this device should scan employee QR or barcode IDs from the camera.
- Use Additional Information if the kiosk should show branch instructions, notices, or queue reminders on the side panel.
- Save the record, then use its
idas the?deviceid=...query when opening the kiosk page.
Key Fields
| Field | User Explanation | Status |
|---|---|---|
ID
id |
Auto-generated device number. This is the value used by the deviceid query on the kiosk page. |
Automatic |
Name
name |
Device name shown in kiosk selection. Use a label that is easy to distinguish, such as “Front Office 1” or “Warehouse Gate”. | Required |
Employee Group
employeegroup |
Optional employee-group filter for the kiosk. Use it when one kiosk should serve only a specific employee group or location team. | Optional |
Location
locationname |
Physical placement name so admins know where the kiosk is installed. | Optional |
Latitude / Longitude
latitude, longitude |
Location coordinates if the company wants to keep a geographic reference for the kiosk device. | Optional |
Engine Provider
engineprovider |
Defines whether the kiosk uses photo_only, face_api, or webhook. |
Required |
Admin PIN
adminpin |
PIN used to protect device changes and leaving the kiosk page. The default starting value is 0000, but it should be changed for production use. |
Recommended |
Scan ID With Camera
scanidwithcamera |
Enable this if the kiosk must scan employee QR or barcode IDs through the camera. | Optional |
Allow Placeholder Verify
allowplaceholderverify |
Use this only when the rollout allows limited verification fallback behavior for a device that cannot run the normal face flow yet. | Optional |
Active
isactive |
Only active devices can be used by the kiosk page. | Required |
Engine Config
engineconfig |
Additional technical configuration for the selected engine, especially for webhook integrations. | Optional |
Additional Information
additionalinfo |
Optional HTML content shown on the kiosk side panel, such as branch notices, queue rules, dress-code reminders, or help contact information. | Optional |
Notes
notes |
Internal remarks about the device, placement, or technical integration. | Optional |
How to Choose the Engine Provider
- photo_only: the simplest mode, used when a proof photo is enough.
- face_api: best when browser-side face matching is needed and face enrollment is already in place.
- webhook: best when the company uses its own face engine or an external vendor service.
Operational Notes
- Each kiosk location should usually have its own device record so logs and attendance proof remain easy to audit.
- Do not leave the Admin PIN as
0000on a production device. - If the PIN field is left blank during edit, the system keeps the previous PIN. PIN changes must be entered intentionally.
- The kiosk page can show the additional information HTML exactly as entered here, so keep the markup simple and mobile-friendly.
- Inactive devices remain in the master data, but they cannot be selected by the kiosk page.
Common Issues
- The kiosk page cannot find the device: check the
deviceidquery and confirm the record exists here. - Face verification keeps failing: review the engine mode, employee face template, and browser camera permission.
- The QR scan button does not appear: enable Scan ID With Camera on the device master.
- Users can change devices too easily: make sure the Admin PIN is set and managed properly.
Menu Location
- People & Payroll / Settings / Attendance Kiosk Device
/form/attendancekioskdevice