Member (customer) portal

A per-tenant, capability-gated customer portal at /m/:portalSlug: sign in/up, dashboard, events, courses, orders, refer-a-friend, coach, account. Separate session from the operator app.

If you are building a front end

Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: /api/v1/member/*.

Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.

How to turn it on: Provisioned by Genesis per tenant (portal_member_config). Per-feature tiles gate on member capabilities (events, courses, orders, referrals, coach, profile_edit).
Who can use it: member session cookie + member capability map (opt-out).
The API behind it: /api/v1/member/*
Where it lives: /m/[portalSlug]/**

See it in context

Community & member portal — the full walkthrough, step by step: A branded logged-in home for your customers — courses, events, orders, wallet, coach.

Machine-readable

This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.