Log out safely
Logout checks local transaction state before clearing the terminal session and can be blocked when pending work cannot be safely confirmed. Open the profile menu, choose Log out, and review the confirmation message. Confirm the active branch and signed-in role before taking orders on a shared terminal.
Before you start
- An active POS user or public access appropriate to this page.
- The intended Business Account, branch, and terminal identity are known before operational work begins.
Steps
- Open the profile menu.
- Choose Log out.
- Review the confirmation message.
- Confirm logout.
- If blocked, reconnect and resolve pending transactions first.
Expected result
The authenticated session is cleared only after pending local transactions are resolved or safely blocked. Do not take orders until the displayed identity and branch are correct.
Permissions
- Any signed-in POS user can request logout; pending local transactions can block session clearing.
Troubleshooting
POS does not let staff open the profile menu; they cannot continue to choose Log out.
Verify these conditions before another test: An active POS user or public access appropriate to this page. The intended Business Account, branch, and terminal identity are known before operational work begins. Keep the same branch and record, reopen /billing, and try the blocked action once. If it still fails, stop and send Support the terminal ID, intended branch, visible message, and time; omit passwords, PINs, codes, and reset links. Record the visible response when staff open the profile menu.
The signed-in identity, branch, terminal, or navigation remains wrong after the final checkpoint: If blocked, reconnect and resolve pending transactions first.
Check the account identity, branch label, terminal readiness, connection, and pending-transaction indicator. If pending work blocks logout, reconnect and resolve those transactions first. Retry logout once only after the pending count clears. If the user remains signed in, provide Support 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.Unlock an idle POS session
Authenticated POS sessions lock after the configured inactivity period and require reauthentication before the app becomes interactive again.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.
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