Settings & Party Rules

Why this page matters

Every rule your members experience — how big a party is, how long they have to review, how many outstanding reviews is too many — comes from here. Get these right early, because changing them mid-stride tends to confuse a community more than launching with sensible defaults from day one.

Content channels

Decide which platforms members can submit from — LinkedIn, blog, Instagram, and so on. Keep this tight to what your niche actually publishes on; allowing every channel under the sun just spreads your members' attention across formats they don't all care about.

Party defaults

Set the shape of a typical session:

• Party size — how many members can join a single party.
• Room size — how members are broken into smaller groups within a party, if your community runs at scale.
• Time window — how long members have to submit and then complete their reviews before the party closes.

You can override these per-party when you schedule one, but the defaults are what most sessions will run on.

Participation rules

Communities can choose how much outstanding participation a member can carry between sessions. These rules encourage people to follow through on sessions they opt into without requiring any specific action on the destination platform. You control how strict that gate is and how strikes accumulate for members who habitually skip.

Rotation

Control whether members get matched with the same people repeatedly or rotated through the wider community over time. Rotation keeps perspectives varied; letting pairs repeat can build familiarity if that's what your community's culture is going for.

Niche matching and competition-exclusion

Turn on competition-exclusion if your niche is one where members might genuinely compete for the same clients or audience — it keeps direct competitors out of each other's review pool. See Managing Niches for how niches themselves are structured.

Strike threshold

Set how many strikes a member can accumulate — missed reviews, reported behavior — before they're automatically paused. Strikes protect your community's participation standards and conduct, not any specific action a member does or doesn't take on an external platform. Pair this with your moderation process for anything that needs a human judgment call instead of an automatic one.