Your audit trail

Everything that changes a record or uses a privilege writes an entry. You can read them.

What is recorded

Who did it, when, what record, and what changed. For the record types that keep old and new values, the entry carries both, which is what makes a question like "what did this say in March" answerable rather than a guess.

Support actions taken under your consent are recorded as support actions rather than as yours.

Why it is chained

Each entry is linked to the one before it. Removing an entry, or editing one, breaks the chain, and a broken chain is detectable rather than invisible.

An audit trail somebody can quietly edit is not evidence of anything. This one can be verified.

What proves it worked

Change something on a record, then open the audit view for it. Your change is there with your name, the time, and the values on both sides.

What it is useful for beyond compliance

Two things come up far more often than an audit.

Answering a client. "Who changed the settlement date and when" is a question with a real answer, in seconds.

Debugging. Every request carries an identifier that appears in the audit row, in our logs and in our error tracking. If you quote it on a ticket, the whole path is reconstructable rather than described from memory.

What you can export

The entries, with everything else, through the ordinary export. They are your records.

Retention

Audit entries are kept for the period in your agreement, which is longer than the retention on most other record types, and they are not thinned when other data is aggregated.

Who in your business can read it

The same visibility rules that apply everywhere else. A person who cannot see a record cannot see its audit entries either, which is why the trail is safe to expose inside your business rather than being an administrator-only screen.