Field job creation + visits & territories
Schedule a field job from the web: pick the service agreement it fulfills (jobs bill against agreements), set the date, add crew notes. Plus compact read panels for recent field visits and defined territories — the web could previously complete jobs it couldn't create.
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/ops/jobs, GET /api/v1/ops/agreements, GET /api/v1/ops/visits, GET /api/v1/ops/territories.
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
- Part of the 'ops' module.
- Who can use it
- RBAC: ops.jobs.write (create) / ops.agreements.read (picker) / ops.visits.read / ops.territories.read.
- The API behind it
POST /api/v1/ops/jobs, GET /api/v1/ops/agreements, GET /api/v1/ops/visits, GET /api/v1/ops/territories- Where it lives
- /ops
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.