How to tell what an AI agent changed in Salesforce
The short answer: To audit AI agent changes in Salesforce, use three sources together. Field history shows old and new values for the fields you track. Setup Audit Trail shows configuration changes, including permission changes to the agent’s user. Agentforce session tracing shows what the agent did and why. None covers everything, so switch them on before the pilot, not after.
Say the pilot report lands on Monday and reads “41 opportunities updated over the weekend.” By Tuesday someone in sales leadership wants to know which 41, what the Amount said before, and whether a person approved any of it. You know the agent did something. You don’t yet know where to look for the details.
The good news is that you already own most of the tools. The awkward news is that each one answers a different question, and the gaps between them are exactly where the interesting questions fall.
Features vary by edition and license. Check the release notes for your org before you rely on any of this.
Does an AI agent run as a user in Salesforce?
Yes, but which user depends on the kind of agent. That decides whose name your audit trail shows.
As reported by Salesforce Ben, a service agent working with an unidentified or merely verified customer runs as its own agent user, which is created with the Einstein Agent license and Einstein Agent User profile and starts with minimal permissions. Only when the customer is authenticated, such as a logged-in portal user, does it run as that person. Salesforce’s Trailhead material says employee agents are logged in as the person they’re helping, using that user’s permissions and org security settings.
So two pilots can leave two different trails. A service agent’s work should point at a user you can name. An employee agent’s work points at whichever employee was chatting. Neither of the pages we read says how every agent action appears in a record’s Last Modified By field, so test it in a sandbox before you assume.
What does field history show about agent changes?
Field history shows who changed a tracked field, when, and what it was before and after. It’s the only native source that holds the “before” value, which is why it’s the first thing to switch on.
The limits matter. As reported by Salesforce Ben, you can track 20 fields per standard or custom object, tracking starts when you select a field and isn’t retroactive, and changes are kept for up to 18 months in the UI and 24 months through the API. For long text and multi-select picklists you see who and when, but not the values. Our guide to field history tracking limits covers what to do when 20 isn’t enough.
Field history also doesn’t know the change came from an agent. It records a user. If the agent has its own user, you filter on that. If it runs as an employee, an agent change and a human change look the same.
What does Setup Audit Trail show?
Setup Audit Trail shows changes to configuration, not to records. It’s the right place to answer “who changed the permissions of the agent’s user?” and the wrong place to answer “what did the agent do to opportunity 0061?”
As reported by Salesforce Ben, it records metadata changes with the user who made them, including permission and profile changes. The Setup page lists the last 20 changes, and a CSV download covers the last 180 days. Page layout and record page changes show only that something changed, not what. If you want evidence beyond 180 days, download it on a schedule and keep the file.
One Winter ’27 note: as reported by Salesforce Ben, access to the Setup Audit Trail is moving to a dedicated View Setup Audit Trail permission, as a release update. Existing access is kept automatically, so check who holds it and whether they should.
What does Agentforce tracing show?
Agentforce session tracing shows the conversation and the steps the agent took, stored as records in Data 360. It explains what the agent did and why. It’s the closest thing to a flight recorder.
Salesforce’s architecture guidance says the Session Tracing Data Model records a session as a hierarchy of interactions, steps and messages, and that action steps “record every action an agent takes including API calls, data modifications.” That’s the part that helps most with “what did it change?” Salesforce’s July 21, 2026 Observability post says Observability is included for all Agentforce customers at no additional Data Cloud cost, and describes tracing of planner decisions, prompt and action flows, errors and final output. That post doesn’t use the term “GA”, and it mentions a rollout in August. The Winter ’27 platform blog marks Observability Center, the console view, as beta.
Two prerequisites to check. Per the architecture guide, audit data is captured in Data 360 only when Audit and Feedback is turned on, on the Einstein Audit, Analytics, and Monitoring Setup page, and it’s on by default when Agentforce is turned on in an org with a single dataspace. And none of the Salesforce pages we read says tracing stores the previous value of each changed field. Don’t assume it does.
What does each source miss?
| Source | Answers | Doesn’t answer |
|---|---|---|
| Field history | What a tracked field was, and became, and who changed it | Untracked fields; whether an agent was behind it; long text values |
| Setup Audit Trail | Who changed permissions or configuration | Anything about record data |
| Agentforce session tracing | What the agent did, in what order, and why | Confirmed before values; changes made outside the agent |
| Record owner and Last Modified By | Which user touched the record last | Anything earlier than the last touch |
The honest summary: field history gives you the numbers, tracing gives you the story, and Setup Audit Trail tells you whether someone widened the agent’s access along the way.
What should you set up before an agent pilot?
Set up four things, in this order. Each takes under an hour.
- Give the agent its own named user wherever the agent type allows it, and note the user’s name in your pilot document. Shared logins make the trail unreadable.
- List the fields the agent might change and turn on field history for each. If the list is longer than 20 for one object, shorten the pilot’s scope.
- Confirm Audit and Feedback is on, and name who can query the tracing data. A trace nobody can read is a decoration.
- Rehearse one question in a sandbox. Have the agent change one record, then try to answer “what, when, who, before and after” using only these sources. Where you get stuck is your gap.
What to do Monday:
– Find out which kind of agent your pilot uses and which user it will run as.
– Turn on field history for the five fields you’d least like to lose track of.
– Open Setup and check whether Audit and Feedback is on for the agent’s org.
– Run the sandbox rehearsal above and write down what you couldn’t answer.
For the wider checklist behind a pilot, our post on Agentforce data readiness and the Agentforce Readiness Sprint cover the data and access side.
Where we come in
Wake, by GTM Cloud, is in early access. It logs changes to the fields and objects you choose, beyond the native 20-field limit, with old value, new value, who and when, and lets you restore a value. A dedicated agent view is planned, not built. Tiller, an agent action ledger, is in design and possibly never built: we’re first checking what the platform already records. Read the Wake page for the limits.
Questions people ask
Does Salesforce log what Agentforce changes?
Partly. Agentforce session tracing records the agent’s steps, including data modification actions, in Data 360. Field history records old and new values for tracked fields. No single log covers both, and Salesforce’s pages we read don’t say tracing keeps before values.
Can I see why an agent made a change?
Yes, that’s what session tracing is for. It records planner decisions, prompt and action flows and errors, so you can follow the reasoning path. It needs Audit and Feedback turned on in Data 360. Field history can’t give you the why, only the what.
Is there an undo for an agent’s changes?
We found nothing in the Salesforce pages we read that offers a one-click undo for an agent run. Field history lets you read the old value and re-enter it by hand, record by record. Anything faster needs a tool that stores before values and can restore them, or a data load you build from an export. Decide that before the pilot.
Sources
- Salesforce Ben: Agentforce permissions explained: as reported, which user a service agent runs as and its license and profile.
- Get started with Agentforce for employees (Trailhead): employee agents run as the person they help.
- Salesforce: Agentforce Observability: July 21, 2026 post on session tracing and the data model.
- Operational Excellence for the Agentic Enterprise (Salesforce Architects): action steps, trace hierarchy and the Audit and Feedback prerequisite.
- Platform Winter ’27 release (Salesforce blog): Observability Center marked beta.
- Salesforce Ben: field history tracking: as reported, limits, retention and what is recorded.
- Salesforce Ben: Setup Audit Trail: as reported, what it records, 180-day export, 20-entry view.
- Salesforce Ben: Winter ’27 features for admins: as reported, the View Setup Audit Trail release update.