Modules & featuresEach platform pill shows that platform’s true catalog — what actually exists there, nothing greyed-in from elsewhere. Core modules first, features within them. One switch cascades to every linked surface — turning a module off follows it everywhere it renders.
Scope + owner (§17): module state is PER-PLATFORM — the pill IS the platform selector, and no switch renders unscoped. folo.link: composes the view and owns no module state; every switch writes through the owning product’s admin API (shared-engine modules: one write via the engine’s API, both products).
Scope + owner (§17): module state is PER-PLATFORM — the pill IS the platform selector, and no switch renders unscoped. folo.link: composes the view and owns no module state; every switch writes through the owning product’s admin API (shared-engine modules: one write via the engine’s API, both products).
Each pill is that platform’s true catalog — one switch, the cascade follows it.
Demo data
the consumer surface
Modules on
8 / 9
in the Folo catalogFeatures on
21
within enabled modulesShared engines
3 / 3
one switch state on both pillsLast changeAwaiting source
—
💬
ChatDMs · inbox
Shared engineOne engine under Folo and Fanogram — same DB and CDN. One switch state, shown on both pills: flip it here and the other pill shows the same. The switch writes through the engine’s API once — one write path, one audit trail.
Effect: off ⇒ Chat and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: the shared engine’s API — ONE write, both product pills read the same state · audited.
Direct messages
Unified inbox
PPV unlocks in chat
▤
Vault & mediafolders · drag & drop · watermarking
Shared engineOne engine under Folo and Fanogram — same DB and CDN. One switch state, shown on both pills: flip it here and the other pill shows the same. The switch writes through the engine’s API once — one write path, one audit trail.
Effect: off ⇒ Vault & media and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: the shared engine’s API — ONE write, both product pills read the same state · audited.
Folders
Drag & drop
Watermarking (leak tracer)
📞
Live & calls1:1 calls · live rooms
Effect: off ⇒ Live & calls and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
1:1 video calls
Live rooms
Paid entry
📣
Channelsbroadcast & paid channels
Effect: off ⇒ Channels and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
Broadcast channels
Paid channels
Channel drops
🎬
Clips & reelsshort-form feed
Effect: off ⇒ Clips & reels and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
Clips feed
Creator upload
◐
Stories & notes24h stories · profile notes
Effect: off ⇒ Stories & notes and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
Stories (24h)
Notes
◈
Discoveryfeatured · trending · search
Effect: off ⇒ Discovery and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
Featured rail
Trending
Search
Linked surfaces ⓘHome page builder
★
Primemembership · perks
One surfaceConverges w/ FG Accounts→Pro — ONE membership-tier manager; per-product wording is a label, never a second surface (Mav 2026-08-09).
Effect: off ⇒ Prime and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: Folo’s own admin API · audited there — folo.link composes the view, owns no module state.
Perk set (per Prime manager)
Carries to Fanogram (entitlement)
$
Payments · consumptionfan pays · wallet shows — the ledger records on Fanogram
Shared engineOne ledger (locked ruling): Folo records nothing sale-side. This module is the consumption surface; recording + CRM live on Fanogram’s side of the same engine.
Effect: off ⇒ Payments · consumption and its linked features disappear from Folo for everyone — per-person exceptions live in Capabilities, grants in Entitlements. Write path: the shared engine’s API — ONE write, both product pills read the same state · audited.
Tips
PPV purchases
Subscriptions
▦
Modules ≠ flags ≠ entitlements — this page owns the switches. The ladder: MODULE (exists) → FLAG (rolled out) → CAPABILITY (this entity may) → ENTITLEMENT (this account was granted) — full vocabulary on control.html →
Three switches, three concepts — never blended. Module switches are product truth (is this capability part of the product here?). Feature flags are rollout (staged exposure of something already true). Entitlements are per-account grants (this person or plan gets it). This page owns the first; flags and entitlements each keep their own surface.
Composed control, single write path. Every switch here writes through the owning product’s admin API — so each product keeps one write path and one audit trail. folo.link composes the view; it owns no module data. Shared-engine switches (Chat · Vault & media · Payments) write through the engine’s API once — both product pills read the same state.
Composed control, single write path. Every switch here writes through the owning product’s admin API — so each product keeps one write path and one audit trail. folo.link composes the view; it owns no module data. Shared-engine switches (Chat · Vault & media · Payments) write through the engine’s API once — both product pills read the same state.