Who Changed This in Salesforce? Field History Tracking and Setup Audit Trail Explained
"Who changed this?" is one of the most common questions a Salesforce admin gets. It sounds like one question, but in Salesforce it has two different answers, depending on what changed:
- A value on a record changed, for example a Lead status. That is Field History Tracking.
- A setting in the org changed, for example a field made required. That is the Setup Audit Trail.
Neither feature can see what the other records. This guide explains how each one works, how far back it goes, and what to do when neither has the answer.
Quick comparison
| Field History Tracking | Setup Audit Trail | |
|---|---|---|
| Answers | Who changed a value on a record | Who changed a setting in the org |
| Needs to be turned on? | Yes, field by field | No, always on |
| Where to find it | The History related list on the record, or reports | Setup, then View Setup Audit Trail |
| Permission to view or set up | Customize Application to set up | View Setup and Configuration |
| How far back | From the moment you turned it on, kept for a limited time | 180 days |
Start with Last Modified By
Before opening either feature, look at the Last Modified By field on the record. It is already on every record and needs no setup. Salesforce even lists "Created By and Last Modified By" among fields you cannot add to history tracking, because they are already there. It only shows the most recent change, but very often that is all you need.
Field History Tracking: changes to records
Field History Tracking lets you "select certain fields to track and show field history in an object history list." Once a field is tracked, "when you modify a field on a supported object, Salesforce adds an entry to the History related list," and "all entries include the date, time, nature of the change, and who made the change."
The history is stored in a related object such as AccountHistory, so you can report on it, not just view it on the record.
How to turn it on: in Setup, use Quick Find to open Field History Tracking for the object, then choose the fields. You need the Customize Application permission. Then add the history related list to the page layout so people can actually see it.
Limits to know: you can track "up to 20 standard and custom fields per object," and history is kept "for up to 18 months, and up to 24 months via the API" unless your org uses Field Audit Trail. Salesforce also notes that "field history tracking data does not count against storage limits" and that "changes can take a few minutes to a few hours to appear in history."
Setup Audit Trail: changes to settings
"Setup Audit Trail tracks the recent setup changes that you and other admins make," and Salesforce notes that "audit history is especially useful when there are multiple admins." There is nothing to switch on.
How to open it: "From Setup, use the Quick Find box to find and select View Setup Audit Trail." You need the View Setup and Configuration permission. The page "shows the 20 most recent setup changes made to your org," with the date, who made the change and what changed. "To download your org's complete setup history for the past 180 days, click Download."
Blind spots: when the answer is not there
Both features have gaps you should know before you promise someone an answer:
- The setup trail expires. "After 180 days, setup entity records are deleted."
- Field history only starts when you turn it on. "Salesforce starts tracking field history from the date and time that you turn it on a field," and earlier changes are not recorded. This is common in inherited orgs.
- Some automated changes are not recorded. Field history "doesn't record changes that occur in the system context." If a Flow or Apex trigger changes a field the current user cannot edit, "Salesforce doesn't track that change."
- Long text fields show limited detail. For long text fields over 255 characters, Salesforce "records only that the field was edited" and "doesn't store or display the actual before and after values."
What to say when there is no answer
- Check Last Modified By.
- Decide which trail fits the question: record or setting.
- If the trail is empty, explain which blind spot applies.
- Turn on what is needed so the question can be answered next time, after agreeing with the team which fields are worth tracking.
"The org cannot tell us yet, here is why, and here is what I have turned on" is a much better answer than a guess.
Practice in a free org
In a free Developer Edition org, turn on history tracking for one Account field, add the history related list to the layout, change the value twice and read the rows. Then open View Setup Audit Trail and find the entry for the tracking change you just made.
Related reading
- Before You Add a Custom Field in Salesforce: includes when a new field needs history tracking.
- What does a Salesforce admin actually do all day?
- Your first 90 days as a Salesforce admin: turning on the right tracking early.
- Our Substack post Two Trails, and Neither Sees the Other is a shorter read on the same idea.
Frequently asked questions
How do I see who changed a field in Salesforce? Check Last Modified By for the most recent change. For older changes, use the History related list, which works only if Field History Tracking was on for that field at the time.
How do I see who changed a setting in Salesforce? Open View Setup Audit Trail in Setup. It shows the 20 most recent changes, and you can download the last 180 days.
How far back does the Setup Audit Trail go? 180 days. After that, Salesforce deletes the records.
Why is a change missing from field history? Tracking may have been turned on after the change, the change may have happened in system context through automation, or the field may be a long text field that records only that it was edited.
Blazer2Role helps career changers move into Salesforce roles, and we sell coaching and courses. Platform behavior and limits vary by edition and change over time, so check current Salesforce documentation for your org. Drafted with AI assistance under Blazer2Role's editorial direction.