Unlock an idle POS session
Authenticated POS sessions lock after the configured inactivity period and require reauthentication before the app becomes interactive again. Return to the locked terminal, enter the requested credentials in the reauthentication dialog, and submit once and wait for the dialog to close. Confirm the active branch and signed-in role before taking orders on a shared terminal.
Before you start
- The same POS user who owns the locked session is present.
- The requested reauthentication credential is available without sharing it with another staff member.
Steps
- Return to the locked terminal.
- Enter the requested credentials in the reauthentication dialog.
- Submit once and wait for the dialog to close.
- If reauthentication cannot complete, use the offered safe logout path.
Expected result
The reauthentication dialog closes and the existing session becomes interactive without changing user or branch. Do not take orders until the displayed identity and branch are correct.
Permissions
- The credentials of the POS user who owns the locked session; another user must use safe logout and sign in separately.
Troubleshooting
Staff cannot return to the locked terminal because the control is missing, disabled, or rejected before they enter the requested credentials in the reauthentication dialog.
A safe retry starts by confirming: The same POS user who owns the locked session is present. The requested reauthentication credential is available without sharing it with another staff member. Check those conditions on /billing and repeat only the blocked step once. Preserve the screen and ask Support to review the terminal ID, intended branch, visible message, and time; omit passwords, PINs, codes, and reset links. Capture the displayed state produced when staff return to the locked terminal.
The signed-in identity, branch, terminal, or navigation remains wrong after the final checkpoint: If reauthentication cannot complete, use the offered safe logout path.
Check the account identity, branch label, terminal readiness, connection, and pending-transaction indicator. Correct the identity or session condition, then retry once. Stop if the branch or user still differs. If reauthentication cannot complete, use the offered safe logout path. Ask Support to review the terminal ID, intended branch, visible message, and time; omit passwords, PINs, codes, and reset links.
Related articles
Use the assigned email and password to open the register; the returned role and capabilities determine which screens and actions appear.Install the POS app
Install is offered only when the browser reports that this site can be installed as a Progressive Web App.Switch the active branch
Use the profile menu to change branch; TajerGo blocks switching when local pending transactions could be attributed to the wrong branch.Change the POS language
Use the profile menu language control to change the interface language for the current terminal session.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback