Search documentation

Search pages and sections of the Rona docs

Back to homeDocs Hub

Getting Started

  • Introduction
  • Setup
  • First Steps
  • Dashboard

Core Modules

  • Inventory
  • Sales
  • Manufacturing
  • Quality
  • Traceability
  • Finance
  • Workforce
  • Kiosk

Admin & Permissions

  • Users
  • Roles
  • Organization
  • Audit Logs

Rona AI

  • Overview
  • Queries
  • Reports
  • Tracing

API Reference

  • Authentication
  • Inventory API
  • Sales API
  • Manufacturing API
  • Finance API

Version

v2.6 · Real-time lot tracing

Core Modules / 08

Kiosk

The Kiosk turns any tablet or shared device into a secure attendance terminal. Employees clock in, start breaks, end breaks, and clock out with their employee ID plus a short passcode or a fresh face scan — no personal login required at the terminal.

ATTENDANCESHARED DEVICEFACE RECOGNITION

Key features

  • Dedicated terminal that runs without a user session
  • One-time device credential ties the tablet to your organization
  • Employee ID plus a short numeric passcode
  • Optional EID plus face capture with server-side matching
  • Clock in, clock out, break start, and break end
  • Large touch-friendly actions for shop-floor tablets
  • Success screen with automatic reset for the next employee
  • Live status showing whether a device is active
  • Rate limiting to protect against repeated attempts

How it works

01

Register the device

An administrator registers a kiosk in the workspace and receives a device credential that is shown only once.

02

Activate the terminal

Open the kiosk terminal on the tablet and enter the device credential. The device remains signed in until its session expires, is ended, or the kiosk is deactivated.

03

Employee identifies themselves

On the idle screen the employee enters their EID, then either a five-digit passcode or selects Capture face and uses the camera preview. Capture alone is not verification.

04

Choose an attendance action

The employee taps Clock In, Clock Out, Start Break, or End Break. The event is recorded against their attendance record.

05

Confirm and reset

A success screen shows the employee name, action, and time, then the terminal returns to the idle screen for the next person.

Terminal screens

Screens
SetupShown until a valid device credential is entered. Registers the tablet as a kiosk for the organization.
IdleThe main entry screen — employee ID, passcode, or face sign-in, and the four attendance actions, with a live clock.
SuccessConfirms the employee name, the action performed, and the recorded time, then resets automatically.

Auto-reset

After a successful punch the terminal waits briefly, then clears the form so the next employee can step up — no manual sign-out needed.

Attendance actions

Available actions
CLOCK_INThe employee starts their work day
CLOCK_OUTThe employee finishes their work day
BREAK_STARTThe employee begins a break
BREAK_ENDThe employee returns from a break

Face sign-in

Enter your employee ID, then select Capture face as an alternative to a passcode. A visible camera preview lets you position your face and capture or cancel. face-api.js computes a numeric descriptor locally; camera frames are not uploaded. Capture does not verify identity. When you choose an attendance action, the terminal sends your EID, descriptor, and event type to the server. The server matches against that employee’s active enrollment in the kiosk organization before recording attendance. Enrolled descriptors are never downloaded to the kiosk. The pending scan expires after 30 seconds and is cleared when the EID changes or a punch is attempted, whether it succeeds or fails. Each subsequent face punch requires a fresh scan. Device sessions are separate from face matching; a face mismatch does not end the device session.

Enrollment
EnrollSign in to your own account and open /staff with hr.attendance.clock permission. Review the biometric notice, consent, and capture your own face for your linked employee in the current organization.
One active faceEach employee keeps a single active face; enrolling a new one automatically revokes the previous.
RevokeStaff can revoke their own active enrollment in /staff at any time, disabling it for subsequent server matches.
PrivacyThe 128-value descriptor is sensitive biometric data sent to the server for storage and matching, with consent. Camera frames stay in the browser. Ask your organization about retention, access and deletion; revocation disables matching, not necessarily record retention.

Face recognition is not absolute

Facial recognition can be defeated by photos, videos, or identical twins, and is not a guarantee of identity. Accuracy also depends on lighting and camera quality. Treat face sign-in as a convenience layer, keep passcodes available, and use it where the terminal can be supervised. There is no liveness guarantee. Employees must register their own face in /staff before using it; no kiosk enrollment-list reload is needed because matching happens on the server.

Native terminals (Rona Kiosk app)

For dedicated hardware, install the Rona Kiosk app on a ZKTeco Android attendance terminal. Faces and fingerprints are enrolled and matched on the terminal by the device's biometric engine, so employees simply look at the camera or place a finger — no employee ID is typed. The server receives only who punched, the action, the verification methods used and the time.

01

Pair by QR code

Register a kiosk in the workspace and scan the QR code shown with the device credential from the terminal. The terminal creates a hardware-backed key and signs every request with it.

02

Choose a verification policy

Per kiosk: face only, face or fingerprint, face and fingerprint, card and face, or card and fingerprint. A card (RFID/NFC) is only ever a second factor and is never accepted on its own.

03

Enroll in Supervisor mode

An HR user creates a one-time enrollment code on the Kiosks page and enters it on the terminal to enroll faces, fingerprints and cards. Templates are stored encrypted and synced to every terminal of the organization.

04

Works offline

If the connection drops, punches are queued on the terminal and uploaded with their original time once it reconnects (up to 72 hours old). Each punch carries a unique ID, so retries are never recorded twice.

Kiosk credentials per employee

Open Employees → Kiosk credentials to see enrolled templates and cards and to revoke them. Terminals delete revoked credentials on their next sync. Attendance shows the source kiosk and verification methods for each punch.

Device credentials

Device data
NameHow the kiosk is identified (e.g. Main Gate Tablet)
Device credentialIssued at registration, shown only once, and stored securely
StatusACTIVE or INACTIVE
Registered atWhen the device was added
Last seenThe last time the device contacted the server

Store the credential immediately

The device credential is displayed a single time when the kiosk is registered or rotated. Copy or download it then and enter it on the tablet — it cannot be retrieved later. If it is lost, rotate the credential to issue a new one.

Security

  • Employees never need a personal login on the shared device
  • Each punch requires the employee ID and a five-digit passcode (or a face scan)
  • The server matches each EID and fresh descriptor against that employee’s active enrollment; kiosks never download enrolled descriptors
  • Enrolled faces can be revoked per employee at any time
  • Authentication attempts and punches are rate limited
  • Device sessions expire and can be revoked by deactivating the kiosk
  • Only administrators with kiosk permissions can manage devices

Permissions

Managing kiosk devices is governed by role-based access control. A role must hold the relevant permission before it can register or manage terminals.

Kiosk permissions
kiosk.readView kiosk devices
kiosk.createRegister new kiosk devices
kiosk.activateActivate kiosk devices
kiosk.deactivateDeactivate kiosk devices
hr.credential.readView employee biometric templates and cards
hr.credential.enrollCreate enrollment codes for terminal Supervisor mode
hr.credential.revokeRevoke employee biometric templates and cards

Best practices

  • Name devices by physical location (e.g. Reception, Warehouse A)
  • Keep the terminal credential out of shared notes and chat
  • Deactivate any tablet that is lost, replaced, or retired
  • Mount devices where they can be supervised
  • Check last-seen regularly to spot offline or misconfigured tablets
  • Give kiosk management permissions only to administrators who need them
Continue

Explore workforce

Employees, attendance, shifts, departments, and positions — the records that every kiosk punch feeds into.

Workforce module
PreviousWorkforceNextUsers