/activities
Every meaningful change on the platform is recorded in an append-only audit trail. Records are
never edited or deleted from it — which is what makes it usable as evidence rather than as a
convenience.
What is recorded
System-made changes are recorded with the job as the actor, not as an anonymous change. A
change made by the collections sweep is distinguishable from one made by a person, which matters
enormously when reconstructing what happened.
Reasons are mandatory where it counts
Actions that materially change a position or override a computed result require a reason before they will save. On a collections case, for example, that includes putting a case on hold, skipping a staged action, and overriding a score. The reason is stored with the event, not in a note somebody may or may not write.Where audit shows up
The central activity list is the cross-cutting view. Individual records also carry their own history:Using the trail
1
Start from the record, not the log
A record’s own timeline is narrower and usually answers the question immediately.
2
Use the central log for cross-record questions
“What did this user do yesterday?” or “what changed across the branch on the 14th?”.
3
Compare before and after
The values, not just the fact of a change.
4
Check the actor type
A job-made change points at configuration; a user-made change points at process.
Typical investigations
What the audit trail is not
- Not a backup. It records changes; it does not restore prior states.
- Not a substitute for reconciliation. It tells you what happened, not whether the result is right.
- Not editable. If an entry is wrong, the correction is a new event, not an amendment.
Retention and access
The trail contains personal data and financial detail. Access is permission-controlled through the Activity Logs permission set, and retention follows your organisation’s policy. See Roles and permissions.Related
Approvals
Decisions, deciders and reasons.
Platform health
Automated detection of data problems.