Signing in and out

The KDS has no login form of its own. It uses your SSP Manager account, so one sign-in covers Manager, the KDS and the other SSP web apps in the same browser.

Sign in

1. Open kitchen.ssppos.com. If nobody is signed in you see the welcome screen with one button: Sign in with SSP.
2. Tap it. SSP Manager's login page opens; sign in with the kitchen account (email and password, or Google / Apple if the account uses them).
3. You come straight back to the KDS.

If your account can see one location, the board opens immediately. If it can see several, the Select a Location screen lists them as cards — name, city and address — and Select Location opens that board. The URL then ends with the location's number, so a bookmark to that address skips the choice next time.

One account per screen

Sign each kitchen screen in with a dedicated kitchen account rather than a manager's own login. The screen stays signed in until someone signs it out, and anything done on it is recorded against that account.

Sign out

Tap the avatar (your initials, top-right) and choose Sign out. A confirmation asks you to be sure — "This closes the tablet. A manager will need to sign in again." — because signing out:

• signs the KDS out,
• signs SSP Manager and the other SSP web apps in this browser out as well, since they share the login,
• but not the Waiter app or the NFC configurator, which keep their own sessions.

If the sign-out fails (no connection, for example) a red message says Couldn't sign out. Please try again. and the screen stays signed in.

When the KDS signs itself out

If the session has expired or been revoked — a manager changed the password, the account was deactivated, or the token simply timed out — the next thing the screen tries to do takes it back to the welcome screen. Tap Sign in with SSP again. No work is lost: every tap that had already reached the server stays recorded.

A refusal is different from an expired session. If the account is signed in but lacks the ability for what you tapped (for example 86-ing a dish), the KDS stays on the board and shows the refusal as a red message. See Troubleshooting.

What this device remembers

Some choices are stored on the device (in the browser), so they survive a reload and a sign-out, and are not shared with other screens:

Remembered on this device	Scope
Which stations the screen shows	Per location. A station deleted in Manager is dropped automatically.
The sort order of the board, and any custom drag order	Per location and per tab
Light / dark / system theme	Whole browser

Some things are deliberately not remembered and reset on every reload:

Resets on reload	Why
The tab — the board always opens on Active	The live board is the safe default
Mute	A muted screen that stayed muted overnight would miss the first ticket of service
Sound unlock — you tap Sound is off — tap to enable again	Browsers require a tap before they allow sound
Which strips are open (Ready for handoff, Later today, Coming later) and which grouped lines are split	Working state of the moment

Clearing the browser's site data forgets everything in the first table; set the stations again.