Notifications inbox

Updates from your team and your work in one list (GET /comms/notifications), mark-as-read per item. The bell in the shell header deep-links here.

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 /comms/notifications, POST /comms/notifications/:id/read.

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.
Who can use it: session only; server scopes to the signed-in user.
The API behind it: GET /comms/notifications, POST /comms/notifications/:id/read
Where it lives: /notifications

See it in context

Messaging — SMS & email — the full walkthrough, step by step: Your number, your domain, every message logged to the customer record.

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.