Summer ’26 Release Series
Salesforce Summer ’26 brings a long list of updates, but most teams don’t have the time, or the need, to digest every line of the release notes. What matters is understanding which changes will affect your platform and which ones can wait.
In this session, Salesforce MVP Keir Bowden joined Ziipline Co-Founder Matt Grimwade to talk through the release from a delivery perspective. This is a hands-on discussion based on real projects, focused on topics that could affect your architecture and plans in the next few months.
What this session covers
Platform changes that need planning
Summer ’26 introduces updates that require review, not just awareness. We cover the MFA enforcement rollout for all employee license users through June and July 2026, phishing-resistant MFA for admins, the Multiple-Configuration SAML Framework enforcement, SOAP API login() restrictions and the new Any API Auth permission, the move to External Client Apps and OAuth, the TLS certificate lifespan reduction to 200 days from March 2026, and Apex becoming secure by default in API 67.0 with database operations running in user mode. These are the areas that need action to avoid disruption.
AI moving into delivery
Agentforce continues to expand across the platform. We highlight Setup with Agentforce going GA, modifying screen flows directly with Agentforce, troubleshooting flows with Agentforce, the Inbound Lead Generation to Lead Nurturing Agent handoff, qualifying Contacts and Person Accounts (previously Leads only), the Find Case Expert action in Service, agentic milestones with proactive risk scoring, and securing AI agent connections through hosted MCP servers. The focus is practical application and governance.
Automation with stronger control
Flow enhancements improve oversight and maintainability. We look at custom batch sizes for scheduled flows, email templates stored as references rather than IDs so they no longer break on deployment, the collapsible fault path, stacked radio button groups in screen flows, and Advanced Approvals moving into Slack with the Approval Trace component on related records.
Clearer reporting and insight
Reporting and analytics updates strengthen visibility. This includes brand color palettes for Lightning reports and dashboards, custom Lightning Web Components in dashboards, two row-level formulas in reports, Data 360 dimensional hierarchies and Calculated Insight Object History, currency reporting in Data 360, semi-join and anti-join support in CRM Analytics, multi-value text filters, and full-width printing for wide charts. The emphasis is measurable impact rather than feature volume.
So what should you actually do?
A release on its own doesn’t change much. What matters is what you choose to do next.
When we look at new Salesforce functionality, we’re thinking about how it fits into the shape of your existing platform. Does it simplify things? Does it introduce risk? Does it solve a problem you actually have? If the answer isn’t clear, it’s probably not a priority.
It is also worth paying attention to what is still in beta. Not because every beta feature will make it to general availability, but because it shows where Salesforce is heading. A specific capability may evolve or even disappear, but the underlying problem space rarely does.
Engaging early creates the opportunity to give feedback and help influence how a feature takes shape. Waiting until GA often means those decisions are already fixed. Having visibility of beta functionality also means you are better prepared when it goes live.
If Summer ’26 has raised questions about where to focus, or how emerging capabilities may shape your roadmap, we’re happy to talk it through.