Overview and audience
Kiosk Attendance is a paid Prospeno add-on for shared-device attendance.
A company can configure one or more kiosk terminals for offices, project sites, warehouses, or other active work locations.
Employees use a four-digit PIN to check in or out. Depending on kiosk settings, they may also capture a selfie and select a project.
When offline mode is enabled, attendance events are stored on the kiosk device and synchronized after the connection returns.
| Role | Access |
|---|---|
| Admin | Admins can create and configure kiosk setups, select locations, configure attendance rules, assign employee PINs, control project selection, allow Manager or Supervisor launch access, launch the kiosk, review kiosk status, manually synchronize queued events, and clear kiosk device data. |
| Manager | Managers cannot change kiosk settings. They may launch an approved kiosk when the kiosk configuration allows Manager launch access. |
| Supervisor | Supervisors cannot change kiosk settings. They may launch an approved kiosk when Supervisor launch access is enabled. |
| Employee | Employees do not configure or unlock the kiosk. They use the shared terminal after an authorized person launches it. |
Role
Admin
Access
Admins can create and configure kiosk setups, select locations, configure attendance rules, assign employee PINs, control project selection, allow Manager or Supervisor launch access, launch the kiosk, review kiosk status, manually synchronize queued events, and clear kiosk device data.
Role
Manager
Access
Managers cannot change kiosk settings. They may launch an approved kiosk when the kiosk configuration allows Manager launch access.
Role
Supervisor
Access
Supervisors cannot change kiosk settings. They may launch an approved kiosk when Supervisor launch access is enabled.
Role
Employee
Access
Employees do not configure or unlock the kiosk. They use the shared terminal after an authorized person launches it.
Permission matrix
Kiosk Attendance must be active for the company before its settings can be saved or used.
When the module is not enabled, Prospeno shows a locked module state.
Disabling the module does not remove previously synchronized attendance records from Attendance Logs.
Setup workflow
Admins can create one or more kiosk setups.
Use Add kiosk or Add another kiosk to create additional terminals.
- Kiosk name
- Assigned location or site
- PIN attendance
- Selfie requirement
- Offline mode
- Allowed employees
- Active status
- Project assignment mode
- Default project
- Manager launch permission
- Supervisor launch permission
Kiosk name
- Enter a clear device or site name.
- Examples: Main Office Kiosk, Warehouse Entrance, Project Site A, North Gate Tablet
- A clear name helps Admins distinguish multiple shared devices.
Assigned location
- Every kiosk must be connected to an active location before launch.
- The assigned location helps identify where kiosk attendance is expected to occur.
- Create and verify locations under the Locations page before configuring the kiosk.
Attendance rules
PIN attendance enabled
- Allows employees to identify themselves using a four-digit kiosk PIN.
Selfie required
- Requires the employee to capture a selfie during the kiosk attendance flow.
- The device must have a working camera and browser permission.
Offline mode enabled
- Allows attendance events to be stored on the local device when the kiosk cannot reach Prospeno.
- Queued records synchronize when connectivity returns.
All active employees
- Allows all eligible active employees to use the kiosk.
- Turn this off when only selected employees should be permitted.
Kiosk active
- Controls whether the kiosk setup can currently be launched and used.
When All active employees is disabled, choose the employees permitted to use the kiosk.
Employees outside the allowed list cannot complete the PIN flow on that kiosk.
This setting does not change their company role or project assignments.
PIN and security panel
Assign each employee a unique four-digit PIN.
Select Save PIN after entering the PIN.
PIN requirements:
PINs are hashed and are not displayed again after saving.
Admins should assign a new PIN when an employee forgets it or when its privacy may have been compromised.
- exactly four digits
- unique within the kiosk context
- should not be easily guessed
- should not be shared between employees
The kiosk terminal displays:
Enter your PIN
The keypad contains:
An invalid PIN displays a generic message such as:
PIN not recognized. Please try again.
The generic message avoids revealing which employee accounts exist.
- digits 0–9
- clear or backspace
- confirm
Three-strike lock
After three failed PIN attempts, the terminal temporarily locks for approximately 30 seconds.
This helps reduce repeated PIN guessing.
The server also applies additional request-rate protection.
After the lock period ends, the employee may try again.
Before employees can use the kiosk, an authorized user opens the kiosk launch page.
The unlock screen may show: Kiosk unlock, Authorized session verified
An Admin can unlock the kiosk.
Managers or Supervisors may unlock it only when their launch permission is enabled for that kiosk.
After authorization, Prospeno opens the shared terminal.
Project-assignment modes comparison
General Work only
- All kiosk attendance is recorded as General Work.
- General Work does not affect the profit of an individual project.
- Use this for office, warehouse, or company-wide work that is not tied to a project.
Ask employee to choose project
- After the employee enters the PIN, the terminal asks for a work assignment.
- The employee may see: General Work, eligible projects, Confirm Check-in
- Use this when one kiosk serves employees working on different projects.
Use default project
- The kiosk automatically connects attendance to the configured default project.
- Use this when the device belongs to a dedicated project site.
- Confirm the default project before launching the kiosk.
Check-in/check-out workflow
Select Launch Kiosk Mode after the setup is complete.
The kiosk opens through a launch URL associated with the selected kiosk configuration.
For a cleaner shared-device experience:
- use fullscreen mode
- keep the browser on the kiosk page
- prevent employees from using the device for unrelated activity
- keep the device charged
- confirm the camera works
- test offline and online behavior
- 1
Enter the four-digit PIN.
- 2
Select the project when required.
- 3
Capture or confirm the selfie when required.
- 4
Review the attendance action.
- 5
Select Check In.
- 6
Wait for the success message.
The terminal may display: Ready to check in, Check In, Checked in successfully.
After success, the terminal returns to the PIN screen automatically.
- 1
Enter the employee PIN.
- 2
Capture or confirm the selfie when required.
- 3
Review the attendance action.
- 4
Select Check Out.
- 5
Wait for the success message.
The terminal may display: Ready to check out, Check Out, Checked out successfully.
The completed check-out allows the attendance record to calculate final hours.
When Selfie Required is enabled, the employee may see: Capture, Retake, Continue
The kiosk uses the device’s front-facing camera where supported.
A captured selfie becomes attendance evidence after synchronization.
Selfie capture may fail when:
Test the actual kiosk device before field deployment.
- camera permission is denied
- another application is using the camera
- the browser does not support the required camera feature
- the device camera is unavailable
- the browser is in a restricted mode
Offline and synchronization panel
When offline mode is enabled, kiosk events are stored in the browser’s local device storage.
Queue statuses may include:
The kiosk attempts to synchronize when the internet connection returns.
Offline mode helps keep attendance operating during temporary outages, but the record does not appear in central web pages until synchronization succeeds.
- Pending
- Syncing
- Synced
- Failed
Offline attendance is not visible centrally until synchronized
While the kiosk is offline:
- valid kiosk activity may be queued locally
- selfies may remain on the local device until sync
- attendance may not yet appear in Attendance Logs
- the Project Command Center and Timesheet may not yet reflect the work
- Admins should avoid clearing browser data
- employees should not repeat successful offline actions unnecessarily
After connectivity returns, use Sync now when automatic synchronization has not completed.
The Admin status panel may show:
- Connection
- Online or Offline
- Pending sync
- Failed sync
- Last sync
Available actions may include:
- Sync now
- Refresh Sync
- Open Kiosk Settings
- Enter fullscreen
- Exit fullscreen
- Clear kiosk device data
- Exit kiosk
- Close
Select Sync now to attempt uploading queued attendance events.
Use it when:
Do not repeatedly close or refresh the browser while a synchronization is actively running.
- the device has returned online
- pending records remain
- automatic synchronization appears delayed
- failed events require another attempt
A failed event remains in the device queue until another synchronization attempt or approved cleanup action occurs.
Possible causes include:
Review the current kiosk configuration before clearing failed records.
- unstable internet connection
- expired kiosk authorization
- invalid or archived location
- changed employee eligibility
- server validation failure
- corrupted local data
Clear kiosk device data
Clear kiosk device data removes kiosk information stored on the shared browser.
Use it only when:
Clearing device data may permanently remove unsynchronized attendance and selfie evidence.
Synchronize all pending records first whenever possible.
- the kiosk is being retired
- the device is being transferred
- local data is corrupted
- support instructs the Admin to reset the device
Device and browser requirements
Device and browser requirements
A kiosk device should have:
A tablet or large phone is generally easier to use than a small handset.
- a modern supported browser
- JavaScript enabled
- local browser storage
- a stable camera when selfies are required
- internet connectivity for synchronization
- enough local storage for offline events
- permission to use the camera
- a screen large enough for the keypad and capture flow
Local device security
Local device security
Offline mode stores attendance information on the kiosk device.
This may include:
Use a company-controlled device.
Do not deploy Kiosk Attendance on a public or personally shared browser without appropriate security controls.
- locally cached PIN verification data
- queued attendance events
- selfie files
- kiosk configuration
Fullscreen and shared-device use
Multi-kiosk operation
A company may configure multiple kiosks.
Each kiosk can have its own:
Use separate kiosk setups for different offices, warehouses, entrances, or project sites.
- name
- location
- allowed employees
- project assignment mode
- default project
- selfie rule
- offline rule
- launch permissions
Multi-location operation
Each kiosk is assigned to one location.
Different kiosks may use different locations.
Before launch, verify that the selected kiosk is connected to the correct physical site.
A kiosk assigned to the wrong location may produce misleading attendance evidence.
Attendance, Project Labor, Timesheet, and Payroll relationship
Attendance Logs
- After synchronization, kiosk activity becomes a normal attendance record with Kiosk as its source.
- Admins and authorized Managers can review the resulting attendance in Attendance Logs.
- The record follows the same status and approval rules as other attendance sources.
Project Labor
- When kiosk attendance is assigned to a project, approved attendance contributes to project labor cost.
- General Work does not affect an individual project’s profit.
Timesheet
- Synchronized kiosk hours appear in Timesheet under the employee and work date.
- Open or unsynchronized records may not yet show final hours.
Payroll
- Salaries & Payroll may use approved kiosk attendance through the same attendance pipeline used by mobile and web records.
- The kiosk does not create a payroll run directly.
Locations
- Every kiosk requires an assigned location.
- Locations controls the site definition and supports attendance evidence and geofence rules.
- Changing or archiving a kiosk location may affect future kiosk usage.
Kiosk Attendance
- Designed for a shared company device.
- Use when employees do not have compatible phones.
- Use when the company wants one controlled attendance terminal.
- Use when the worksite has a shared entrance.
- Use when centralized selfie capture is preferred.
Prospeno Field
- Designed for an individual employee’s mobile device.
- Use when employees need individual mobile attendance and field workflows.
Profit-effect callout
Kiosk Attendance affects project profit only through synchronized, valid, approved project attendance.
The process is:
Kiosk event → Attendance record → Completed check-out → Approval → Allocated project labor cost
General Work does not affect individual project profit.
Pending, open, failed-to-sync, and rejected attendance are not treated as approved project labor cost.
Critical offline-data warning
Clearing unsynchronized browser data
Clearing browser data can remove unsynchronized attendance stored on the kiosk device.
Offline records are not centrally visible until synchronized.
- Selfie capture requires browser camera permission.
- Offline records are not centrally visible until synchronized.
- Clearing browser data can remove unsynchronized attendance.
- Mobile Field App attendance is separate from kiosk offline mode.
Recommended rollout
- 1
Create and verify the location.
- 2
Enable the Kiosk Attendance module.
- 3
Create one kiosk setup.
- 4
Assign the correct location.
- 5
Choose the project-assignment mode.
- 6
Assign allowed employees.
- 7
Create employee PINs.
- 8
Test camera permission.
- 9
Test check-in and check-out online.
- 10
Test offline queue and synchronization.
- 11
Review records in Attendance Logs.
- 12
Deploy additional kiosks after the first setup is stable.
The shield or Admin control on the terminal is restricted.
Unauthorized users may see: Admin access required.
Use the Admin controls to review status, synchronize, exit, or return to settings.
Employees should not have access to these controls.
When the Kiosk Attendance module is cancelled, disabled, or expires:
- new kiosk use may be blocked
- kiosk settings may become unavailable
- historical synchronized attendance remains in Attendance Logs
- existing project labor history is preserved according to normal retention rules
Important limitations
- Kiosk Attendance is a paid add-on.
- Only Admins can configure kiosk settings and employee PINs.
- Managers and Supervisors can launch only when explicitly allowed.
- Employees cannot unlock or administer the kiosk.
- A kiosk must have an assigned active location.
- PINs are exactly four digits.
- Three failed PIN attempts trigger a temporary lock.
- Selfie capture requires browser camera permission.
- Offline records are not centrally visible until synchronized.
- Clearing browser data can remove unsynchronized attendance.
- The shared device stores sensitive local attendance data.
- Server-side PIN rate limiting may behave differently across distributed server instances.
- Mobile Field App attendance is separate from kiosk offline mode.
- Billing, proration, and subscription rules are managed through Module Marketplace and Company Subscription.
Where to find help
Use the ? button in the web application for the current page guide, Getting Started, Module Guides, and Contact Support.
Related links
Jump to the module, marketplace, or broader help resources.