Field history tracking for the User object: what it covers and what it doesn’t
The short answer: In Winter ’27, Salesforce lets you track up to 20 fields on the User object, including Profile, Role, Is Active and Manager, with old value, new value, who and when. Salesforce Ben’s release roundup calls it generally available, while the Setup toggle still reads Beta. It doesn’t replace Setup Audit Trail or Login History. Those log different things.
An auditor asks a plain question: “Who moved Dana from Sales Rep to System Administrator, and when?” You open Dana’s user record. The record shows the profile she has now. It has never shown the one she had on Tuesday.
Until now, answering that meant a custom trigger, a third-party package, or a lot of squinting at Setup Audit Trail. User field history tracking in Salesforce closes part of that gap. Only part, and it helps to know which part before you rely on it.
Features vary by edition and license. Check the release notes for your org before you rely on any of this.
What does user field history tracking record?
It records changes to the User fields you select, with the old value, the new value, a timestamp and the user who made the change. As reported by the Salesforce Break recap of Winter ’27, changes made through the UI, bulk operations, Apex and the API are all captured. You can track a maximum of 20 fields.
You can’t choose any field. Salesforce Help gives a fixed list: Name, Alias, Company Name, Division, Department, Title, Address, Phone, Extension, Time, Locale, Language, Mobile Phone, Start Day, End Day, Email, Manager, Contact, Is Active, Profile, Role, Username and Delegated Approver. Custom fields with Auto Number, Formula, Rich Text Area and Long Text Area data types aren’t tracked.
Help also notes tracking applies to internal users only. And the history appears on the user’s access summary page, not in a related list on the User record.
Is it generally available or still in beta?
Both labels are in circulation. Salesforce Ben’s Winter ’27 roundup titles the item “Generally Available” and says it is “now generally available”, and a second Salesforce Ben piece says not to be surprised if the UI still shows a beta label. The Setup toggle is named User Field History Tracking (Beta), and Salesforce Help uses that same name.
So the feature is described as GA while the control is labeled Beta. We can’t resolve that from the outside. Another recap, from Salesforce Break, says it moved from beta in Winter ’26 to GA in Winter ’27. Read the release notes for your org, and test in a sandbox before you build an audit process around it.
Treat it as available, labeled Beta, and verify in your own org.
Where do you turn it on?
Salesforce Ben reports the switch is in Setup, under User Management Settings: enable User Field History Tracking (Beta). Salesforce Help names the setting but doesn’t give a path in the part we read, so confirm the location in your org. The Metadata API reference lists a matching userFieldHistoryTracking setting on UserManagementSettings, which matters if you deploy settings between orgs.
Then pick the fields:
- In Setup, enable User Field History Tracking (Beta).
- Choose the fields to track, up to 20. Salesforce Ben says you configure them once the setting is on. Salesforce Break describes the route as Object Manager, User, Fields & Relationships.
- Open a user’s access summary page to read the history.
Per Salesforce Help, if you turn the setting off and on again, the fields you selected stay selected, and changes made while it was on stay recorded. Tracking is not retroactive: changes before you switch it on aren’t there.
Which User fields are worth tracking?
Start with the four that change what a person can do or who they answer to: Profile, Role, Is Active and Manager. That is opinion, but it is easy to defend.
| Field | Why track it |
|---|---|
| Profile | The biggest lever on what a user can do. The question “when did this person become an admin?” is answered here |
| Role | Changes what record access they inherit through the hierarchy |
| Is Active | Shows when someone was frozen out or switched back on, which matters at leaver time |
| Manager | Drives approval routing and escalation in many orgs, and nobody remembers changing it |
| Username, Email | Identity fields. A changed email on an active user is worth a look. Email is available for tracking only after it has been verified, per Help |
| Delegated Approver | Quietly reroutes approvals |
Leave Locale, Language and Title for later. You have 20 slots and no reason to fill them on day one.
What does it not replace?
It doesn’t replace Setup Audit Trail, Login History or a user access review, because each answers a different question.
- Setup Audit Trail logs admin and configuration activity, such as profile and permission changes, per Salesforce Help. Salesforce keeps a limited history and recommends exporting the trail every six months. Winter ’27 also adds a dedicated View Setup Audit Trail permission, as reported by Salesforce Ben, which we cover in the post on that permission.
- Login History shows who logged in, when and from where. Salesforce Help says the page shows up to 20,000 records from the past six months, with CSV and GZIP downloads for more.
- Permission set assignments aren’t on the list of trackable User fields. If your question is “who was given this permission set?”, field history on the User object won’t answer it.
- Role assignments on the Roles Setup page aren’t tracked, according to Salesforce Help. If you change roles that way, field history won’t see it. That is a gap you should know about before an auditor finds it.
Native history also has a retention limit. Salesforce Help’s general rule is about 18 months in the UI, and the User section we read doesn’t state a different figure, so confirm it for this object. If you need to know who has access today and why, as opposed to what changed, see our post on how to run a user access review in Salesforce.
What to do Monday:
1. In a sandbox, find User Field History Tracking (Beta) under User Management Settings and switch it on.
2. Select Profile, Role, Is Active and Manager, plus Username and Delegated Approver if you use them.
3. Change a test user’s profile, then open their access summary page and confirm you can read the old value, new value and who changed it.
4. Diary a six-month reminder to export Setup Audit Trail and Login History.
Where we come in
Native User history is good for the 20 fields it allows. For other objects where you need more fields or longer retention, Wake, by GTM Cloud, is in early access: it logs changes to fields you choose and keeps them for as long as you decide, beside Salesforce’s own history. Its page doesn’t describe User object support, so ask before assuming. Details are on the Wake page.
Questions people ask
How many fields can you track on the User object?
Up to 20, chosen from a fixed list that includes Profile, Role, Manager, Is Active, Email and Username, per Salesforce Help. Custom User fields of types Auto Number, Formula, Rich Text Area and Long Text Area can’t be tracked. Tracking covers internal users only.
Is user field history tracking generally available?
Salesforce Ben reports it as generally available in Winter ’27, yet the Setup setting and the Salesforce Help page still call it User Field History Tracking (Beta). The sources describe it differently, so check the release notes for your edition and test it in a sandbox before relying on it.
Does it show who gave someone a permission set?
No. Permission set assignments aren’t among the User fields Salesforce lets you track. Setup Audit Trail logs admin changes such as permission changes, so start there. Salesforce keeps only a limited history natively, so export it regularly, store the copy somewhere safe, and keep a note of who owns that job.
Sources
- Top 12 Winter ’27 features for admins, as reported by Salesforce Ben: GA heading, Beta toggle, Setup path, 20-field limit, View Setup Audit Trail permission.
- Field History Tracking overview, Salesforce Help: trackable User fields, Beta setting name, access summary page, internal users only, untracked types, Roles Setup page gap.
- Winter ’27 admin highlights, as reported by Salesforce Break: captured change sources, Object Manager route, Winter ’26 beta claim.
- Salesforce Winter ’27 is live, as reported by Salesforce Ben: generally available, beta label may still show.
- Setup Audit Trail Control, Salesforce Help: what Setup Audit Trail logs, limited retention, six-month export.
- Monitor Login History, Salesforce Help: 20,000 records, six months, CSV and GZIP.
- UserManagementSettings, Metadata API reference: the userFieldHistoryTracking setting.