Player self-join
The player scans the room QR or opens its live-list page, enters an email and receives an OTP. Verification creates or retrieves one ACES account number, then the player chooses a game and a public display name.
ROOM-SCOPED OPERATIONS
Live lists.
Real floor updates.
A proposed operational workflow for verified rooms. No room is shown as live until authenticated staff post current data.
Current status: workflow published; no connected room feed yet. ACES does not accept buy-ins, guarantee seats or operate the poker room.
1. Room and admin approval
- Room claim: an operator submits public room facts and private authority evidence.
- Editorial review: ACES verifies the listing without treating the ownership claim as proof of current games.
- Admin approval: ACES provisions individual staff accounts—never a shared public PIN—with room-scoped permissions.
- Roles: room owner can invite/revoke managers; floor manager controls games and lists; host can update assigned tables only; viewer is read-only.
- Audit: every game, player-status and staff-access change records actor and timestamp.
2. Start a live list
- Floor staff create a game with room, format, stakes, table status, seat count and the time confirmed.
- The game starts as draft. A manager publishes it as open only when the floor confirms it.
- Every public board shows “updated X minutes ago,” the responsible room and a direct confirmation channel.
- If staff stop updating, the list becomes stale automatically and then offline; yesterday’s queue never rolls forward.
3. Add a player through the same ACES signup
Staff-assisted join
Authorized floor staff can open the same form or QR flow at the desk and help the player enter an email. Staff cannot bypass the OTP, invent a shadow account or view the code. Phone is encouraged for alerts but not initially required.
Returning ACES player
The verified email retrieves the existing ACES identity instead of creating a duplicate. With consent, the live list shows only the chosen display name—not email, phone, wallet, shipping address or account number.
After joining, the customer record can be progressively updated with real name, screen name, photos, profile answers, phone, social links and other service-relevant details. Private fields never belong on the public board.
4. Player states
- Waiting: ordered by server timestamp, with staff-controlled priority exceptions logged.
- Called: player receives a private alert; a visible countdown is optional.
- Seated: removed from the public waiting list and recorded in the audit log.
- Deferred: player asks to remain but not be called for the next seat.
- No-show / removed: reason is private; public board shows no negative label.
- Left: player or staff closes the entry; duplicate active entries are blocked.
5. What the public sees
Room, game, stakes, status, tables running, seats open if staff confirm them, consented display names in queue order and last-updated time. The board does not show phone numbers, emails, wallet addresses, buy-ins, balances, exact arrival history or staff notes.
A live list is operational information, not a reservation guarantee. The room controls seating and eligibility at the venue.
6. Safety and failure rules
- Individual authenticated accounts, least-privilege roles and immediate revocation.
- Server records are authoritative; browser-local demo data can never publish.
- Rate limits, duplicate detection and audit logs for all list mutations.
- Player removal and privacy requests available at the desk and through ACES support.
- Manual room-offline switch, automatic stale timeout and incident rollback.
- No rewards, comps, payments or Points until separately agreed, implemented and legally reviewed.