Summer '26 Lands June 15: The Admin Checklist for Week One

Release weekends for Summer '26 ran May 9, June 5 and June 12 — by June 15 every org has it. Most release-note roundups list two hundred features. Here are the handful that change how you administer the org, plus the five mandatory release updates that will break things if you ignore them.

The headline change: Chatter is off by default

New orgs created on Summer '26 ship with Chatter disabled. Existing orgs keep whatever they have — but the signal is unmistakable: Salesforce sees Slack as the collaboration layer and Chatter as legacy. If your processes still depend on Chatter feeds (approvals, @mention escalations, record-feed audit habits), start the migration conversation this quarter on your terms, not next year on Salesforce's.

Permission changes you'll actually feel

Permission dependency visibility

The quiet winner of this release. When you edit a profile or permission set, Salesforce now shows you the indirect permissions your change drags along — and asks you to approve them before saving. Every admin has a story about granting one permission and silently enabling three others; that failure mode now has a speed bump. Treat the new dependency view as a review gate in your change process.

Per-queue access control

You can now enable or disable hierarchical access per queue instead of one blanket rule for all queues. If you've ever built a workaround so managers couldn't see the compensation-review queue, you can finally delete it. Audit your queues this week — the right setting is now expressible.

Flow gets nicer to build in

• Data Table lookups show record names instead of raw IDs — screen flows immediately look less like database dumps
• Radio Button Group component — a proper visual single-select, no more disguised picklists
• Collapsible fault paths — large canvases stop being spaghetti the moment error handling is added

Small individually, but together they continue the trend we covered when Flow Orchestration went free: Flow is the automation surface Salesforce invests in. If your team still defaults to building new automation outside Flow, the gap keeps widening.

The five release updates you must test

These are enforced, not optional. In order of likely blast radius:

• Multi-configuration SAML migration — the single-config SAML framework is being retired. If your SSO predates 2020, test this in sandbox first; a broken SAML config is an everyone-is-locked-out incident.
• Custom X (Twitter) authentication — the Salesforce-managed auth provider goes away; social sign-on via X needs your own app registration now.
• Apex Batch Action result ordering — results now sort by request order. Code that assumed the old ordering will misattribute results silently. Grep your batch-action handlers.
• Date picker accessibility at 200% zoom and page header/modal accessibility — low risk, but custom CSS overrides on standard components can break visually. Spot-check your most-used pages.

A release update you tested is a Tuesday. A release update you didn't is a war room.

The week-one plan

• Day 1: Run all five release updates in a refreshed sandbox; log what breaks
• Day 2: Audit queues for hierarchical-access settings; document intended state
• Day 3: Walk your top three permission sets through the new dependency view; you will find surprises
• Day 4: Upgrade one high-traffic screen flow with the new Data Table and Radio Group components — visible quality wins build trust in the platform
• Day 5: Write the Chatter position memo: keep, migrate, or sunset — with a date

And if you're staring at this list with no sandbox refreshed and the June security deadlines also bearing down — that's exactly the moment a managed-services partner pays for itself.