# Connect and manage restaurant devices

**Console: Settings → Location settings → Devices.** For the authorised
restaurant manager. Confirm the working location and identify the physical
phone, tablet, or till before editing its record.

## Add and connect a device

1. Select **Add device**, enter a recognisable **Device name**, such as “Front
   counter tablet”, and review **Active**.
2. Select **Create**, wait for the saved result, and find that device in the
   list. Creating its record does not sign the physical device in.
3. Install the supported TablePort staff app and open it on the intended device.
4. Open the device's login action in the Console and select **Generate QR
   code**. Scan it in the app, or use **Open in TablePort app** on the intended
   device when appropriate. If the code expires, use **Generate new QR**.
5. Alternatively, follow **Enter device ID**: enter that device's ID in the app
   and complete SMS verification. SMS goes to the location mobile or the
   configured **Custom login mobile**.
6. Verify the app's actual location, staff identity, and access. Check a small
   read-only task and the device's session record before handing it to staff.

Login QR codes, links, verification codes, and staff PINs are access
credentials. Do not put them in documentation, shared screenshots, chat prompts,
or public support messages. A device record or an active session alone does not
prove its network, printer, payment reader, or staff permissions work.

## Review the device settings

Expand the device and check the relevant tab:

| Tab      | Review                                                                                             |
| -------- | -------------------------------------------------------------------------------------------------- |
| General  | Device name and **Device active**                                                                  |
| Defaults | **Default employee**, **Default floor plan**, and **Default printer**, where choices are available |
| Security | **Custom login mobile**, **Auto sign-out**, **Disable time tracking**, and **Active sessions**     |
| Kiosk    | Customer-facing self-order configuration, when that mode is intended                               |

Use **Save changes** for intended configuration edits, then reopen and compare
the saved values. Defaults are not additional staff permissions. Verify the
actual selected employee, floor plan, and printer in the app after connecting.

**Auto sign-out** signs staff out after inactivity; choose a duration consistent
with restaurant practice and test it before service. **Disable time tracking**
prevents clock-in/out on that device; it does not end an existing shift or
repair pending clock actions. Review [Time tracking](/staff/time-tracking)
first.

[Kiosk mode](/settings/location/kiosk) is for guest self-ordering, not a
shortcut for staff sign-in. Review its card provider, exit PIN, order types, tip
screen, idle timeout, and intended kiosk terminal before use. Keep its PIN
private and verify the complete customer flow through an agreed safe test before
service. A saved kiosk setting is not proof of payment or printer readiness.

## Review sessions and remove access deliberately

The device's **Active sessions** list can show client/app information, version,
activity, and expiry. Check the actual session and physical device with the
shift leader before **Revoke**. **Revoke all** concerns all sessions on this
device record; it is separate from revoking one listed session.

Read the confirmation and verify the result. Revoked devices need to
authenticate again. Before planned revocation, deactivation, deletion, or
sign-out, inspect [Sync status](/troubleshooting/connection-and-sync), uncertain
payments and pending clock actions on the original device. Preserve
unsynchronised work and coordinate service, printer-host responsibilities, and
replacement access.

**Device active** changes the saved configuration; review any deactivation
confirmation and save the intended change. **Delete device** has a permanent
confirmation and revokes its sessions. Do not delete or recreate a device to
force an uncertain order, payment, or clock record to sync. For suspected
unauthorised access, have the responsible manager coordinate access removal and
support recovery together.

## If connection or saving fails

- **SMS missing:** verify the saved location/custom login mobile with the
  manager. Do not redirect verification to an unrelated person's number.
- **QR failed or expired:** keep the same device record, read the error, and use
  the offered retry or new-code action. Do not create another device record
  simply because the login did not finish.
- **Controls missing:** check role, location, available records, and app
  release. Do not use another staff member's PIN to obtain the expected screen.
- **Save outcome uncertain:** reopen the original device and inspect its saved
  settings and sessions before repeating a change.

Escalate with location, device name, intended change, app version, displayed
state, exact error, and pending-work status through an authorised channel.
Exclude login QR/link contents, verification codes, PINs, private network
addresses, and guest/payment details from captures.

See [Printer recovery](/troubleshooting/printers),
[Payment recovery](/troubleshooting/payments), and
[Time record recovery](/troubleshooting/time-records).