Salesforce Winter ’27 release notes: the changes admins should care about

The short answer: Four Winter ’27 changes need action: Profile Filtering is enforced, tokens and OAuth flows are tightening, SOAP login() needs a permission, and a View Setup Audit Trail permission is on its way. Four more are worth switching on when you’re ready. The remaining items, mostly AI and security features, are good to know about before someone asks.

The release notes are hundreds of pages long, and Winter ’27 has already reached production orgs. Salesforce’s own schedule had waves from early September to early October, as reported by Salesforce Dictionary. The risk is rarely the headline feature. It’s the quiet one: a Flow that suddenly sees a blank profile name, an integration that stops logging in on a Monday. So this is the shortlist we’d read first, in the order we’d act on it.

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

Which Winter ’27 changes need action before anything else?

Four changes can break something that works today, so read these first. Each has a status, because Salesforce changes dates more often than people remember.

Profile Filtering (release update, enforced in Winter ’27). Users see only their own profile name unless they hold View All Profiles, according to Salesforce Ben. It was added in Summer ’26. Any Flow, validation rule or Apex that reads another user’s profile name can quietly stop working. We cover the checks in profile filtering is enforced in Winter ’27.

View Setup Audit Trail permission (release update). Access to the Setup Audit Trail gets its own permission, so an auditor no longer needs the broader View Setup. Existing access is preserved. Sources disagree on timing: Salesforce Ben lists it in the Winter ’27 notes, while Salesforce Break and a second Salesforce Ben article report enforcement in Spring ’27, from January 2027. The detail is in the View Setup Audit Trail post.

Refresh tokens and OAuth flows (release updates, dated). Per Salesforce’s architect highlights, production refresh tokens expire after 30 days of inactivity from November 4, 2026. The OAuth 2.0 device flow is restricted from November 30, 2026. The username-password, user-agent and hybrid user-agent flows retire on February 20, 2027. A quarterly integration that logs in once every 90 days is the one that gets caught.

SOAP API login() (release update, as reported). Salesforce Dictionary reports that Winter ’27 enforces the PermissionsUseAnyApiAuth permission for SOAP login() calls, and that users without it get an error instead of a session. We found no primary source we could open for this one, so confirm it in Setup > Release Updates.

Which Winter ’27 features are worth turning on?

Four items are optional and off by default, so you choose the moment.

Keep Manual Shares When Transferring Records. Setup > Sharing Settings > Edit. When on, manual shares survive an owner change, for all records, with no per-record control. Salesforce’s architect post advises checking which processes rely on owner changes to remove access first. Our walk-through: manual shares and owner changes.

User Field History Tracking. Salesforce Ben reports it as generally available, with up to 20 fields on the User object. The Setup toggle (User Management Settings) still reads “(Beta)”, so the label and the status don’t match. Worth enabling for the fields people ask “who changed that?” about, such as Profile, Role and IsActive. See what user field history covers.

Flexible inline editing in list views. Two optional settings under User Interface in Setup: one removes the dependence on page layouts, so users can edit any field they have access to. The other allows inline edits in list views with multiple record types. Turn on the first and you’ve changed who can edit what from a list, so test it against field-level security you thought was belt and braces.

Setup with Agentforce enhancements. Salesforce’s blog lists these as generally available. Per Salesforce Ben, they include managing Dynamic Actions on mobile and creating related list enrichments by describing what you want. Treat the output like any other change: look at it in a sandbox before production.

What else is in Winter ’27 that is good to know?

Several items are more about being able to answer a question than doing a task. The status matters more here than anywhere.

  • MCP Risk Scores in Security Center (GA). Each third-party MCP server gets a Low, Medium or High rating, scanned at registration and monitored afterward, per Salesforce’s blog of October 13, 2026. Admins can block high-risk servers. Relevant if anyone in your org has connected an agent to something outside Salesforce. More in MCP risk scores in Security Center.
  • Observability Center (beta). A single console for tracing agent sessions and errors. Beta, so no production dependencies yet.
  • Lifecycle Center (GA). The new name for DevOps Center, with approvals and audit logging for agent-generated code.
  • Preview records from Lightning reports (beta). The eye icon opens a record in a sidebar without leaving the report.
  • SOQL FORMULA() in WHERE (beta). Sandboxes, Developer Editions and scratch orgs on API 68.0 or later. Not available in production.

How do release updates and dates actually work?

Release updates are dated by Salesforce, but the dates move. Setup > Release Updates shows what applies to your org and, where there’s a Test Run, lets you try it first. The date for your instance is the one published on Salesforce Trust.

Two examples from this cycle. Salesforce Dictionary reports the OAuth username-password retirement moved out of Winter ’27 to February 20, 2027, and that an email-domain update was cancelled and replaced by another with a December 1, 2026 date. Check the live screen, not a blog post from August, this one included.

How do you check a release against your own org?

Search your metadata for what the release touches, then test in a sandbox as a person who isn’t you. A system administrator passes tests that a sales rep fails.

  1. Open Setup > Release Updates and list everything marked as enforced or upcoming.
  2. For each, search Flows, validation rules, formula fields, Apex and reports for the thing it changes.
  3. Use login-as on a standard-user profile in a sandbox that has the update on.
  4. Ask the vendor of any managed package whether it’s ready.
  5. Write the result down, even if the result is “nothing found.” Next release you’ll want it.

What to do Monday:

1. Open Setup > Release Updates and screenshot the list with its dates.

2. Search your Flows and validation rules for references to another user’s profile name.

3. List every integration that hasn’t logged in for 30 days, and check its refresh token.

4. Count who holds View Setup, and decide who really needs it.

Where we come in

Reading release notes against a real org is a few hours three times a year, and it’s exactly what slips when the backlog is long. We write up what changed and what to do about it in The Fix, our newsletter for admins. It doesn’t read your org for you, and it won’t replace a sandbox test, but it tells you which pages to open.

Questions people ask

When was Winter ’27 released?

Salesforce rolled Winter ’27 out to production in waves. Salesforce Dictionary reports September 4, October 2 and October 9, 2026, with the date for your instance on Salesforce Trust governing your org. Sandbox preview came earlier. By now, your org has very likely upgraded.

Are the Winter ’27 features all generally available?

No. Salesforce’s blog says its platform features are generally available unless noted, and marks Observability Center as beta. Salesforce Ben lists report record preview and SOQL FORMULA() as beta too, and User Field History Tracking as generally available despite a Setup label that says Beta. Check each release note.

Can you delay a release update?

Sometimes. Salesforce publishes an enforcement date for each, and most have a Test Run or a way to enable them early. Once enforced, you generally can’t opt out. Salesforce may also delay, change or cancel an update, so recheck the dates in Setup before you plan around them.

Sources