Rename, discount, or restrict a fan on OnlyFans
Push a display-name change, a time-boxed subscription discount, or a restriction to OnlyFans directly, once the feature is enabled for your account.
Who this is for: team members and workspace owners who want OnlyFans itself to reflect a decision made in Club, not just Club's own records.
There are three separate actions, and they live in two different places and behind two different flags.
Rename
Club's own name for a fan is always editable — click the name in the chat thread header, or in the fan card's own title, and save. That local rename works with no flag at all: it never fails just because writes to OnlyFans are off.
Pushing the same name into OnlyFans as a native display name is the part that's gated: it only
fires when OF_FAN_ACTIONS is on, the requester has the inbox → fan_of_actions team
capability, and the fan's id is a real numeric OnlyFans id. Missing the capability doesn't fail
the rename — it just quietly skips the OnlyFans push, so your own label still saves.
Discount and restrict
These live in the Profile tab of the fan card, as a small OF-actions strip:
- Discount — a personal subscription discount. The button doesn't fire on one click: it opens a percent (5–60%) and duration (1–12 months) picker first, because a percent sent by accident has to be undone by hand, in OnlyFans, later.
- Restrict — hides the fan's comments and messages; their subscription itself is unaffected. Pressing it again on a restricted fan unrestricts them.
Off by default, one flag each, no per-account UI toggle
OF_FAN_ACTIONS gates restrict and the rename-push; discount needs a second,
independently-set flag (OF_FAN_ACTIONS_DISCOUNT) on top, because it's the one action that
touches a live fan's money directly and its behavior is calibrated last. Neither has a
per-account switch in the panel — until an operator sets the environment flag, the buttons stay
grey with a tooltip explaining which of the two reasons applies: "not enabled yet" is different
from "discount specifically isn't live yet," and the strip says which.
What actually happens when you press one
Every native write here — rename, discount, restrict — goes through the same shared engine-job queue every other OnlyFans write in Club uses (folder ops, promos, posts). The request answers "queued," not "done": the row survives an engine crash or pod restart, which a synchronous in-request wait wouldn't. A small action log directly under the strip shows the real, settled outcome once it resolves — read it rather than assuming a queued action already landed.
What's next
- Open a fan's card — where discount and restrict live.
- Write and tag private notes on a fan —
the notes you keep can also sync into the fan's native OnlyFans note, behind the same
OF_FAN_ACTIONSflag.
Export the full fan roster and conversations
Download a ZIP of your whole fan roster — profiles, conversations, and methodology — for offline analysis or an AI agent.
See which saved lists a fan belongs to
While chatting with a fan, see at a glance which saved segments — "whale," "expired," or anything else you've built — they currently match.