Customer pass / entitlements page

A signed link a customer opens to see their entitlements — no account needed. The link IS the authorization (opaque token in the URL).

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 /portal/:organizationSlug/my-account (token).

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: Sent to customers by your flows.
Who can use it: token-authenticated (signed URL).
The API behind it: GET /portal/:organizationSlug/my-account (token)
Where it lives: /p/:organizationSlug/:token

See it in context

Events & ticketing — the full walkthrough, step by step: Publish an event; your site sells it — registration, check-in, and the follow-up.

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.