Loading
A permanent record of every change: who made it, when, which field, and what the value was before. Including changes made by integrations and by automations.
The last part matters most. A trail that records people and not API writes has a gap exactly where the volume is.
Not compliance, mostly. It is for the ordinary Tuesday when a customer says a discount was agreed, a close date is disputed, or four hundred records changed overnight and nobody knows why.
Each of those is a five-minute question with a trail and an afternoon of archaeology without one.
No. That single property is what makes it usable as evidence.
It must, attributed to the token and the user behind it.
For the life of the record, subject to your own retention policy.
Half an hour with your own data usually saves reading three of these. The guides will still be here afterwards.