How to Set Up and Manage Billiard Hall Staff Permissions and Access Levels in Your POS System

A trusted cashier closes out a shift with a ₱3,000 cash shortage — and when you check the logs, you realize there's no record of who approved a string of discounts that afternoon. If your operation doesn't have clearly defined billiard hall staff permissions and access levels in your POS system, you're essentially running on the honor system. That works until it doesn't.

Structuring what each staff role can see and do isn't about distrust — it's about clarity, accountability, and protecting your business from both honest mistakes and deliberate abuse. Here's how to think through it and set it up properly.

Start with Three Core Roles: Owner, Manager, and Cashier

Most billiard halls don't need a dozen permission levels — they need three well-defined ones. Overcomplicating your role structure creates confusion on the floor and makes onboarding new staff slower than it needs to be.

• Owner/Admin: Full access to everything — reports, pricing configuration, staff accounts, shift history, and reconciliation data. This account should be used sparingly and never left logged in on a shared terminal.
• Manager: Day-to-day operational control — opening and closing shifts, approving discounts, viewing reports, and managing table sessions. Managers should not typically have access to staff account creation or system-wide pricing changes unless your structure specifically requires it.
• Cashier: Narrow, task-focused access — starting and ending table sessions, processing checkouts, recording product sales, and handling cash. No access to historical reports, discount overrides, or shift reconciliation data.

This three-tier structure covers the vast majority of billiard hall operations. If you have a senior cashier or floor supervisor role, map them closest to Manager but restrict the reporting and configuration access they don't need.

Define What Each Role Can and Cannot Do — Before You Configure Anything

Before you touch a single setting in your billiard hall POS system, write out what each role should be allowed to do. This sounds obvious, but most operators skip it — and then end up with a cashier who can edit completed sessions or a manager who can't run the end-of-day report they need.

Work through these permission categories explicitly:

1. Table session control: Who can start, pause, resume, transfer, and end sessions? Cashiers should handle routine starts and ends. Session transfers between tables and pauses mid-game are typically fine at the cashier level. Voiding or retroactively adjusting a completed session should require Manager approval.
2. Pricing and discounts: Who can apply a discount or override a rate? This is one of the highest-risk permissions in any POS. Keep discount application at Manager level or above, and make sure every discount is logged against a named account.
3. Cash drawer access: Who can open the drawer outside of a transaction? In a well-run operation, the answer should be: nobody, without a logged reason. Your system should record every drawer open event.
4. Reports and revenue data: Cashiers should not see cumulative revenue figures, shift comparisons, or historical data. That information is for management. Limit report access accordingly.
5. Inventory adjustments: Stock deductions tied to sales should happen automatically. Manual adjustments — receiving stock, correcting counts — should be Manager-level only.

Use Server-Side Permissions, Not Just Interface Restrictions

There's an important technical distinction worth understanding: some systems hide certain buttons from lower-tier staff in the interface, but don't actually enforce restrictions on the server side. That means a determined employee who knows the system could potentially access restricted functions through a browser workaround or shared login.

When evaluating your POS setup, confirm that permissions are enforced server-side — meaning the system itself rejects unauthorized actions, not just the visible interface. This matters because it ensures your audit trail is reliable. If a Manager-level action is logged, it genuinely required Manager credentials to perform.

CuePoint enforces staff roles with server-side permissions and maintains a full audit trail, so every discount applied, session ended, or drawer opened is attributed to a specific account. That audit log becomes your first line of defense when a discrepancy surfaces.

Set Up Individual Accounts — Never Share Logins

Shared login credentials are the single most common reason staff permission systems fail in practice. If three cashiers all log in as "cashier1," your audit trail is useless — you know what was done, but not who did it.

Every staff member who uses your POS should have their own named account. This applies even if you have part-time or weekend-only staff. The setup takes two minutes per person and pays for itself the first time you need to trace a transaction back to a specific shift.

A few practical rules to enforce:

• Staff must log out when stepping away from the terminal — not just leave the session idle.
• Passwords should not be written on sticky notes near the register. (It happens more than you'd think.)
• When a staff member leaves your employ, disable or delete their account the same day — not "eventually."

For billiard hall staff management, the combination of individual accounts and shift handover procedures creates a clear chain of accountability across every operating hour.

Connect Permissions to Your Shift Handover and Cash Reconciliation Process

Staff permissions don't operate in a vacuum — they need to connect to your shift structure. A permission system that lets anyone open a shift but only Managers close it creates a gap: who's accountable for cash collected during a shift that a cashier opened without Manager oversight?

A clean shift structure looks like this:

1. Manager opens the shift, logs starting cash, and confirms the drawer balance.
2. Cashier takes over the terminal under their own login. All transactions are logged to their account for that shift period.
3. At shift end, cashier counts cash and records their figure. Manager reviews, confirms or flags a variance, and closes the shift.

This process only works if your permission setup supports it — specifically, if cashiers cannot close shifts themselves and if variance data is accessible only to Managers and above. If your cash drawer and day-close reconciliation process is currently handled by whoever is last in the building, tightening your permission structure is the first step to fixing it.

Review Access Levels Periodically — Not Just at Setup

Staff permissions tend to get configured once and then forgotten. Over time, this creates drift: a cashier gets promoted to shift lead and starts doing manager-level tasks under a cashier login; an owner account gets used for daily operations because it's the only one anyone remembers; a former manager's account sits active for months after they've left.

Schedule a quarterly review of your staff accounts. Check:

• Are all active accounts still used by current employees?
• Do current roles match what people are actually doing day-to-day?
• Has anyone accumulated permissions they no longer need?
• Are there any accounts that haven't logged in for 30+ days that should be deactivated?

Reviewing your billiard hall revenue and activity reports alongside your staff account list makes it easy to spot anomalies — unusual discount frequency, sessions closed without matching product sales, or transactions logged outside of scheduled shifts.

A Practical Takeaway

Getting billiard hall staff permissions and access levels right in your POS system doesn't require a complex setup — it requires deliberate setup. Start by mapping your three core roles to specific, written permission lists before you configure anything. Enforce individual logins, connect permissions to your shift handover process, and review accounts every quarter. The goal isn't surveillance — it's a system where every transaction has an owner, every discrepancy has a starting point, and your staff can operate confidently within clearly defined boundaries.