.webp)
.gif)
Salesforce ships three major releases every year. Across Winter '25, Spring '25, Summer '25, and Winter '26 through Spring '26, the platform has delivered a consistent set of improvements to permissions management, Flow builder, list views, and record page configuration. Not every release note makes it into daily practice — so this article pulls out the features that actually change how administrators, RevOps teams, and CRM architects work inside the platform.
The 2025 release cycle — covering Winter '25, Spring '25, and Summer '25 — delivered meaningful upgrades across three core areas: understanding who has access to what, building more capable flows, and working more efficiently inside list views and record pages.
Winter '25 introduced Object Access, which gives administrators the ability to see every permission set, permission set group, and profile that grants access to a given object from a single view. Before this, tracing why a user could see a particular object required manually checking multiple permission sets and profiles — a process that was time-consuming and easy to get wrong. Object Access makes that investigation straightforward.
The User Access Summary Page sits alongside this and provides a consolidated view of a specific user's permissions — user permissions, object permissions, and field permissions — in one place. The "Access Granted By" button within this page shows exactly what is granting a particular permission, which eliminates a significant amount of detective work during audits or troubleshooting sessions.
The Enhanced User List View brought search, filtering, and inline editing to user management — three capabilities that had been missing from what is one of the most frequently used pages in Salesforce Setup. For any admin managing a growing user base, this alone materially reduces the time spent on routine user configuration tasks.
On the Flow side, Winter '25 delivered several updates that expand what a screen flow can do without requiring a developer. The Action Button component allows a flow screen to trigger a second flow and display output from that flow on the same screen, without switching screens. The Choice Lookup field gained the ability to accept multiple selections, removing a limitation that had previously required workarounds. Upsert operations in Flow gained the ability to match records based on a field within a flow variable, rather than requiring manual mapping. Together these changes make screen flows a more capable replacement for custom Lightning components in many common use cases.
The Dynamic Highlights Panel was extended to support up to 12 fields, with filter criteria to control which fields display on a given record page. Account Plans also arrived in Winter '25, providing a native space to document opportunity context, run a SWOT analysis, set objectives and metrics, and visualize relationship maps — useful for any team managing a structured account strategy inside Salesforce.
Spring '25 added the ability to sort list views by multiple columns simultaneously — a straightforward improvement that makes list views considerably more useful for anyone working with large data sets. The same multi-column sort is available for related lists on record pages.
Permission set management received two practical updates. Administrators can now add or remove permission sets to a permission set group from a single location. They can also remove user permissions and custom permissions directly from within a permission set's summary view, rather than navigating into the permission set itself. These changes reduce the number of clicks required for routine permission management without changing how the underlying permission model works.
A new object permission — View All Fields — was also introduced, giving administrators a cleaner way to grant read access to all fields on an object without needing to configure individual field permissions.
The Progress Indicator screen flow component gave flow builders a native way to show users where they are in a multi-step flow — previously this required a custom component or a workaround.
Summer '25 concentrated improvements across user management, the Flow builder interface, and several permissions workflows that had previously required navigating between multiple screens.
Public group and queue membership can now be managed from one place, alongside permission set and permission set group assignments. Adjusting object access across multiple permission sets from a single view — rather than opening each permission set individually — was another long-overdue consolidation. Field, user, object, and custom permissions can now be edited directly from the permission set summary view. These changes collectively reduce the administrative overhead of permission management in any org with more than a handful of permission sets.
The Flow builder gained several interface improvements: individual component widths can be configured on a flow screen, the canvas supports pinch-to-zoom via trackpad, flow screens can be previewed in different sizes based on user device, and a new Time data type allows flows to work with a specific time value independent of a full date-time field.
The Visual Picker flow screen component allows administrators to display an icon within a button and configure button size — improving the visual design options available within screen flows without requiring a custom component.
Two infrastructure improvements are worth noting for any team managing a complex Salesforce org. First, when deleting a custom object, Salesforce now displays a page showing all dependencies — related objects, fields, and references — that must be resolved before the deletion can complete. This prevents the previously common experience of discovering broken dependencies after the fact. Second, a new setting allows organizations to configure an org-wide email address specifically for report and dashboard subscription emails, replacing the previous default behavior of using the individual user's email address as the sender.
The 2026 release cycle so far — Winter '26 and Spring '26 — has continued the theme of consolidating administrative workflows and extending Flow builder capabilities. Spring '26 also introduced meaningful updates to Pipeline Inspection, scheduled flow automation, and dashboard extensibility.
Field history tracking configuration can now be managed for all objects from a single location. Previously, this required navigating into each object individually within Setup — a significant inconvenience in any org tracking history across multiple objects. Centralizing this configuration makes it easier to audit and maintain a consistent tracking policy.
The Flow debug experience has been extended to screen flows, giving administrators the ability to step through a screen flow in debug mode in the same way that was previously available for other flow types. This simplifies the process of identifying where a screen flow is failing without needing to reproduce the issue in a live environment. In Spring '26, input variables in the flow debugger now persist between runs and edits — so if you are iteratively testing a flow, you no longer need to re-enter test values each time.
The Send Email flow component gained the ability to combine email address collections and individual addresses in the same recipient field. This removes a constraint that had previously required separate logic to handle mixed recipient lists.
A small but useful list view improvement arrived in Winter '26: when configuring list view columns, typing a letter on your keyboard jumps to fields beginning with that letter — a minor change that meaningfully speeds up column configuration in objects with a large number of fields.
License management became more efficient with automatic removal of related permission set license assignments when a permission set or permission set group is unassigned from a user. Previously, this required a manual step. It is worth noting the exceptions: automatic unassignment does not occur when updates are made via user access policies, when the user holds the license through another permission set, when removing a licensed permission set from a permission set group, or when unassigning 50 or more permission sets or permission set groups at once.
Spring '26 introduced updates across four areas that are directly relevant to B2B revenue teams: Pipeline Inspection visibility, scheduled flow performance, screen flow development, and dashboard extensibility.
Pipeline Inspection gained two new columns that surface engagement data without requiring sales reps to open individual opportunity records. The Activity Heatmap column displays a visual indicator of both inbound and outbound interactions — calls, events, and emails — over a rolling 30-day period. Sales managers and reps can see at a glance whether a deal has had recent activity or gone quiet, without manually scrolling through each opportunity's activity timeline. The Contacts column sits alongside this and shows a count of individual stakeholders actively involved in activities over the same 30-day window. Deals that are progressing through a single point of contact — rather than multiple stakeholders — become immediately visible. Both columns address a common failure mode in pipeline reviews: deals that look healthy on stage and amount but have no recent engagement and no multi-threaded coverage.
Admins can now specify a custom batch size — from 1 to 200 records — directly within a scheduled flow's start element. Previously, Salesforce applied a fixed default of 200. For complex automations processing records with many related lookups, calculations, or callouts, processing 200 records in a single batch frequently exhausted governor limits and caused flow failures. Custom batch sizing allows admins to tune performance based on the actual complexity of the automation, trading throughput for reliability where needed.
Available on Foundations and Agentforce 1 edition licenses, the natural language prompt capability in the Agentforce panel allows admins to modify existing screen flows using plain English instructions. The AI can add, remove, or adjust screen elements and actions based on a text description, without the admin manually configuring each change in the Flow builder. This is currently in beta and requires one of the qualifying license types, but it points toward a meaningful reduction in the configuration overhead for iterative flow development.
The ability to embed custom Lightning Web Components (LWCs) directly into Lightning dashboards moved from beta to general availability in Spring '26. Developers can now build complex, interactive visualizations — including chart types not available in standard Salesforce widgets, such as waterfall charts — and embed them within dashboards alongside standard components. Users can filter, explore, and trigger actions from within the dashboard without navigating to a separate page. For RevOps and analytics teams that have hit the ceiling of what standard dashboard widgets can display, this removes the need for a third-party tool to handle advanced visualization requirements.
Spring '26 also introduced the ability to trigger record-triggered flows when files are created or changed, using ContentDocument and ContentVersion as trigger objects. This opens up automation scenarios around document management — such as triggering a notification, updating a record, or initiating a process when a specific file type is attached to a record — that previously required custom Apex code.
The Message flow screen component provides a native way to display styled message blocks within a screen flow. It is distinct from a toast message — which is a temporary notification that appears at the top of the screen — and is better suited to inline informational content within a flow screen itself.
Custom disclaimers can now be configured for exported reports, giving administrators control over what additional text appears when users export report data. For organizations with compliance requirements around data exports, this provides a native solution without requiring a managed package or custom development.
The pattern across the 2025 and 2026 releases is consistent: Salesforce is consolidating administrative workflows that previously required navigating between multiple areas of Setup, extending Flow builder to handle more use cases natively without custom code, and surfacing pipeline engagement data directly in the tools sales teams already use. For B2B revenue teams, all three directions have a practical implication.
Consolidated permissions management means that RevOps administrators and CRM architects can audit, adjust, and document user access more efficiently — which directly supports the kind of quarterly license reviews that keep CRM spend in check. The improvements to object access visibility, user access summaries, and permission set management are particularly relevant for any organization running a structured license optimization process.
Extended Flow capability means that more automation and user experience work can be done by administrators rather than developers, which reduces the cost and lead time of CRM improvements. Screen flow enhancements in particular — the Action Button, Visual Picker, Progress Indicator, Message component, natural language prompts, and the ability to trigger flows on file changes — expand the range of internal tools and guided processes that can be built directly on the Salesforce platform. Custom batch sizing for scheduled flows removes a reliability constraint that has blocked adoption of Flow-based automation for complex data operations.
Pipeline Inspection improvements address a different category of problem: deal visibility for frontline sales and their managers. The Activity Heatmap and Contact Insights columns close a gap that previously required manual activity review — making pipeline inspection faster and more likely to catch at-risk deals before they slip.
Object Access is an administrative tool that shows every permission set, permission set group, and profile granting access to a specific Salesforce object from a single view. Before this feature, determining why a user could access a given object required checking each permission set and profile individually. Object Access consolidates that investigation into one screen, making permissions audits and troubleshooting significantly faster for Salesforce administrators.
The User Access Summary Page is a consolidated view of a specific user's permissions in Salesforce, covering user permissions, object permissions, and field permissions in a single location. The "Access Granted By" button within the page identifies the specific permission set, profile, or permission set group that is granting each individual permission. It was introduced in Winter '25 and is particularly useful during user access audits and license reviews.
Across the 2025 and 2026 releases, Salesforce extended Flow builder in several directions. Screen flows gained the Action Button component (Winter '25), multi-select from Choice Lookup (Winter '25), the Progress Indicator component (Spring '25), configurable component widths and device-based preview (Summer '25), the Visual Picker component (Summer '25), the Message component (Spring '26), and persistent debug variables (Spring '26). Record-triggered flows can now fire on ContentDocument and ContentVersion objects, enabling file-based automation (Spring '26). The debug experience was extended to screen flows in Winter '26. Natural language prompts for modifying screen flows are available in beta on qualifying licenses (Spring '26).
Account Plans is a native Salesforce feature introduced in Winter '25 that provides a structured space within an account record to document opportunity context, conduct a SWOT analysis, set objectives and metrics, and visualize relationship maps. It is designed for teams managing a formal account planning process and provides a built-in alternative to managing this information in external documents or custom-built Lightning components.
The 2025 and 2026 releases delivered a series of incremental improvements to how permissions are managed in Salesforce Setup. Key changes include: adding or removing permission sets within a permission set group from one place (Spring '25), editing permissions directly from the permission set summary view (Summer '25), adjusting object access across multiple permission sets from a single view (Summer '25), managing public group and queue membership alongside permission set assignments from one place (Summer '25), centralizing field history tracking configuration for all objects (Winter '26), and automatic removal of related permission set license assignments when a permission set is unassigned from a user (Winter '26).
In Summer '25, Salesforce introduced a dependency review page that displays when an administrator attempts to delete a custom object. The page lists all dependencies — related objects, fields, and references — that must be resolved before the deletion can complete. This prevents broken dependencies from being discovered after the fact and gives administrators a clear checklist of what needs to be cleaned up before removing an object from the org.
The Activity Heatmap is a new column in Pipeline Inspection, introduced in Spring '26, that displays a visual indicator of inbound and outbound interactions — calls, events, and emails — across each opportunity over a rolling 30-day period. It allows sales reps and managers to assess deal engagement at a glance without opening individual opportunity records. Opportunities with no recent activity are immediately visible, reducing the risk of deals going cold without being flagged in a pipeline review.
Custom batch sizes, introduced in Spring '26, allow admins to set the number of records processed per batch in a scheduled flow — from 1 to 200 — directly within the flow's start element. The previous default of 200 caused governor limit errors for complex automations. By reducing the batch size, admins can prevent failures on high-complexity flows at the cost of longer total execution time, giving them direct control over the reliability-versus-throughput trade-off.
Presenting our distinguished clientele! We collaborate closely with visionary B2B tech and software companies, intricately shaping their comprehensive Revenue Architecture. Take a look at who we have already served.
Explore our captivating customer success
stories here.
You have questions? Our Founder and Managing
Partner Michael is looking forward to hearing from
you.
