Audit Trails: Recording Who Changed What

Sooner or later, every organization asks a question like: "Who changed this setting?" "When was this page deleted?" "Why did this price change?" Without a record, answering means guessing, interviewing people and sometimes blaming the wrong person. With a record, it takes a minute.

Audit trails are those records. Our platform keeps them for important changes, designed to answer real questions without becoming a privacy problem of their own. Here is how.

What we record

Audit records capture the essentials of an important change:

• Who made it, tied to their account
• What changed, including the record and the kind of change
• When it happened
• Why, where a reason was given, such as a deletion reason or the source of an automated change

Important records, including content, settings and many module records, are audited automatically when they change. Deletions record who deleted an item and, where provided, why.

Revisions for content

For pages and blog posts, revision history goes further than an audit record. Each save keeps the full content, so earlier versions can be compared and restored. Each revision also records a reason, such as an editor's save, an import or an automated publishing run, which makes the history readable. You can read more in revision history for pages and posts.

AI use is audited too

Our internal AI tools record every prompt and reply, along with who used them and why. Customer AI features record measured usage and charges. Those records mean any AI-assisted work can be traced to a person and a purpose, and any AI charge can be explained. We describe that in separating internal AI tools from customer AI features.

Settings changes are traceable

Settings that affect money, security or what customers see are changed through admin screens that record the change. When a platform-wide switch is changed, such as how AI requests are routed, the change is recorded with the person who made it. Only specific people are allowed to change the most sensitive switches at all.

Secrets never enter the record

An audit trail can become a liability if it stores sensitive data. We keep passwords, keys, card details and session data out of audit records entirely. Where a change involves a secret, the record notes that the secret changed, not what it changed to. Audit records are useful precisely because they can be read without exposing anything dangerous.

Read access is limited

Audit records describe what people did, which is sensitive in its own way. Access to them is limited to people with a legitimate need, such as authorized administrators investigating a problem.

Records support fairness

Audit trails are not about suspicion. Most unexpected changes have innocent explanations: a teammate fixed something, an import updated a record, an automated process ran. Having the record lets teams find the explanation quickly and without blame. When something truly went wrong, the record shows what to fix.

Automated changes are labeled too

Not every change is made by a person clicking a button. Imports, scheduled tasks, migrations and publishing scripts also change records. Those changes are labeled with their source, such as an import run or a release, so the record does not falsely suggest a person made them. When we published this blog's article library, for example, every saved article and revision carried a reason that identifies the publishing run that created it.

Audit records support honest status

Audit trails also help us report honestly about our own work. When we say a change was made, by whom and when, the record backs it up. That fits the habit described in reporting status honestly: evidence over adjectives.

Small organizations benefit most

Large companies often have dedicated compliance staff. Small churches, nonprofits and businesses usually do not. For them, an audit trail built into the platform provides accountability that would otherwise require effort they cannot spare. When a volunteer changes a setting or a former staff member deletes something, the record is already there.

Records last as long as they are useful

Audit records should be kept long enough to answer the questions people realistically ask, with retention matched to their purpose. Financial and security questions often arise long after the fact, while routine content questions usually come quickly. Keeping everything forever is not a virtue; keeping what matters for as long as it matters is.

Frequently asked questions

What is an audit trail?

An audit trail is a record of important changes in a system, showing who made each change, what changed, when and sometimes why.

Do audit logs store passwords or card numbers?

They should not. Audit records note that sensitive values changed without storing the values themselves.

Who can see audit records?

Access is limited to people with a legitimate need, such as authorized administrators investigating a problem.