Dispatch board (crew assignment)
Drag-free dispatch: see scheduled field jobs alongside your team roster and assign/unassign crew per job (POST /dispatch/assignments). The board reads the same ops jobs the Field Ops page manages, so dispatchers and schedulers work off one truth.
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 /ops/jobs, GET /users/members, GET/POST /dispatch/assignments.
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 for orgs using field ops; reachable from Field Ops → Dispatch board.
- Who can use it
- dispatch.assignments.read to see, dispatch.assignments.write to assign.
- The API behind it
GET /ops/jobs, GET /users/members, GET/POST /dispatch/assignments- Where it lives
- /ops/dispatch
See it in context
Field operations & dispatch — the full walkthrough, step by step: Jobs, crews, and a dispatch board — for the work that happens outside the browser.
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.