The new View Setup Audit Trail permission, and why your auditor will like it

The short answer: Salesforce is adding a dedicated View Setup Audit Trail permission as a release update. Instead of giving an auditor View Setup and Configuration, which opens most of Setup, you grant only this one. Existing access is preserved when it’s enforced. It shows setup changes for 180 days, and it does not record changes to your data.

The auditor’s email asks for “evidence of who changed the sharing settings this year.” You’re happy to help. The only way to let her read the audit trail has been View Setup, and View Setup lets her read your whole configuration: every profile, every integration setting, every permission set. So you do what most admins do. You log in, download the CSV yourself, and email it. Then she asks for it again next quarter.

Features vary by edition and license. Check the release notes for your org before you rely on any of this.

What is the View Setup Audit Trail permission?

It’s a new, separate permission that controls access to the Setup Audit Trail. Per Salesforce Ben, users no longer need the broader View Setup permission to read it. It’s a release update, and Salesforce Ben says existing users keep their access automatically.

The case for it is least privilege. The current requirement, View Setup and Configuration, also lets people view the rest of Setup, as Salesforce Ben’s Spring ’27 preview puts it. An auditor, a compliance analyst or a security lead who needs the log gets the log and nothing else.

When does it take effect?

Sources disagree, so check the Release Updates screen in your org. Salesforce Ben lists the update in its Winter ’27 admin features. Salesforce Break says it’s enforced in Spring ’27, and a second Salesforce Ben article says enforcement starts in January 2027. Salesforce can also delay, change or cancel updates.

What both describe about the switchover is the same. At enforcement, any profile or permission set that already has View Setup and Configuration also gets View Setup Audit Trail, so nobody loses access. New profiles, permission sets and users get it only if you assign it. Your Salesforce Trust page gives your instance’s date.

How do you give an auditor read access without View Setup?

Create a permission set that contains only View Setup Audit Trail, and assign it to the auditor. Salesforce Ben recommends granting it on its own for audit-trail-only access and using permission sets or permission set groups rather than profiles where you can.

  1. Setup > Permission Sets > New. Name it for what it does, such as “Setup audit trail reader”.
  2. Under System Permissions, select View Setup Audit Trail and save. The permission should appear once the release update is active in your org. We haven’t confirmed its exact location in that list, so check there first.
  3. Assign it to the auditor’s user, ideally for a set period, and note the date in your change log.
  4. Test it: log in as a similar user in a sandbox and confirm the audit trail opens and the rest of Setup doesn’t.

An auditor with no Salesforce license can’t use any of this. They need a user. That’s one more reason many admins keep sending CSVs, and it’s fine to keep doing it if the audit is a one-off.

What does the Setup Audit Trail record, and for how long?

It records configuration changes: who changed what in Setup, and when. According to Salesforce Help, the page lists the date, the user and what the change was, shows the 20 most recent changes on screen, and lets you download the past 180 days. After 180 days, setup entries are deleted.

Per Salesforce Ben, the log covers things like permission and permission set changes, user assignments, object and field changes, sharing defaults, Flow and Apex class changes, and Login-As use. The detail varies. For page layouts you may see only that a change happened. Sharing rules aren’t itemized, though org-wide default changes are. Apex shows that a class changed, not the code, so it doesn’t replace version control.

The developer documentation also describes a SetupAuditTrail object you can query through the API, which is how you’d copy entries somewhere durable before the 180 days run out. Gearset’s guide reports that exports are held for 72 hours in the Audit Trail Export Dashboard, so download and file them straight away.

What does the audit trail not cover?

It logs setup changes, not data changes. If the question is “who changed the amount on this opportunity,” the audit trail has nothing. That job belongs to Field History Tracking, which covers up to 20 fields per object and has to be turned on field by field. Gearset reports retention of about 18 months in the UI, or 24 through the API.

It also isn’t a record of what people viewed, exported or ran. Per Gearset’s guide, individual report exports and detailed user activity need Event Monitoring. And it can’t tell you who could do something, only who changed the settings. Three questions, three sources: the audit trail answers who changed the setup, field history answers who changed the data, and a user access review answers who is allowed to do what today.

What to do Monday:

1. Open Setup > Release Updates and read the View Setup Audit Trail entry and its date.

2. Count who holds View Setup and Configuration, then ask each group whether they need it or only need the log.

3. Build the “Setup audit trail reader” permission set now, so it’s ready.

4. Put a recurring reminder in your calendar to export the trail before 180 days pass.

Where we come in

Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. Today it shows what each person can do and which profile or permission set grants it, and compares two users or sets side by side. It also keeps snapshots and a change history and runs review campaigns. It reads access and changes none, and it isn’t a replacement for the Setup Audit Trail. Join the Watchbill pilot if access reviews are your headache.

Questions people ask

Can anyone see the Setup Audit Trail today?

Per Salesforce Help and Salesforce Ben, users need the View Setup and Configuration permission. Older guides say system administrators only, but the permission is what controls it. After enforcement of the release update, View Setup Audit Trail becomes the dedicated permission, and existing View Setup holders get it automatically.

Does the Setup Audit Trail log data changes?

No. It logs configuration changes such as permissions, fields and Flows. Changes to record values are the job of Field History Tracking, with its 20-field limit per object, or of an extension that keeps longer history. Wake, by GTM Cloud, is one, in early access. For activity like report exports, you need Event Monitoring.

How long does Salesforce keep the Setup Audit Trail?

Salesforce Help says the downloadable history covers 180 days, after which entries are deleted, and that the page shows only the last 20. If an auditor needs a full year, you have to export on a schedule and keep the files yourself.

Sources