Licenses

Open: Licenses in the left menu. This entry is available to system accounts.

A license groups a restaurant's users, locations, configurations, and sessions. Check the license code before changing settings.

View usage

Search for a license and inspect its card. Usage includes locations, users, active sessions, client sessions, tables, API keys, and connected service clients. A connected client count describes connections; it is not proof that a cash register processed an order.

Create and configure a license

1. Choose Add license.
2. Enter the license code and choose Create.
3. Open Settings on the saved card.
4. Set the maximum number of client sessions. A limit of 0 means unlimited.
5. Review cash-register monitoring: maximum failed attempts and connection timeout.
6. Enable staff or guest session recording only when it is appropriate for the venue.

Existing setting changes are saved through their controls; there is no separate publish step. Maximum failed attempts accepts 1–20 and connection timeout accepts 5–300 seconds.

Administrative actions

The demo license has a Recreate demo users action for test-account maintenance. It is not a normal staff onboarding operation. Use Users for staff accounts.

System accounts can delete licenses. Confirm the target and operational impact before deleting a restaurant license.

Restaurant administrators use Configurations for the global monitoring and recording controls available within their license.

Check a settings change

After changing a setting, reopen the license's settings and check the stored value. For a session limit, compare current client-session usage with the intended limit. For connection monitoring, check Messages; increasing a timeout does not repair a disconnected register.

Before asking an operator for help, note the license code, the setting changed, its previous and intended values, and the time of the change. Keep credentials and recorded session contents out of support messages.