Member-portal settings

Configure the customer-facing portal: branding, welcome message, self-signup toggle, capabilities. What you set here is exactly what /m/:slug and the /lp/:slug landing render for your customers.

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: GET/PATCH portal config endpoints.

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: On for orgs with a portal slug.
Who can use it: org admin; PATCH /events/portal-config style config writes.
The API behind it: GET/PATCH portal config endpoints
Where it lives: /settings/member-portal

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.