Cashier Roles & Permissions
HandyCafe uses role-based access control (RBAC) to manage what each staff member can see and do within the system. Every cashier is assigned a role and that role determines their exact permissions across the entire application.
Plan Availability
HandyCafe Genesis Pro includes the complete role and permission system described below. Manager roles, custom roles and several active cashiers are all available.
Where Staff Is Managed
Open Settings, then Staff. The page has two tabs:
- Cashiers -- The staff accounts that can sign in from the cashier login screen.
- Roles & Permissions -- The roles and the permission matrix.
The Shifts options sit on the same page. See Shift Management below.
Role Types
When you add or edit a cashier, the role is chosen from four types:
Admin
The Admin role grants unrestricted access to every feature in the system. Admins can manage cashiers, view all reports, modify settings and perform any operation. This role is intended for cafe owners and senior managers who need full control.
There is always at least one Admin account in the system. The last Admin is marked Last Admin and cannot be deleted, demoted or deactivated until another user is promoted to Admin. The Admin role is read-only in the permission matrix.
Manager and Cashier
Manager and Cashier are built-in roles. Their permissions can be edited in the matrix. The roles themselves cannot be deleted. When you change a built-in role that is already assigned to staff, HandyCafe asks whether to apply the change to every cashier using it.
Custom
Custom roles are the roles you create in the Roles & Permissions tab. Choose Custom as the role type in the cashier dialog, then pick the role. A custom role can be edited and deleted.
Accounts created before the current role system may still show a Default role type. It is kept for those accounts but is not offered for new ones.
Permission Groups
The Roles & Permissions tab shows a matrix: each role is a column and each permission is a row with a checkbox. There are about 76 permissions in 11 groups.
| Group | What it covers |
|---|---|
| Computer Management (18) | Manage Computers (the Computers page itself), pause and resume, cancel a pending session, transfer a session payment to another PC, add time, power actions, remote management, screenshot, application control, run command on computer, file transfer, delete files on the client, send message, guest tabs, edit the computer record, close the client application, open the computer details panel and sign in on a client machine. |
| Members (13) | View, Add, Delete, Update, Show Emails, Show Phones, Sell package, Load money, Sell time, Adjust time, Pay debt, Refund / cancel purchase, Change password. |
| Consoles (5) | View, Add, Delete, Update, Pause / resume session. |
| Logs (4) | View, Show Full Logs, Show Today's Logs, Delete. |
| Logs Page Tabs (8) | Which Logs tabs the role sees: System Logs, Transactions, Recycle Bin, Audit, IP Logs, Tamper Events, HWID Blacklist, Steam VAC. |
| Reporting (3) | View, Show Full Reports, Show Today's Reports. |
| Sales, Stock & Payments (4) | Manage, Add, Delete, Update. |
| Bills (8) | Bills page, open, rename, move an order onto a bill, collect and close, partial payment, cancel without collecting, see closed bills. |
| Orders (5) | Orders Page, add an order item, remove an order item, approve and close, cancel without collecting. |
| Stock (4) | Stock Page, record goods received, adjust stock manually, set the critical level. |
| Page Visibility (4) | Cloud page, AI page, Gateway settings and Wi-Fi device tabs, Wi-Fi sales page. |
Some rows depend on the row above them and stay locked until it is on. For example, the Logs Page Tabs need View and either Show Full Logs or Show Today's Logs. The Orders and Stock actions need Orders Page and Stock Page. Close client application also grants the power actions.
Risky permissions, such as Run command on computer, Delete Files on Client, refunds and bill cancellation, are flagged in the matrix. The riskiest ones, including run command, file delete, session cancel and payment transfer, are never granted by default and must be turned on explicitly.
If a cashier has View and Show Today's Logs but not Show Full Logs, they can only see log entries from the current day. Reporting works the same way: Show Today's Reports without Show Full Reports limits a cashier to the current day's figures.
Working with the matrix
- Search permission filters the rows by name.
- The filters All, Granted, Differences and Flagged narrow the list. Granted needs a role column selected first.
- The buttons above the matrix grant or revoke every permission for the selected role.
- Changes are saved with the page's Save button. A dot marks roles with unsaved changes.
Creating a Cashier Account
- Open Settings, then Staff, then the Cashiers tab.
- Click Add Cashier.
- Enter the Username and Password. Choose a strong password. This account may have access to financial data and customer information.
- Optionally fill in the Display Name, Email and Mobile.
- Choose the role type: Admin, Manager, Cashier or Custom. For Custom, pick the role in Custom Role.
- Click Save to create the account.
The new cashier can now sign in to the HandyCafe server from the cashier login screen. Passive cashiers are not listed on that screen.
Creating a Custom Role
- Open Settings, then Staff, then the Roles & Permissions tab.
- Click Add Role.
- Enter a name for the new role (e.g., "Shift Supervisor", "Junior Cashier", "Night Staff").
- The new role starts with the built-in Cashier permissions, which include remote management, screenshot and file transfer. Review its column in the matrix and check or uncheck permissions.
- Click Save at the bottom of the page.
Once saved, you can assign this role to any cashier account with the Custom role type. There is no role level. Roles differ only by their permissions.
Backend Enforcement
Permissions are enforced on the server side, not just hidden in the UI. Even if someone were to bypass the client interface or manipulate the frontend code, the server validates every request against the cashier's role permissions before executing it.
This means:
- A cashier without the Members Delete permission cannot delete a member, even by sending a direct API request.
- A cashier without Show Full Reports cannot retrieve historical report data, regardless of how they access the system.
- All permission checks happen in the Rust backend before any database operation is performed.
Security: Rate Limiting
To protect against brute-force attacks, HandyCafe enforces login rate limiting:
- 5 failed login attempts within a 10-minute window triggers an automatic lockout.
- The lockout lasts 15 minutes, during which no login attempts are accepted for that account.
- After the lockout period expires, the cashier can try again.
This applies to both the server login screen and the cashier login on client PCs.
Shift Management
Every transaction (session payments, order payments and so on) is recorded with the identity of the cashier who handled it. Revenue can therefore always be traced per cashier.
Counted shifts are optional and off by default. Turn on Enable shifts in the Shifts section of Settings > Staff. Cashiers then open the till by counting it at sign-in and close it by counting again at sign-out. The difference is recorded against the shift. Require a note when the count does not match makes the cashier explain any discrepancy. See Cash Register and Day-End Summary.
Permission Examples
Scenario 1: Basic Cashier A new hire who only needs to start and stop sessions and take payments. Give them a custom role with Manage Computers, Add time and the Bills collection rows. They cannot view members, reports, logs or consoles.
Scenario 2: Shift Supervisor A trusted employee who oversees the floor. Add the Members View and Update, Consoles View, and Reporting View with Show Today's Reports. They can manage sessions, view (but not delete) members, see consoles and check today's revenue, but cannot access full historical reports or modify payment methods.
Scenario 3: Night Manager A manager who handles the late shift independently. Start from the built-in Manager role and leave off the Members Delete, Logs Delete and Sales, Stock & Payments Delete rows. They can manage everything during their shift but cannot permanently remove critical data.
Scenario 4: Privacy-Restricted Staff A cashier who should not see customer contact details. Grant Members View but leave Show Emails and Show Phones off. They can look up members by name but personal contact information is hidden.