Roles & permissions admin

The reusable RBAC-admin example: member list with roles, effective permissions with role-vs-override provenance, grant/revoke overrides, plus a guide page explaining the model. The page partners copy when they need admin surfaces.

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 /users/members, GET/POST /users/:id/permissions.

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: Always on for admins.
Who can use it: users.* / role admin permissions; API is the wall.
The API behind it: GET /users/members, GET/POST /users/:id/permissions
Where it lives: /settings/permissions/settings/permissions/guide

See it in context

One login, many businesses — the full walkthrough, step by step: Agencies and multi-brand operators: every business, one account, real separation.

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.

Roles & permissions admin

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 /users/members, GET/POST /users/:id/permissions.

How to turn it on: Always on for admins.
Who can use it: users.* / role admin permissions; API is the wall.
The API behind it: GET /users/members, GET/POST /users/:id/permissions
Where it lives: /settings/permissions/settings/permissions/guide

See it in context

One login, many businesses — the full walkthrough, step by step: Agencies and multi-brand operators: every business, one account, real separation.