History & Audit Trail
Every tracked change keeps its own line in history — who changed it, when, and exactly what the value was before. And deleting a record takes it out of the way without taking it out of existence.
The History tab, which the platform adds to any record type set to keep history. The premium, the sum insured and the owner each kept the value they held before.
Before and after, per field
History records the individual field that changed with its old and new value, not just that someone edited the record.
Enforced by the database
Tracking runs at the database level, so an import, an integration or a script cannot write around it.
Who did what, separately
An operation-level log records the action and the user behind it, alongside the field-by-field history.
Track only what matters
History is a setting per record type and per field, so the trail holds what a regulator will actually ask for.
Deleted, not destroyed
Deleting marks the record and stores who did it and when. The row stays in the database rather than being removed from it.
Answerable months later
Because nothing is physically removed, a dispute raised long after the fact can still be answered from the data itself.
Where you'll use it
Why we like this one
Audit is usually bolted on after a compliance team asks an uncomfortable question — a logging module that covers the screens people use and misses the integrations that don't. Tracking that lives with the record means the answer is already there, whoever made the change, and a record nobody can destroy is what lets a team keep its data tidy without fearing the delete button.
More in Platform Essentials