If your fixed terminal seems to be logging out or closing on its own, there are a few common reasons why this might happen.
Automatic browser data clearing
Some browsers are set up to automatically clear cookies or browsing data. Since fixed terminals use a browser cookie to recognise the device, deleting cookies will disconnect the terminal.
To check your settings in Google Chrome:
Open your Google Account settings
Go to Data & Privacy
Under History settings, select Activity controls
Check whether any automatic deletion settings are enabled
Disable them if required and save your changes
You should also check your browser settings to make sure cookies aren't being automatically cleared when the browser closes.
The terminal has been opened somewhere else
A fixed terminal can only be active in one place at a time.
If the same terminal is opened on another computer or tablet, the original terminal will automatically disconnect.
If you have multiple clock-in locations, make sure you've created a separate fixed terminal for each device or location.
Internet connection issues
Fixed terminals require a stable internet connection.
If the connection is lost for an extended period, the terminal may disconnect or close unexpectedly. A reliable internet connection will help prevent interrupted clock-ins and terminal shutdowns.
Another user closed the terminal
A manager or administrator may have accidentally (or intentionally) closed the terminal.
If this happens, simply reopen the terminal using a manager or administrator account.
Note: Employees cannot reopen a fixed terminal once it has been closed.
If you're unsure who has access, you can check role permissions under:
Settings > Permission management