Sign-in problems

What is the problem?

Sign-in fails with "Could not sign in", the app keeps bouncing back to the login screen, or the screen that opens is not the one you expected.

Why it can happen

• The account was never activated (new invite not completed) or was disabled.
• The wrong sign-in screen for the job (POS vs admin console).
• A typo, or a stale session that expired overnight.
• The whole restaurant is suspended at platform level.

How to check it — work through these, in order

1. 1
   Right screen for the job? Cashiers sign in at the POS; kitchen staff, waiters, managers and owners at the admin console. Each login page says who it is for.
2. 2
   Activated? A brand-new account must set its password from the activation email first — see Activate your account. Until then, sign-in cannot work.
3. 3
   Exact email, correct password. Emails are not case-sensitive; passwords are. Watch for autocorrect on phone keyboards.
4. 4
   Disabled account? If access was revoked when someone left, their sign-in stops working by design — the owner would know (Disable a user).
5. 5
   Whole restaurant locked out? If *everyone* fails at once with the same error, the account may be suspended — see Account suspended.

Sessions

Sessions expire after inactivity (overnight on a till is normal) — the app simply returns to the login screen. Sign in again; nothing is lost. Queued offline sales survive a sign-out and sync for the account that made them.

What NOT to do

How you know it is fixed

You land on the right screen for your role (cashier → till, kitchen → KDS, everyone else → their best page).

Still not working?

Tell your owner/manager first — most sign-in problems are an unactivated or disabled account. If the account looks fine, contact support with the email on the account and the exact error.