Your User Context Flows Aren't Running in User Context | Salesforce Winter 27 Updates Part 1

Flow Builder doesn't look like Flow Builder any more. Winter '27 brings SLDS 2 to Flow Builder as the Salesforce Cosmos theme — the biggest visual change since Flow Builder shipped in 2019. But underneath the repaint there are eleven changes worth knowing about, and the last one isn't cosmetic at all. This is Part 1: everything that changed about how Flow Builder looks and works, demoed live in a Winter '27 pre-release org — including a side-by-side against a second org still on the old release, so you can see the canvas change rather than take my word for it, and the flow XML open in VS Code for the metadata change. ⏱ CHAPTERS 01:34 Key dates for Winter '27 02:41 Find your own release date on Salesforce Trust 04:02 Eleven changes, four acts 05:01 1 · Collapsible sidebar in the Setup menu 06:40 2 · The new canvas — SLDS 2 as the Cosmos theme 07:56 3 · Auto-generated element labels (needs Agentforce) 08:44 4 · Customizable Flow Builder experience — the preferences panel 10:53 5 · Keyboard shortcuts on the canvas 12:56 6 · Easier Decision element navigation 14:13 7 · End elements saved to metadata — the XML in VS Code 16:59 8 · The unused resources filter 18:28 9 · Better flow version comparison 20:10 10 · Flow version edit history 21:38 11 · Enforce user permissions, however it runs 25:36 Recap — eleven changes, one rebuilt builder 📄 OFFICIAL RELEASE NOTES Cosmos theme in Flow Builder — https://help.salesforce.com/s/article... Keyboard shortcuts — https://help.salesforce.com/s/article... End elements saved to metadata — https://help.salesforce.com/s/article... Unused resources filter — https://help.salesforce.com/s/article... Flow version comparison — https://help.salesforce.com/s/article... Flow version edit history — https://help.salesforce.com/s/article... Enforce user permissions — https://help.salesforce.com/s/article... All Winter '27 release notes — https://help.salesforce.com/s/article... 🔗 USEFUL LINKS Salesforce Trust — look up your own instance and release weekend (walkthrough at 02:41) — https://status.salesforce.com Pre-release org signup — https://www.salesforce.com/products/f... ⚠️ TWO THINGS WORTH KNOWING Auto-generated element labels need an Agentforce licence. This org doesn't have one, so that feature is explained at 07:53 but not demoed. If you go looking for it and nothing happens, the licence is why. The new run context option only applies to flows running on API version 68.0 or later. Your org upgrading doesn't retrofit it onto flows you haven't touched. 🔍 THE BIT I'D SKIP TO 21:38 — the run context change. At 23:25 the How to Run the Flow dropdown on an API 68.0 flow shows four options, including "User Context — Enforces User Permissions". At 23:47 the same dropdown on a flow still running API 67 shows three. Which is exactly why the 68.0 requirement matters more than your org's release date. 📌 WHY THIS ORDER Every change in this video is visible in the background of every demo. Covering them first means nothing later in the series gets spoiled by a detail you noticed early. Everything here is from a pre-release org ahead of general availability, so details can still shift before your release weekend. #Salesforce #Winter27 #SalesforceFlow #FlowBuilder #SalesforceAdmin #SalesforceDeveloper #SalesforceArchitect #Trailblazer #SalesforceRelease