Security

Who can see my data internally?

Q: 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.

Access is role-based and enforced server-side, not only hidden in the interface: four fixed roles (owner, dispatcher, office, technician) 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 at any time.

All six answers and the control register

In Settings

An owner can browse the full event history, filtered by actor, action, entity, branch and date, and export it as CSV or JSON.

Settings · Audit logOwner

Event history

Filtered by entity: work orders · Oct 20

Time · actor and actionTaken by

9:14 AM: D. Okafor completed WO-48377; Person
9:20 AM: Opened WO-48390 from AGR-0219; Automated action
9:41 AM: M. Chen changed the status of WO-48102; Person
10:02 AM: Renewal reminder queued for AGR-0219; System process

Export CSVExport JSON

What that rests on

ControlHow it is enforced

Four fixed rolesOwner, dispatcher, office, technician, checked server-side against a fixed role matrix, not hidden by the interface. A technician sees only their assigned jobs.

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.

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.

The other five.

Bring the question to a call.We run the control on real records.

Start free Book a demo