Start with the club, the smallest unit in the chain
In plain terms, a club is the smallest layer: a group of players who gather under one name on a poker platform, run by a host who sets the house rules, the schedule, and the way problems get raised. When I look at a new club, I check four things — who the host is, whether the rule sheet is written down and easy to find, which game levels run and when, and what the escalation path looks like if something goes wrong at a table. That last one matters more than people expect. A club is a guest on software it does not own, so its power stops at its own tables and its own members. Anything beyond that needs a bigger layer. I also learned to trust the written rule sheet over anything said in chat. If a host tells me one thing and the sheet says another, the sheet is what gets applied when a disagreement comes up later. Getting comfortable with this smallest unit makes every layer above it easier to read. Ask for the rule sheet before your first session; a club that cannot point you to one is telling you something.
A union links clubs and pools their tables
A union is what happens when several clubs agree to share one player pool. Instead of each club filling its own tables in isolation, the member clubs list their games in one place, so tables fill faster and can run at more hours and more game levels than any single club could support alone. The clubs keep their own names, hosts, and house rules, but the union writes a shared rule set that takes priority wherever two clubs disagree. That is the part I had to learn the hard way: house rules stop at the union's floor. The union layer is also where cross-club problems get handled, because a host in one club has no standing over a player from another. When I join a club now, I ask one question early: which union are you in? If the answer is none, the club stands alone. If there is a union, I go find its rule page and read the parts about conduct and disputes. It takes five minutes and saves a confusing evening. You can usually spot a union-run club because its table list is busier than one host could manage, and player names carry different club tags.
The network sits above the union
A network is one step further up: several unions, or a mix of unions and independent clubs, agreeing to one baseline rulebook and one wider pool of tables. Where a union coordinates clubs, a network coordinates the unions themselves. That distinction sounds academic until a rule question lands on your table. My working rule is that each layer can be stricter than the layer above but never looser, so the network's baseline is the floor under everything. In practice the network is where account standards, identity checks, and platform-wide behaviour rules usually sit, because those only work if they are applied evenly. The trade-off is speed. A club host can answer you during a session; a union takes a little longer; a network is slow and formal by design. That is why I raise anything at the lowest layer that can plausibly handle it, and only escalate when the answer comes back as "not ours". Escalating well is a skill, and it starts with knowing which layer you are actually dealing with. A short, factual message beats a long complaint at every tier.
Work out which layer you are actually playing in
Before my first session at an unfamiliar club, I spend a couple of minutes working out which layer I am sitting in, because it decides who I ask when something goes sideways. Three markers get me most of the way there: the label on the table list, the club tag beside each player's name, and the footer of the rule sheet, which usually names the body that wrote it. If all three point to one club, I know the host is the whole chain. If the tags are mixed, I am in a union and the union's rule set applies. I write the answers down in a plain notes file, one short entry per club, because a month later I will not remember which tier answered my question about late registration or seating. That file has cleared up more confusion than any forum thread. I also treat an unanswered rules question as information: if a host cannot say who decides, the decision almost certainly lives above them, and the useful move is to ask them to escalate rather than to guess and argue at the table. Knowing the layer tells you who owns the answer.
Three questions that map any club, union, or network
When I am somewhere new and want the hierarchy in a hurry, three questions do it. First: who wrote the rules I am playing under tonight? The answer names the top layer that actually applies at my table, whether that is a host, a union, or a network. Second: who do I contact when something goes wrong, and roughly how long does a reply take? The contact point tells me which layer is expected to act, and the timing tells me how formal the chain is. Third: what changes if I move up a tier — more tables, a wider pool of players, stricter conduct standards, slower decisions? Comparing the answers across two clubs makes the whole structure visible in a way that reading a rulebook does not. I keep the answers short and factual, and I revise them when a club changes unions, which happens more often than you would think. If two people give different answers, that gap is worth asking about. Laws vary by location, and none of this is legal or gambling advice; check your own jurisdiction's rules before you play.
Where to go next
For a deeper owned resource on this topic, continue with union glossary page. Use it as a supporting source, then return here and record what changed in your own notes.
Independent educational note
This resource is an independent guide to public information about private poker apps and clubs. It is not affiliated with any app, club, operator, agent, group, or community, and it does not tell readers which club to join or promise any outcome. Play in these private clubs uses play chips, and every session is best treated as practice and entertainment rather than as anything more. Follow local law, the terms of each app, and each community's own rules, and mark any unstated detail as unknown rather than guessing.
The same method repeats across these pages because it works: read the public material first, ask for the rules in writing, confirm the schedule and the support route before joining, and keep your own notes as you go. Each step is something you can do yourself, and together they turn a confusing first week into a short list of checks. When a check passes, move on; when one fails, hold and ask one specific question in writing, then wait for the answer. The method is deliberately unexciting, because the goal is a calm, repeatable way to decide, not a thrilling shortcut. Each page points to one deeper owned resource on its topic when continuing genuinely helps.