Follow this guide to understand how to configure the new Kiosk web app which supports offline clocking (for Humanforce Cloud WFM customers). If you'd like an overview of the features and user-flow in the Offline Kiosk, we recommend reviewing the feature overview article
Offline Clocking is supported via a new Kiosk web application, which is currently in Early Access. As such, not all Kiosk-related settings and features are supported. This new Kiosk can operate in fully online environments also. Contact our support team to request early access.
Pre-requisite: Facial Recognition v2
In order for employees to identify with the new Kiosk web app, they must use facial recognition. Other "log in" modes are not supported at this time.
So before continuing with this set-up guide, ensure the employees who require access to the Kiosk have been set-up with FaceRec v2 access. A guide for migrating from FaceRec v1 to v2 is also available here.
Other identification modes may be supported in future.
Navigating to the New Kiosk App
These steps should be completed by an administrator before any employees attempt to use the Kiosk.
Set the Location for the Kiosk. Using the device/tablet that will act as your HF Kiosk, open the preferred web browser (E.g. Chrome, Safari, Edge, Firefox) and login to your HF cloud instance. Follow this article to set the location against the Kiosk. This will ensure the Kiosk web app will download the correct Location-based clocking settings as well as the employees and rosters only for that location.
Important: If Location is not applied, the Kiosk will download and store significantly more information than may be necessary for typical operation.
Allow for 10MB free disk space per employee. E.g. consider all possible staff that could be rostered at the location. If it works out to be 50 staff, then allow for 500MB storage space for the kiosk to utilize.Now you can navigate to the new Kiosk app page by changing the URL to /kiosk I.e. https://yourcompany.humanforce.com/kiosk (replace yourcompany with your organisation's specific details)
If the tablet is not yet a registered kiosk terminal, you will be prompted to register. If registered, skip this step.
If you already logged into your HF cloud instance in step 1, then you can complete the terminal registration. Once registered, reload the /kiosk page.The browser will begin downloading the Kiosk app content for offline operation.
As suggested by the info-panel, you may want to bookmark the kiosk page and ensure it is the default page/URL that is loaded when the browser is launched. You may also want to set the browser to full-screen mode.After a few minutes (could be up to 10m with larger databases), the Kiosk will be ready for employees to identify via Face Recognition.
Note: Employees should clock-out from the same kiosk they clocked-in, to ensure the clocking events are correctly capture and sync'd with the cloud servers.
Important: The Kiosk app content is cached in the browser. Clearing the browser cache, or using a different browser may require the app content to be downloaded again. If your device's OS supports disabling the clearing of cookies, site data and browsing history, we suggest enabling that restriction.
Additional Configuration
Humanforce Kiosks support a number of system and location-based settings as well as individual user settings that can be controlled via Clock-in Settings. Many of these options, however, are not supported in the new Kiosk web app at this time. Nonetheless, several important settings are available, as outlined below.
The Kiosk will download future shifts within a 72hr window. This is to cover situations where the Kiosk is offline for extended periods.
Clocking features cannot be disabled (because this Kiosk app is designed purely for clocking - not for Employee self-service functions.)
The following steps (except for the Kiosk Location set-up) can be completed from any device.
Location Settings
Keep in mind which Location you have set for the Kiosk in step 1 (above). Now you can open the Location Settings page.
Admin > System Config > Location Settings
“Block clock-in unless rostered at current location” - this setting is not applicable. Non-rostered clocking will always be available. Additionally, employees do not need “Allow non-rostered clock-in” permission.
The options to Enable Area, Event and Function will be respected in the new Kiosk web app.
Shift Transfers are not supported in the Early Access release.
"Display next rostered shift" not supported at this time.
System Settings
Admin > Admin Config > System Settings
Clocking: “Automatically logoff after any clocking action” - this setting is ignored; automatic logoff will always occur.
Clocking: “Block clock-out if overtime consent failed” - this setting is fully supported.
Kiosk: “Kiosk timeout” - this setting is supported. It ensures a user is logged out after the specified time when no activity on the Kiosk is detected
Clock-in Settings
Admin > System Config > Clock-in Settings
Shift Options: Kiosk will respect the “Roster Linking thresholds for Clock-in” settings for detecting and displaying the current (or upcoming) shift.
Shift Options: “Give a waring when an employee starts early for a shift” - this setting is not applicable for the New Kiosk yet.
Breaks: “Allow breaks to be clocked” - this setting is currently not handled. Breaks can always be clocked in the New Kiosk app.
Breaks: “When logging off and no breaks were taken…” - not supported at this time.
Other Options: “Reminder message” - not supported at this time.
Other Options: “Declaration form” - this is fully supported; the Kiosk will respect the checkbox and display the form text accordingly.