Who can see my data internally?
Access is role-based and enforced server-side, not just hidden in the UI — the four roles above define what a user can see and do. Every action on the core records is written to an append-only event ledger, and an organization owner can browse and export the full history for their organization at any time.
- Four fixed rolesOwner, dispatcher, office, technician — checked server-side against a fixed role matrix at the server-component and server-action layer, not hidden by the interface. A technician sees only their assigned jobs. Live
- Append-only event ledgerCreates, status changes, completions and deletes on customers, sites, equipment, agreements, work orders and invoices each write an event in the same transaction as the change. The event commits only if the change does. Live
- Org-wide audit log and exportAn owner can browse the full event history filtered by actor, action, entity, branch and date, and export it as CSV or JSON from Settings. Live
This is one of six questions answered individually. The full picture — access control, audit trail, data handling, integrations, and what we haven't built — is on the security page.
02
The other five.
Each one is its own page, so you can forward the single answer somebody asked for.
03
Still not satisfied?
Fair. Bring the question to a call and we'll show you the control running against real records, not a slide about it.