Skip to content

Login attempts

Team → Login attempts is the sign-in log for your restaurant. The screen describes itself as Monitor sign-in activity by user, status, date, and IP, and it is the first place to look when somebody says they cannot get in, or when you want to know whether anyone has been trying.

Reading it needs the same permission as managing users, so in practice the owner and managers see it.

Column What it tells you
Time When the attempt happened
User Which account was being signed into
IP The address the attempt came from
Platform Dashboard, POS app, or wherever else the attempt originated
Device The device as it identified itself
Browser / OS For dashboard sign-ins
Reason Why a failed attempt failed

Filters across the top: User ID, status (All Status, Success, Failed), IP Address, From Date and To Date. Narrow by user and status first — a single person’s failures are usually a forgotten password or a changed PIN, while the same failure across several accounts from one address is something else.

With nothing matching, the list reads No login attempts found.

One person, several failures, then a success. Normal. They mistyped, then got it right.

One person, failures that stop dead. Likely a lockout. Five wrong PIN guesses lock that identity for 15 minutes; the person can simply wait, or you can set them a new PIN on the Users screen. A new PIN cannot be one of their last three.

Failures against a name that no longer works here. Soft-delete the account if you have not already, so the login stops working while their history stays intact.

Repeated failures from one address against several accounts. Treat that as an attack on your restaurant. Change the passwords on any account that has been hit, give counter staff new PINs, revoke device sessions you do not recognise on Devices, and tell RestroManage support the address and the time window.