Operator kiosk

HTF supports kiosk users that belong to one station. A kiosk account is separate from a human team account and does not grant project-wide access.

Create an account

1. With kiosk-accounts:manage permission, open the project's Kiosk users page. Organisation owners/admins and project Admins have this permission; an appropriate custom role can also grant it.
2. Select New kiosk user, choose the station, and enter a username.
3. Save the one-time password shown after creation.
4. On the jig, open the station's /stations/{stationId}/kiosk page and sign in with that username and password.

Use a dedicated browser profile for the jig. Do not sign in with a human HTF account in that profile. To revoke kiosk access, disable or delete the user, or reset its password. End kiosk session revokes the current session.

Session lifetime

A dedicated kiosk session uses a persistent cookie backed by the HTF database. It expires 30 days after sign-in; activity does not extend that expiry. The operator must sign in again after expiry or revocation. The session survives application deployments and browser restarts when the browser profile retains its cookies. Clearing cookies requires another sign-in.

Human web sessions use WorkOS session refresh. That refresh does not extend a dedicated kiosk session. For HTF v0.1.5, refresh the portal to load the new UI; no station reboot or station software update is required. The station runtime pin and MQTT contract are unchanged.

Recover after a tab change or disconnect

HTF v0.1.4 restores stage progress when you return to the station screen and retains active lane state for a restored kiosk session. After reconnection, the kiosk can recover a run that was already active at sign-in, including a completion that arrived while the browser was disconnected. Check the restored outcome before starting another run for the same DUT.

A kiosk user can only recover runs that overlap the current session on its assigned station. Runs completed before sign-in and project-wide history are unavailable. Recovered logs contain only entries received by the server since sign-in. Server completion time defines this boundary, so a station clock offset does not change which completed runs the session can see.

Kiosk accounts cannot browse DUT capture history or capture issues. Use a human account with the appropriate roles and permissions to review production evidence.

Use Retry to keep another attempt in the same test sequence. Starting a normal new test creates a new sequence, even if its DUT ID is unchanged.

For a physical production jig, configure the operating system as a dedicated single-application session and keep maintenance access separate from the operator session. Your IT team should validate the OS lockdown on the actual hardware before handover.