Config-driven module navigation
Turn app modules on/off and reorder the nav by editing one file. The nav is derived from NAV_CATALOG filtered + sorted by site.config.ts modules.
If you are building a front end
This one is configuration and UI rather than an endpoint you call — it ships with the template and turns on from config or the dashboard.
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
- site.config.ts -> modules: { <key>: { enabled: false } } to hide; { order: N } to reorder. Module keys: dashboard, crm, pipeline, events, demand, orders, ops, workflows, finance, community, ai-insight, learning, discover, vendors, trust, settings.
- Who can use it
- company config (presence/order) + role permission (per-user visibility); a hidden module is still API-enforced server-side.
- Where it lives
- app shell nav (sidebar + mobile bottom bar)
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.