A support rep opens a colleague's user record on Monday morning and the profile name they could see on Friday is no longer there. Nothing is broken. Winter '27 enforced Profile Filtering over the weekend, and that rep does not hold View All Profiles. Most of what Winter '27 asks of admins looks like this: quiet defaults and permission changes rather than one loud feature.
This is the admin's map of Winter '27: the release updates that enforce now, the Flow Builder changes you will use every day, the setup and sharing options worth turning on, and the security dates that land between now and Summer '27. Release notes first published the week of August 17, 2026. Sandbox preview began the weekend of August 28-29, and production upgrades ran over the weekends starting September 4, October 2 and October 9, 2026. The sandbox checklist at the bottom is the order to test in.
Release updates enforced this release
Open Setup, go to Release Updates, and filter to the items due this release. The list that ships is shorter than the one circulating in August, and the five that remain are worth a careful test.
Enable Profile Filtering. First available in Summer '26 and enforced now. Users cannot see profile names other than their own unless they have View All Profiles. The trap is how you test it. If your own user holds View All Profiles, testing as yourself always passes. Use login-as against your most restricted profiles, and check the reports, flows and record pages that display another user's profile name. Assign View All Profiles through a permission set to the security admins, support engineers and licence managers who need it.
Assign Use Any API Auth Permission for SOAP login(). Every user who authenticates through the SOAP API login() call needs the Use Any API Auth permission. Salesforce enforces it uniformly from December 1, 2026, across production and sandboxes. Pull Login History for SOAP logins over the last 90 days, list the distinct users, and grant the permission to each integration user that needs it.
Three accessibility updates. Page headers and modal windows above 200% zoom (enforced now after being postponed from Summer '26), date pickers, popovers, bottom utility bars and record headers, and cards, docked containers, menu lists and panels. The page headers update is the prerequisite for the other two and supports 300 to 400% zoom. The other two target usability at 1280 pixels wide and 400% magnification. Test custom Lightning components and any AppExchange components at 400% zoom before you sign off.
Three updates left the release after the notes published, which is why some August checklists are wrong:
- Retirement of the OAuth 2.0 username-password flow for connected apps moved from Winter '27 to February 20, 2027.
- Update Instanced URLs in API Traffic moved to the Spring '27 list. Its own page describes phased enforcement, starting in sandboxes in October 2026 and production in January 2027.
- Adopt Authorized Email Domains was cancelled and replaced by Maintain Your Email Verification Exception, enforced December 1, 2026. If Salesforce Support ever switched off user email verification for your org, configure an authorized email domain and the new "Require Address Verification to Send Email" field before that date. If your Deliverability settings verify sending domains by DKIM keys, configure the authorized domain first, then turn that setting off.
Our enforcement shuffle news piece has the timeline of how the list changed.
Flow Builder: the canvas you work in every day
Flow Builder now picks up your org's SLDS 2 Cosmos theme automatically, with more spacing and an updated palette. The canvas is denser. Element cards hide the element type and API name behind an info-icon tooltip, and the End element is an icon instead of a card. Flow Builder does not support SLDS 2 dark mode yet, so do not promise it to the users who asked.
Four additions change how you maintain flows rather than how you build them:
- Edit History. A timeline of every save on the current flow version. Preview any save, see which elements changed, then restore it with Save as New Version or copy the logic out with Save as New Flow. Enterprise, Performance, Unlimited and Developer editions only.
- Unused Resources filter. In the Toolbox, choose Filter, then Unused, to list every resource nothing references. It works in auto-layout and free-form.
- Flow tags and categories. Create tag categories and tags on the Tags tab of the Automation app, then tag one flow from its row action or many at once. Salesforce pulled this feature in September and re-added it the week of November 2, so check that your org shows the Tags tab before you plan around it.
- Group elements. In auto-layout, Add to Flow, then Group, wraps related elements in a named, collapsible block.
Building gets faster too. Split by Field Value and Split by Date are new Decision element types that route records with inline pickers instead of written conditions. The Collection Filter Criteria resource returns the first matching record from a collection without a Loop element. Flow Builder now catches two common runtime errors at save: text values longer than the target field in Create Records and Update Records elements, and missing required fields in Create Records.
User Context - Enforces User Permissions is the security change hiding in the Save dialog. Under Show Advanced, How to Run the Flow, this option makes a screen or autolaunched flow always run with the running user's access, even when Apex or another flow calls it from system context. Use it on any flow that should never inherit elevated access.
One correction for anyone who read early previews: the redesigned element search and categories panel was removed from the release notes on September 14 and did not ship in Winter '27.
Flow testing finally lives in Flow Builder
Flow Test Mode started as a beta in September and Help now lists it as generally available. Turn it on under Setup, Process Automation Settings, Flow Test Mode, then click Test in Flow Builder. You build reusable test scenarios with assertions for autolaunched and record-triggered flows, and each scenario reports pass or fail. Mock outputs for Action and Subflow elements let a test run without the real callout or subflow behind it.
You can also debug with a static 15 or 18 character record ID and with primitive collection inputs. Developers can generate draft test scenarios from a terminal with headless Agentforce for Flow.
One expectation to manage: Apex is still the currency of the 75% deployment coverage gate. Our guide to Flow testing in 2026 explains why declarative tests do not count toward it.
Screen flows, quick actions and approvals
Screen flows on mass quick actions. A Flow quick action can now run against the records a user selects in a list view or related list, and the flow receives the selected record IDs. Add the action to the List View Button Layout for list views, or to the related list on the page layout. Our mass quick actions guide walks through a build pattern.
Screen flows also gain a Time component for appointment and booking inputs, and reactive formulas in conditional visibility, so a visibility rule can react to another component on the same screen. Salesforce lists that one as available from September 29, 2026.
For approvals, the Request Approvals component lets a user choose from up to 10 autolaunched flow approval processes on a record page. Add it in Lightning App Builder or on an object detail page in Experience Builder, with options to hide submitter comments or require the submitter to pick an approver. You can now set approval work items to a private sharing model, so reviewers cannot see other steps' work items, and approval admins can debug, suspend and resume submissions.
Setup, users and sharing
Org Health and Usage in Setup no longer requires Salesforce with Agentforce. Every admin gets security, performance, trust and usage metrics ranked by severity, with a Go to Page link to the related Setup page.
Field History Tracking for Users is generally available. Track up to 20 fields on the User object from Object Manager, and the history covers changes from the UI, bulk loads, Apex and the API.
Keep manual shares when transferring records is a new org setting under Sharing Settings, off by default. Until now a transfer deleted manual shares, which is how users lost access to records they had been explicitly given. Turn it on in a sandbox and run your ownership-transfer jobs before you change production.
Role Access Summary shows a role's users, hierarchy position, sharing rules and everywhere the role is referenced, including folders, public groups, queues and list views.
View Setup Audit Trail permission is a new release update enforced in Spring '27. It gives audit trail access its own permission instead of riding on View Setup. Salesforce auto-enables it on every profile and permission set that already has View Setup, so existing users keep access, but new profiles, permission sets and users need it granted explicitly.
Two list view settings arrive under User Interface Settings, both off by default: one removes the page layout dependency for inline edits, and one allows inline edits in list views that mix record types. Page-based quick actions (Beta) let you design a Quick Action Page once in Lightning App Builder and reuse it across actions of type Lightning Page. Manage Org Responsibilities (Beta) asks you to name a Security Contact and a Primary Admin Contact so Salesforce knows who receives security notices.
Agentforce is on: what admins now own
The release note "Agentforce Platform Enabled by Default" says the platform is enabled for every org with Agentforce access. Existing orgs were enabled on a rolling basis from the first week of September 2026, and removing the Agentforce setting from Setup is planned for later in Winter '27. There is no extra cost and no billing change. Admins get Agentforce Studio and Agentforce Builder once Einstein generative AI is on. Other users need the Manage AI Agents permission, and an agent reaches end users only after someone activates it.
The only off switch the note names is the Einstein setting on the Einstein Setup page. Write down who may activate agents before someone asks.
Three smaller Agentforce changes need an admin's hand. Every Agentforce data library now requires a description before you can save it. The Agentforce assistant in Builder is renamed Agent Optimizer (Beta). Agentforce Observability recalculated Success Rate and changed metric names, so recheck any agent dashboard you share with leadership.
Sales admins have one dated item. Automated field updates for Agentforce Pipeline Management auto-enable from November 14 through November 16, 2026, in orgs with the Agentforce for Sales licence and at least 10 call transcripts. The agent suggests Next Step and Stage updates on opportunities from voice and video calls. Tell your sales managers before their reps see it.
Security and identity dates to calendar
- Refresh token idle limit of 30 days. Idle refresh tokens expire and their access tokens are revoked. Enforcement rolled through sandboxes from October 21 and production from November 4, 2026. Integrations that run quarterly are the ones that break.
- OAuth device flow restricted to local External Client Apps on November 30, 2026. Connected apps using that flow need to move to an External Client App.
- MFA extension release updates appear from November 2026 for orgs that received extensions on MFA for all users, previously exempt users, phishing-resistant MFA for privileged users, or step-up authentication on report exports. Your org's dates show on each release update.
- Migrate to an Easier Way to Require Single Sign-On migrates sandboxes from January 7, 2027 and production from February 4, 2027.
- OAuth user-agent and hybrid user-agent flows retire on February 20, 2027, alongside the username-password flow.
- Security Health Check gained four new signals, including a high-risk check for requiring MFA on all direct UI logins. Run Health Check after the upgrade and compare your score.
Service, sales and suite settings worth a look
Service admins get a consolidated Case Merge setup page with Enhanced Case Merge (Beta), which can use duplicate and matching rules. Knowledge adds reusable Knowledge Blocks, article cloning and duplicate detection. Omni-Channel gets a Queue Access Summary page, and conversations routed to AI agents now skip the pending service routing step and open immediately. New orgs default to Enhanced Chat v2.
Sales admins should note that Salesforce for Outlook now retires on January 30, 2027, after its date moved twice. Suites admins get a redesigned List Sends that emails Contact and Lead lists without a Data 360 segment. Commerce admins on Starter, Pro Suite or Freemium need to check one thing after the upgrade: B2B Commerce users without the Commerce Admin permission set lose access to store pages.
What this release means for admins
Winter '27 rewards admins who read the Release Updates node instead of a blog's list. The changes that bite are permission changes with quiet failure modes: profile names that quietly disappear, SOAP logins that fail on December 1, and refresh tokens that expire after a month of silence. The Flow Builder work is the good news. Edit History, Flow Test Mode and flow tags cover work that admins have been doing by hand for years.
Run the sandbox checklist below in order. For the developer side of the same release, see Winter '27 for Developers. For integration and identity planning, see the Architect article. The Top 10 covers the ten changes that matter regardless of role, and Consultants covers how to explain all of this to a client.