Member Benefits
Member benefits are what fans get for joining a tier. In Flo, that breaks into two parts:
- What you promise — short bullets and an optional description on each tier (marketing copy fans see before and after they join).
- What you deliver — real access you configure in the Membership Hub and Fan Hub (courses, products, posts, live sessions, messages, and external community links).
You need Creator or above to run memberships.
Related: Create a tier · Memberships overview · Membership block · Fan Hub overview.
Promise vs deliver
| Promise (copy) | Deliver (access) | |
|---|---|---|
| Where you edit | Edit tiers → Offer → What's included and Description | Open hub → Classroom, Community, Live, and more |
| What fans see first | Checkmarks on your Membership block and join page | Content, downloads, and links after they sign in |
| Flo enforces it? | No — bullets are labels you write | Yes for Classroom entitlements and tier-gated posts / live events |
Keep them aligned
If a bullet says Full course library but you never add courses in Classroom, members will feel misled. Write bullets that match what you actually set up — or update Classroom right after you change copy.
Part 1 — Benefit bullets (what you promise)
Where to add them
| Path | Steps |
|---|---|
| Membership Studio | Dashboard → Memberships → your program → Edit tiers → Offer tab → expand a tier |
| Hub settings | Open hub → Settings → Pricing & tiers → expand a tier (same fields) |
Under What's included:
| Action | Result |
|---|---|
| Type in a row | One benefit line (e.g. Weekly office hours) |
| Add benefit | Another row |
| X on a row | Removes that line from the editor (save tiers to apply) |
Empty benefit rows are ignored when you save.
Each label can be up to 300 characters — keep lines short so they read well on mobile.
Optional tier description
Below the name and color, Description (optional) is a short paragraph (not a bullet list). Fans see it on the join page under the tier name.
| Tool | Detail |
|---|---|
| Write with AI (sparkle) | Drafts from your tier name, benefit bullets, and program name — edit before saving |
| Length | Aim for a few sentences; AI targets roughly 160 characters |
Full tier setup: Create a tier.
Where benefit copy appears
| Surface | What shows |
|---|---|
| Membership block on your Flo page | Tier name, price, and benefit bullets with checkmarks |
Join page (…/portal/membership) | Same bullets on each tier card, plus description |
| After checkout | Success screen lists the tier’s benefits |
| Switch tier (existing members) | Top two benefit lines as a quick summary |
Benefit bullets do not by themselves unlock courses or hide posts — you configure that separately below.
Part 2 — Delivering real access
Classroom — courses and digital products
Open hub → Classroom.
| Step | What happens |
|---|---|
| Add content | Pick a course or product you already created in Flo |
| Tier scope | All tiers — every member gets access · Specific tier — only that tier (shown as Tier name only in the list) |
| Save | Members on qualifying tiers see Included in Your Membership in the Fan Hub |
| Fan sees | Creator meaning |
|---|---|
| Course row → View → | Opens the course player for their account |
| Product row → Download → | Opens digital product access in the portal |
Higher tiers should include more Classroom items (or the same items plus extra). A common pattern:
| Tier | Classroom setup |
|---|---|
| Free | One intro course — All tiers |
| Supporter | Full course library — Supporter only (or All tiers if free tier should not see it, use tier-only gates on posts instead) |
| VIP | Everything in Supporter plus bonus product — add another entitlement VIP only |
Removing an entitlement in Classroom revokes that resource for future portal views (existing course progress may still apply on the course side — test after changes).
Community posts — who can read
Open hub → Community → create or edit a post.
When composing, use the audience control (people icon):
| Choice | Who sees the post |
|---|---|
| All members | Everyone active in this program |
| A specific tier | Only members on that tier |
The feed shows a label like All members or the tier name so you can audit visibility.
Use tier gates for “VIP-only updates” or early access. Use All members for announcements everyone should see.
Live sessions — who can attend
Open hub → Live → schedule or edit an event.
| Audience | Meaning |
|---|---|
| All members | Any active member can join (subject to your live room rules) |
| Specific tier | Only members on that tier |
Match the tier gate to what you promised in benefit bullets (e.g. Monthly live Q&A on the tier that should attend).
Messages
Open hub → Messages is your inbox for direct conversations with members. It is not tier-gated in the same way as posts — use it for support and relationship building across tiers.
External community (Discord, Slack, etc.)
Flo does not host Discord or Slack inside the hub. You deliver external access in two practical ways:
| Method | How |
|---|---|
| Benefit bullet + manual invite | Bullet says Private Discord — you share the invite in a welcome post, Messages, or your Welcome email |
| Per-tier invite link (saved with tier) | Edit tiers → Delivery tab → Per-tier overrides → Tier-specific invite URL → Save tiers |
When a per-tier link is saved, active members see a Join → card in the Fan Hub feed: You have access to the [tier] community.
Put the real invite only on tiers that should have it — leave the field blank for tiers without external access.
Program-wide invite field
Delivery may also show a single program-wide community URL field. That broader setting is still being rolled out — rely on per-tier invite URLs and benefit copy for production use today.
Fan Hub branding (trust, not perks)
Dashboard → Fan Hub controls portal look — logo, colors, and layout. It does not replace Classroom or benefit bullets, but it makes delivered perks feel cohesive after checkout.
Fan Hub overview · Membership portal.
Design a tier ladder fans understand
Good / better / best (Creator-friendly)
On Creator, you can use up to 3 tiers per program — a natural good / better / best ladder:
| Tier | Price | Bullets (promise) | Delivery (access) |
|---|---|---|---|
| Free | $0 | Taste of community, newsletter-style posts | All members posts + one free course |
| Core | Monthly | Full archive, Classroom courses | Extra courses Core only; some posts Core only |
| VIP | Higher monthly or yearly | Live calls, Discord, templates | Live events VIP only; Discord URL on tier; bonus product VIP only |
Put your strongest offer on the highest tier so upgrades feel obvious.
What to put in bullets vs description
| Use benefit bullets for | Use description for |
|---|---|
| Scannable perks (3–7 short lines) | One emotional sentence about the tier |
| Features you can gate in Classroom / posts / Live | Tone and positioning (“Best for coaches who…”) |
Avoid vague lines like And much more! — name the concrete perk.
Highlight a tier on your Flo page
In Builder, edit your Membership block:
| Setting | Effect |
|---|---|
| Featured tier dropdown | Which tier gets Popular styling on tiers layout, or drives the hero tier on card / compact layouts |
| Membership default | Uses your program’s default featured tier when set; otherwise Flo highlights the first tier in order |
Reorder tiers in Edit tiers (drag handle) to control top-to-bottom order on the block and join page.
Ideas by creator type
Use these as starting points — then wire each line to something in Classroom, Community, or Live.
| Creator type | Benefit bullet ideas | Deliver in Flo with |
|---|---|---|
| Coach / educator | Full course library, worksheets, monthly Q&A | Classroom courses; Live tier-gated events |
| Creator / influencer | Exclusive posts, behind-the-scenes, early drops | Community tier-gated posts |
| Community leader | Discord access, member directory, AMA threads | Per-tier invite URL + All members or tier posts |
| Designer / maker | Template packs, asset downloads | Classroom products; optional product entitlements per tier |
| Fitness / wellness | Workout plans, check-in posts, live classes | Classroom + Live on upper tiers |
Member lifecycle — benefits stay in sync
| Event | What members see |
|---|---|
| Join | Benefits on success screen; Classroom and feed unlock for their tier |
| Upgrade tier | New benefit bullets on switch flow; new Classroom items and gates apply after change |
| Downgrade or cancel | Access adjusts to the new tier or member status — Billing & dunning · Pause and cancel |
When you remove a tier from the editor and save, it is archived for new signups — existing subscribers keep their tier until they change plan.
Launch checklist
| Step | Done? |
|---|---|
| Each paid tier has clear benefit bullets (not empty) | ☐ |
| Bullets match Classroom entitlements | ☐ |
| VIP-only perks use tier gates on posts or Live | ☐ |
| External community links set on Delivery per tier (if promised) | ☐ |
| Membership block published with correct featured tier | ☐ |
| Test join on a lower tier and an upper tier — confirm access differs | ☐ |
Troubleshooting
| Issue | What to check |
|---|---|
| Bullets show on join page but member sees no courses | Hub → Classroom — add course with correct All tiers or tier scope |
| Member on VIP cannot see a post | Post audience — may be limited to a different tier |
| Discord link missing in portal | Delivery per-tier URL saved? Member on the right tier? |
| Benefits look wrong on Flo page | Edit tiers saved? Builder → Update live published? |
| Too many tiers to add | Creator cap is 3 — Create a tier |
What's next?
- Create a tier — prices, bullets, and save rules
- Membership Hub overview — Community, Classroom, Live, Members
- Membership block — show benefits on your Flo page
- Welcome email — reinforce perks after join
- Billing & dunning — renewals and failed payments
- Fan Hub overview — portal branding after checkout