SuperBluOrange can scope the platform around the proposed model and its operating requirements. If the project is an independently operated public room or a shared-liquidity brand, compare standalone poker and network skins.
Define membership and value flows together
Record who may create a club, invite players, approve membership and operate tables. Map any value transfer between a player, manager, club and external service. Each transfer needs an identifiable source and destination, an authorized actor and a corresponding record.
A visual balance adjustment is not an adequate account history. The operator needs to distinguish a correction, reward, transfer and reversal so that the same action can be explained in a report or dispute.
Specify permissions before assigning managers
| Action | Control to agree |
|---|---|
| Invite or remove a member | Permitted role, eligibility checks and effect on existing sessions |
| Adjust a balance | Reason, approval threshold and retained original record |
| Create or change tables | Allowed formats, limits and who approves exceptions |
| Export records | Permitted data, recipient and access logging |
| Revoke a manager | Immediate effect on sessions, tokens and any delegated permissions |
Where a person can initiate and approve a sensitive action, make that exception explicit. Decide whether the risk requires another approver or a narrower permission before launch.
Test a club as an operating unit
- Demonstrate a disputed adjustment and trace it from the player account to the club report.
- Revoke a manager's access and check that an existing session cannot continue performing restricted actions.
- Test whether an administrator for one club can see or change another club's records.
Run the same checks for a closed table or removed member with activity still in progress. The scope needs to state what is settled immediately, what remains pending and who may resolve it. These proposed tests establish acceptance requirements, not a claim that a particular configuration has already passed them.
Scope reports and support
Agree the daily reconciliation, exception report and information available for a player complaint. Define the service hours and authority of the people operating the clubs, separately from technical support for the platform.
Describe your club model and permission structure. Include the player locations, unit mechanics and any transfers or redemption so feasibility and software scope can be assessed together.