Platform
Who changed what, is never a mystery.
Every sensitive write lands in an append-only audit trail, atomically with the change itself. Filter it, read the detail, and follow the link straight to the affected record.
Sound familiar?
Who refunded this?
When the money moved and nobody remembers why, the audit trail is the difference between an answer and an argument.
Compliance asks, you scramble
SOC-flavored questions need an actual trail, not a spreadsheet you start today. This one has been writing since day one.
Trails scattered across tools
Deploy logs here, admin notes there. One workspace-scoped, append-only log keeps the story in a single place, and links to the records.
Accountability by default
01Atomic with the writeThe audit entry commits in the same transaction as the change. There's no state where one exists without the other.
02Append-onlyEntries are never updated or deleted. The trail you read is the trail that happened.
03Filterable streamsQuery by actor, action, or resource, the same hybrid filter power as the orders table.
04Detail panelsEach entry opens to a readable diff of what changed, in a catalog of human-named actions.
05Links to the recordJump from the entry straight to the order, event, or member it touched.
06Workspace and platform scopesTeams see their own workspace's trail; platform operators get the cross-workspace view, itself audited.
Reading the trail
- 01It writes itselfSensitive changes record automatically, no opt-in, no extra step.
- 02Filter the questionActor, action, resource. Narrow the stream to what you're asking.
- 03Follow the linkOpen the affected record and close the loop.
See your trail
Every change in the demo workspace is already logged.