Solutions · Prove

A Salesforce audit trail that answers who changed it, who could, and what broke

Auditors, managers and your own team ask three kinds of question: what changed, who was allowed to change it, and what quietly stopped working. Three apps keep the evidence for each.

The job, and why it hurts

An auditor’s email has three lines. Who changed the discount on this deal? Who is allowed to export customer data? And can you show that someone reviewed that access this year? While you work out the answers, an integration owner mentions that the nightly sync hasn’t run since Tuesday.

Different questions, same gap: nothing was keeping the receipt. Native Field History Tracking covers 20 fields per object and keeps changes for a fixed period, so the field everyone argues about is often not in it. Access is spread across profiles, permission sets and their clones. Failures sit in a log object nobody opens, and a job that stops writes nothing at all.

So the evidence gets rebuilt by hand, after the question arrives, from spreadsheets and memory.

The apps behind a Salesforce audit trail

Where things stand. Wake and Telltale are in early access with design partners. Watchbill is pre-release: built and install-tested.

Wake: field history beyond 20 fields, with a restore

Wake, by GTM Cloud, logs changes to the fields and objects you choose, with the old value, the new value, who changed it and when, and you set how long history is kept. It sits beside Salesforce’s own history on the record, marked by source. Anyone who can edit a field can restore an earlier value from a logged row, and the restore is logged too. See how Wake keeps field history.

Watchbill: who can do what, and who signed it off (pre-release)

Watchbill, by GTM Cloud, is a user access review tool. Today it traces every permission to the profile, set or group that grants it, compares two users or two permission sets side by side, and answers who can edit a field or holds a high-risk permission. Scheduled snapshots, a change history and review campaigns with a sign-off are in the app. See what Watchbill does today.

Telltale: know when something breaks, and when it goes quiet

Telltale, by GTM Cloud, reads the logs your org already writes and groups repeated errors into issues with a count. Rules can run a Flow, Apex, a notification, an email or a platform event, and a heartbeat raises an issue when a job that should report in doesn’t. Read about Telltale’s issues and heartbeats.

How they hand off to each other

They answer three different questions, so there’s no strict order. A typical audit week uses them like this:

  1. Wake answers what changed, on the fields you chose to watch.
  2. Watchbill answers who could have changed it, and, once review campaigns are built, who signed off on that access.
  3. Telltale answers what failed along the way, including the job that never ran.

Each installs alone and works without the others. Start with the question that’s open on your desk. None needs another.

See it first. Take it back. Keep the receipt.

Wake exports the audit log to CSV and can restore a value. Watchbill reads access and changes none, so there’s nothing to take back, and its snapshots and sign-off records arrive as they’re built. Telltale lets you reopen an issue and start any action as a dry run. The whole idea is on the preview, undo and prove page.

When a person should help

Preparing for an audit and not sure what evidence you can already produce? Our Salesforce services team can work through it with you, from what to track to who should review it. A Data Health Check looks at data quality, not access.

Questions people ask

How do I track who changed a field in Salesforce?

Turn on field history for the fields that matter, and check the limits first: native Field History Tracking covers 20 fields per object and keeps changes for a fixed period. Beyond that you need a second log. Wake records old value, new value, who and when for the fields you choose, from the day you start.

How do I audit who has access to what in Salesforce?

Start from the person: list every permission with the profile, set or group that grants it. Then go the other way, asking who can edit a field or holds a high-risk permission. Watchbill does both today in its explorer and search, and it changes nothing in your permission model.

How do I prepare for a Salesforce compliance audit?

Gather three things before anyone asks: who has access and why, evidence that someone reviewed it, and a history of changes to the fields in scope. Decide the retention period for each and where it’s kept. Then practice producing them once, so the first time isn’t the audit.

Can I restore a previous field value in Salesforce?

With Wake, yes, for changes made after you started monitoring the field. Anyone who can edit the field gets Restore This Value on any logged row, and the restore is logged too. Earlier changes aren’t back-filled, so start monitoring before you need the history.

How do I get alerted when a Salesforce integration fails?

Point a monitor at wherever the integration writes its errors, write a rule for the error, and attach a notification or email. Add a heartbeat so a run that never happens raises an issue as well. Telltale does this, and groups repeats into one issue with a count.

Pick the question you dread being asked

Book a Data Health Check, or tell us which field, permission or job the auditor will ask about first.