Security
Trust, checkable
No adjectives. The access model, the audit spine and the document controls are countable in the schema, and this page counts them.
What the schema enforces
Row-level security everywhere
Five hundred sixty-seven policies isolate every tenant’s rows. The marketing site cannot even read your data; nothing public can.
A ceiling above the owner
Platform entitlements bind workspace owners too. What is not sold is not reachable, by token, export or API.
The document spine
Sequential control numbers, an append-only export log and hash-verifiable archives for every issued document.
Token hygiene
Invitation and action tokens are 256-bit, single-use and stored only as hashes. PO links never mutate on open.
Signatures by trigger
Crew attestations are stamped in the database itself. No client, including ours, can write a signature.
Separation of duties
Completers cannot approve their own work orders, verify their own corrective actions, or settle their own claims.
567
RLS policies
325
database functions
244
tenant-scoped tables