Add an organization (seed a prospect)
An operator seeds a prospect organization — a lightweight pricing-anchor stub for a business that isn't a Genesis customer yet — so they can price against a real organization_id. The referred owner's email is captured (optional but encouraged) as a future claim key; no login or role is created. Brand/marketing/naming for the seeded org inherit from the caller's white-label root (resolved by the backend + comms layer, not chosen on the form).
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: POST /api/v1/organizations/seed.
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 by default in the operator app. Toggle/reorder via site.config.ts modules (key 'organizations').
- Who can use it
- permission: organization.prospect.create (owner/admin)
- The API behind it
POST /api/v1/organizations/seed- Where it lives
- /organizations
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.