In October, Salesforce rolled out its Winter release. Alongside a number of technical improvements behind the scenes, it includes features users will notice right away in their everyday work. I went through the release notes for you and picked the updates worth knowing about, whether you administer Salesforce, implement it, or analyze data in it.
What Winter ’27 improves:
- flows will always run with only the permissions of the user who launched them
- you will see a flow error at activation, before users run into it
- screen flows will process multiple selected records at once
- Setup change history can be made available without broad permissions
- list views will let you edit more fields and records of different types
- changes to user accounts will have their own history
User Permissions Run Mode
A flow running in user context could end up inheriting higher permissions from the process or user that triggered it. This opened a security “gap”.
The new run mode rules this out. The flow now works with exactly the access the user has. It pays to review flows that touch sensitive data or objects with restricted access and set the run mode for them.
Catch Flow Errors Before They Happen
In the past, a missing required field or a value longer than the field allows only showed up once the flow was running. Often it was a user who flagged the problem.
Winter ’27 catches these errors when you save and activate the flow, so you can fix them before they reach users. There is also a new automatic retry: if a flow hits a record that someone else is editing at that moment, it waits 10 seconds and tries again. This means fewer incidents caused by concurrent edits.
Bulk Processing with Screen Flows
A screen flow was always tied to a single record. Bulk editing therefore meant either repeating the same steps for each record separately or building a more complex custom solution.
With the new release, you can connect a screen flow to a mass quick action in a list view or related list. The user selects any number of records and the flow receives their IDs. From a related list, it also receives the ID of the parent record. Admins can build bulk updates, record creation or data checks declaratively.
View Setup Audit Trail Permission
Anyone who wanted to view the Setup Audit Trail needed the “View Setup” permission, and with it visibility into the entire org configuration. For auditors or security teams, that was unnecessarily broad access.
Audit Trail now has its own permission, which can be assigned through a profile or permission set. Only those who need to see the change history get access to it. Users who already have access keep it. The change will be especially welcome for European organizations preparing an access rights review ahead of an audit.
Make Inline Editing in List Views More Flexible
Editing values directly in a list view had two limitations: the field had to be on the page layout, and the list had to contain records of a single record type.
Both limitations can now be turned off in User Interface Settings:
- users can edit any field in a list view they have write access to, regardless of the layout,
- inline editing also works in lists that mix different record types.
The default settings stay as before, and an admin has to enable both options.
Enable Field History Tracking for Users
The User object was one of the places where change history was missing. Anyone who needed to document when and how user data changed had to find other ways.
You can now enable history tracking for up to 20 fields. It records edits made in the UI, mass changes and changes made through the API. You enable it in Setup under User Management Settings. Although it is labeled “Beta”, the feature is already generally available. You can use it for audits and for meeting GDPR requirements.
Conclusion
Winter ’27 brings a number of practical improvements: flows are more reliable and secure, access can be managed more precisely, and working with reports is more convenient. We recommend testing the new features in a sandbox first and then deciding which ones to start with.
