Salesforce Summer '26 Release: Top Features for Admins

Summer '26 release notes dropped on April 22, and I'll be honest, this one feels different. After spending a few hours combing through the highlights, I think this release shifts how admins will spend their time day-to-day. Less clicking through profiles. More working with Agentforce. And finally, finally, a real Field Access tab.

If you haven't blocked time on your calendar to prep for the upgrade weekends in June, you'll want to do that soon. Sandboxes upgrade around May 9, and production orgs roll out the weekends of June 5, 12, and 13. That gives you about six weeks to test, retrain users, and update your documentation.

Here's what stood out to me from the Summer '26 release, and what I think you should focus on first.

The New Field Access Tab Is the Audit Tool We've Been Asking For

For years, auditing field-level security has been one of those tasks I tried to avoid. You'd have to bounce between profiles, permission sets, and permission set groups, take screenshots, build a spreadsheet, and pray you didn't miss anything. SOX audit season was a nightmare.

Summer '26 introduces a new Field Access tab at the bottom of every object in Object Manager. Open it, and you get a single consolidated view of every field on that object alongside a matrix showing exactly how access is granted across profiles, permission sets, and permission set groups. No more bouncing around. No more spreadsheets.

I tested it in a preview org last week. Pulled up the Account object, clicked Field Access, and within about ten seconds I had a complete picture of who could see what and why. For onboarding new admins or running compliance reviews, this is going to save hours.

A practical tip: even though the tab is read-only for viewing access, you can use it as a starting point to identify orphaned permissions. If a field has access granted through a permission set that no users are assigned to, you've found dead weight you can clean up.

Flow Gets a Big Round of Quality-of-Life Upgrades

Flow has been getting better every release for years now, but Summer '26 focuses on making flows actually maintainable, which is something the community has been asking about loudly. There are ten new Flow features in this release, and three of them stand out.

First, schedule-triggered flows can now have a configurable maximum batch size. The default has always been 200 records per batch, which works fine until you're processing a flow that hits limits at 150. Now you can override that. Drop it to 50 if you've got heavy logic, or push it higher if you're just doing simple field updates.

Second, error handling on record-triggered flows got smarter. You can finally catch and route errors without building a whole secondary flow to handle failures. This alone is going to save me from rewriting two production flows that I've been meaning to fix for months.

Third, Flow Builder has cleaner UI components and more readable data displays. It sounds like a small thing, but when you're staring at a flow with 40 elements trying to figure out what's happening, every bit of clarity helps. If you're new to Flow vocabulary, I'd recommend bookmarking salesforcedictionary.com as a quick reference for the terms that come up in release notes. It's saved me a few times when I hit jargon I didn't recognize.

Agentforce Stops Being a Sidecar and Starts Being Part of the CRM

Salesforce reports more than 12,000 customers have deployed Agentforce so far. That's a real adoption number, not a marketing fantasy. And Summer '26 is the release where Agentforce stops feeling like a separate product and starts showing up inside the surfaces admins and users already work in.

You'll see Agentforce inside Sales Cloud list views, in marketing authoring tools, and in service console workflows. For admins, this means a few things. You need to think about which agents your users actually have access to (more permission set work). You need to decide which actions agents are allowed to take on records, and you need to set guardrails before someone in sales tells an agent to mass-update opportunities.

I'd suggest doing three things this month. Spin up a sandbox with Agentforce enabled if you haven't already. Identify two or three workflows where agents could realistically help (lead qualification, case summaries, and meeting prep are common starting points). And read up on agent topic modeling, because that's how you control what your agents will and won't do.

If you're new to Agentforce, the terminology around topics, actions, and reasoning engines can be overwhelming. I'd start with the basics on salesforcedictionary.com to build a vocabulary before reading the deeper Trailhead modules. It made the documentation a lot easier to follow.

Web Console: A Browser-Based IDE Built Right Into Your Org

This one is for the developers and admin-developers in your org, but you should know about it because users will start asking questions.

Summer '26 introduces Web Console, a lightweight browser-based IDE built on VS Code for Web foundations. It's designed to replace the legacy Developer Console (which has been showing its age for a decade) and the unofficial Workbench tool that admins and devs have been propping up for SOQL queries and metadata work.

What I like about it: no installation required, available in all org types (including free and developer orgs), and you can write Apex, run SOQL, and customize the org from the same interface. What I'm watching: how it handles deployments and source control compared to the full Agentforce IDE, which is paid-only.

If you've been using Workbench for quick SOQL queries or to inspect API requests, start migrating those habits to Web Console now. The legacy tools aren't going away immediately, but the writing is on the wall.

Reporting Gets Two Row-Level Formulas Per Report

Last one, and it's a small change that's going to make a big difference for me. You can now add up to two row-level formulas in a single report. The previous limit of one formula per report has caused me to create custom formula fields on objects more times than I want to admit, just to get a calculation into a report.

With two formulas, you can do things like calculate the difference between two date fields and compute a percentage in the same report. Quick wins like deal age plus close probability, or invoice age plus collected percentage, are now doable without touching object-level metadata.

It's a quiet feature, but quiet features that reduce admin overhead are exactly what I want from a release.

How to Prep Your Org Before June

Here's the rough plan I'm running this month.

Block time the week of May 9 to log into your preview org and walk through the new Field Access tab on your most critical objects (Account, Contact, Opportunity, Case). Document anything that looks off. Pull a list of your record-triggered and schedule-triggered flows. Identify which ones could benefit from custom batch sizes. Test them in sandbox with the new error handling.

Audit your Agentforce setup. Even if you haven't deployed agents yet, decide on the permission set groups you'll use to govern access when you do. Communicate with your developers about Web Console. If your team has been using Workbench, set a target date to migrate. And update your release readiness documentation. New features mean new screenshots and new training notes for your end users.

If you maintain a glossary or onboarding doc for new admins on your team, this is a good moment to refresh it. I keep a personal cheat sheet of new terminology each release, and the team glossary at salesforcedictionary.com is where I cross-check definitions when I'm building it.

Wrapping Up

Summer '26 isn't a flashy release with one giant headline feature. It's a quietly substantial one that fixes long-standing pain points and integrates Agentforce more deeply into daily workflows. The Field Access tab alone is worth the upgrade for me. The Flow improvements close gaps I've been working around for years. And Agentforce becoming part of the regular CRM surface means admins need to start treating agent access the same way we treat data access.

If you're building a release readiness checklist, those five areas are where I'd start.

What features are you most excited about in Summer '26? Drop a comment with your top three and how you're planning to roll them out. I'm especially curious to hear how teams are governing Agentforce access. There's no playbook yet and we're all figuring it out together.