Limits and rules
Credit and Win Limits
Limits are the main lever you have as an organizer. There are two of them, they work in opposite directions, and both are enforced by the server rather than the app.
Credit limit — how far down a member can go
A credit limit caps how much a member can owe you. It is the number that stops a bad weekend becoming a problem you have to chase.
Importantly, it counts what they already owe plus whatever is at risk on open picks — not just the settled balance. A member cannot quietly go past their limit by stacking up pending bets that haven’t resolved yet.
Set a default under Member Settings so every new member inherits it, then adjust individuals from their member page. Changing the default later does not disturb members who already have one.
Win limit — how far ahead a member can get
A win limit is the mirror image: it caps how much a member can be up before something happens. It is optional, and plenty of groups never set one.
Where it earns its place is a member on a heater. Without a win limit, a run of wins can build a balance you owe that is larger than you intended to carry.
What happens when a win limit is hit
You choose, per member:
Block Picks stops them betting until the balance is settled. Blunt, and unambiguous.
Require Approval lets them keep placing picks, but each one waits for you to approve it. Softer, and better if you want to stay in the game with someone rather than freeze them out.
Both are enforced server-side
Limits are checked when a pick is submitted, on the server — not merely hidden in the app. A member cannot get around one by refreshing, using a different device, or catching the app in a stale state.
Choosing numbers
Start lower than feels necessary. Raising a limit for someone is a pleasant conversation; lowering it after they have run up a balance is not.
Limits are also a per-member tool, not just a global default. It is completely reasonable to run different numbers for the friend who settles every Monday and the one who takes three weeks.