Change History & Corrections
Goal: See and trust the full history of your workshop - and correct data without losing the original.
OpenX keeps two kinds of history, both built in - no separate system, no setup:
- Activity log - an immutable record of every change to your workshop: who, what, when.
- Corrections - a documented way to fix recorded data that never overwrites the original.
Why it's the same canvas as everything else: history isn't a compliance bolt-on, it's how a team moves fast on shared work and safely opens building to any AI. The concept is Ship with Confidence; this is how to use it.
What makes the history trustworthy
| Quality | What it means |
|---|---|
| Attributable | Every change is tied to who made it |
| Legible | Records are readable - structured, with before/after diffs |
| Timely | Stamped server-side when it happened, not by the client |
| Original | The first record is never overwritten |
| Accurate | Each record is verifiable - tamper-evident |
| Complete | Every change is captured automatically |
| Consistent | One schema across every action |
| Enduring | Kept as long as you choose |
| Available | Query and export any time |
The two logs
- Activity log - browse, filter, verify, and export the record of what changed.
- Corrections - fix a value with a reason; the original stays; optionally require a second approver.
The history is yours
It lives in your own tenant. If you ever stop using OpenX, it stays accessible in your account - portable, exportable, owned by you. Fire us, keep running. (More in Ship with Confidence.)
Next steps
- The endpoints behind all of this -> REST API: Change history
- How review works -> Team Review & Access Rights