Who needs it

Club has one panel, but four different people open it for different reasons. What each person sees is governed by team access grants (a separate, Account Platform-owned mechanism — see Boundaries); this page describes what each role does once they're in, not how the grant is configured.

Workspace owner

The owner is the only role with no ceiling — every screen in Club is theirs by default. In practice, the things that are specifically an owner's job:

• Read the money. The revenue dashboard (/dashboard/money) and the source leaderboard reconcile every attributed fan's spend to the account net, split by source, country, and money type.
• Set payout arrangements. /api/admin/traffer-payouts is owner-facing CRUD: a flat fee or a percent-of-revenue arrangement per traffic source. The leaderboard then shows, per source, revenue → traffer cut → the model's net.
• Run promos and bundles. Native OnlyFans promo campaigns and subscription bundles, plus the broadcast and automation-campaign systems that reach fans in bulk.
• Manage the roster. Creating and editing chatter accounts, assigning shifts, and exporting chatter payouts (/api/admin/chatters/payouts.csv) are owner/manager actions.
• Schedule wall posts. Priced or free OnlyFans posts, queued for a dispatcher instead of posted synchronously from the request that created them.

Team member / chatter

A chatter's day lives almost entirely in the inbox:

• The shared inbox. Reply to fans, send PPV, attach vault content, and use saved scripts — all subject to the same shadow/live send gate as everything else in Club.
• A per-fan dossier. Free-text notes and tags on a fan (/api/admin/inbox/fan/{id}/notes) so the next chatter on shift knows who they're talking to.
• A live economics card. While a thread is open, /api/admin/inbox/fan/{id}/economics shows what that fan has bought, what they haven't, and how much they've spent — read from the account's own transaction and PPV-send tables, never from OnlyFans live.
• Clock in and out. Shift tracking (/api/admin/chatters/clock-in / clock-out) is self-service — a chatter can only clock themselves, never another operator.
• The vault, for pitching. Search the vault to find what to send next, and read a content item's suggested price (/api/admin/content/{id}/suggested-price) before sending it.

Traffer

A traffer's job is traffic, not fans — Club gives them a narrower slice of the panel, scoped to the sources they own:

• Build and manage smart links. The Route-Spine policy engine (/api/admin/smartlinks) — creator-facing CRUD for trial/paid links, plus a dry-run resolver that answers "where does this country go?" before anything is published.
• Work the free-slot pool. Instead of minting a new OnlyFans link for every country, /api/admin/free-pool auto-dresses a spare link onto a slot — suggest, dress, dress-batch, or reclaim it back to the pool.
• See their own numbers. The same dashboard and source leaderboard the owner sees, but scoped to the domains they've been granted.

Platform operator / agency owner

Someone running more than one OnlyFans page — an agency, or an owner with several accounts — reads the same dashboards as a single-page owner, but rolled up. The money and traffic dashboards both accept an account_scope of creator or tenant: fan truth is unioned across every page that scope is authorized for, computed once rather than added up from separately-built payloads. On Fansly, the equivalent rollup is its own dashboard (/api/admin/fansly/dashboard) — a parallel screen, not a tab bolted onto the OnlyFans one, because Fansly's data model doesn't share a single OnlyFans transaction table to project from.

What's next

Boundaries — what Club deliberately does not do, and which product picks it up instead.