We are so excited to partner with the best in the CRM business because their releases help you, too! The Summer '25 release for Salesforce is currently rolling out, and below are some of the key enhancements we want to highlight as your Salesforce partner.
The Release Date for Summer '25 will depend on the instance of Salesforce, but the main release weekends are on:
-
May 10, 2025
-
May 17, 2025
-
June 7, 2025
-
June 14, 2025
If you already know the instance your production Org is located on, you can head over to Trust Status, click on your instance name, and hit “Maintenance”. This will show you the date of the Salesforce Summer '25 release hitting your Org. If you don’t know your instance, go to Setup > Company Information.
Flow - Send Email Action Updates
Supported Browsers and Devices
General Enhancements
Add the New Setup Domain
Ensure that Setup pages in Lightning Experience load content correctly when browsers block third-party cookies. If your users have general access to the internet, no action is required. If your company controls users’ or servers’ access to the internet through firewalls or allowlists, your IT department must add *.salesforce-setup.com to the company’s list of allowed domains. Salesforce Setup pages are now hosted on that domain.
When: Salesforce is using a staggered rollout to move the Setup pages to the *.salesforce-setup.com domain. The rollout began in Spring ’24 and continued through Spring ’25. As of Summer ’25, the change is enabled in all sandboxes and nonproduction orgs. The rollout is paused in Summer ’25 and resumes for production orgs in Winter ’26 according to the major release upgrade date for your instance.
Find the full list of updates here - General Enhancements
Lightning Console
Give Salesforce Platform License Users Access to the Lightning Console App
With access to the Lightning Console app, Salesforce Platform and Salesforce Platform Login license users can view multiple records and their related records on the same screen.
How: Enable the Lightning Console User permission on the Salesforce Platform or Salesforce Platform Login license user’s profile.
Benefit from Better Lightning Console Performance with Deferred Inactive Workspace Page Loading
Lightning Console now defers the loading of inactive workspace pages by default, which minimizes extra page loads and improves performance. An inactive workspace page doesn’t load until the user navigates to that page. Regardless of whether the “Defer loading inactive console workspace pages” setting is enabled or disabled, content in pinned regions is always considered active and loads immediately. Previously, if a workspace page opened via a navigation rule, then the page immediately began loading even if the user remained on a different workspace page.
How: This setting is on by default. To turn off this setting, from Setup, in the Quick Find box, enter Console Settings, and select Console Workspace Page Loading Preference. Then turn off Defer loading inactive console workspace pages.
List Views
Simplify Quick Filters for the Record Type Field
When you set up a related-list quick filter for the Record Type field, you now select the Value options from a multi-select picklist of available record types. Previously, you typed the Value options into a free-form text field, which sometimes returned incorrect filtering results.
Enhance Accessibility with the Improved List Views Dropdown Menu
To improve accessibility and provide a more consistent user experience, the list views dropdown menu for all objects now uses Lightning Web Components (LWC). Overall, how your users work in list views hasn’t changed, but the updated dropdown menu has some differences. Previously, the updated list views dropdown menu was available only for list views rendered with LWC and not for list views rendered with Aura.
How: The updated list views dropdown menu displays up to 100 lists. It also shows Recent List Views and the option to search your lists at the top of the dropdown. If you have more than 100 list views, use search terms to find a specific list. The keyboard focus for the list views dropdown menu starts with the focus on the top of the list rather than on the currently pinned list.
The updated list views dropdown menu uses a different Document Object Model (DOM) than the previous dropdown menu. The update to the menu’s markup can affect custom functionality that relies on the list view dropdown menu’s DOM structure, as well as the configuration of some built-in features, such as walkthroughs. To make sure that your list views continue to work as expected, review and test the updated dropdown menu.
Find the full list of updates here - List Views
Fields
Easily Remove Relationships Before Deleting a Custom Object
When you attempt to delete a custom object, if another standard object, custom object, or a Data Cloud data model object (DMO) contains a lookup field that references that custom object, you’ll now see a more detailed page. This page includes a table that lists the objects that have relationships, and now shows you the object API name and the field API name. The object API name is hyperlinked, so you can go directly to the object and remove the relationship. If the object that contains the relationship field is a Data Cloud DMO, you can follow the provided help link to complete the process of removing the relationship.
Find the full list of updates here - Fields
Permissions
Update Object Permissions for All Custom Permission Sets or Profiles in One Step
Save time and clicks by editing object access simultaneously in all custom permission sets and profiles. There’s no need to go to individual permission sets or profile pages. In Object Manager, go to a specific object’s access summary to review, add, or remove object permissions. Salesforce delivered this feature thanks to your ideas on IdeaExchange.
How: In Setup, go to Object Manager, and then select an object. In the sidebar, click Object Access. In the Permission Sets or Profiles tabs, click Edit, make your changes, and then save your work.
Edit Permissions Faster in the Permission Set Summary
Instead of going to many Setup pages, you can now update the user, object, field, and custom permissions in a permission set directly from the summary view. Previously, you were able to make only minimal permissions edits in the summary. Salesforce delivered this feature thanks to your ideas on IdeaExchange.
How: In Setup, select a permission set, click View Summary, and then update the permissions in the various tabs.
Review Tab Settings in Access Summaries
Easily see the tabs that a user can access or the tabs included in a permission set or permission set group. Using the summary views is faster than searching through multiple Setup pages, which was previously required to get this information. Salesforce delivered this feature thanks to your ideas on IdeaExchange.
How: In Setup, select a user, permission set, or permission set group, and then click View Summary.
Find the full list of updates here - Permissions
Reports and Dashboards
Choose Which Dashboard Widgets to Refresh
Refresh only the dashboard widgets that you need rather than the entire dashboard. For example, a support team member can refresh only the Open Tickets widget to see the most up-to-date list of unresolved issues, without refreshing other widgets on the dashboard.
When: This functionality is available on a rolling basis starting in Summer ’25.
How: In the dashboard, click the widget’s refresh icon to view its latest data.
Designate One Email Address to Send Report Subscription Notifications
Create consistent email communications and reduce the risk of spoofing by using an organization-wide email address to send report subscriptions from. Previously, emails were sent with the address of the user who created the report subscription.
How: From Setup, in the Quick Find box, enter Reports, and then select Reports and Dashboards Settings. Select Enable Org-Wide Email Address for Report Subscription, and then select the organization-wide email address to use from the dropdown list. You can set up the organization-wide email address in the Organization-Wide Addresses page in Setup.
Find the full list of updates here - Reports and Dashboards
Sharing
Review Changing Sharing Recalculation Behavior
To improve performance for large-scale transactions, Salesforce is changing how some sharing recalculations work behind the scenes. When group membership or role updates occur, related sharing rules are automatically recalculated. Previously, both of these operations always ran synchronously. Now, after group membership or role updates occur, related owner-based sharing rules can be recalculated asynchronously when that approach results in better performance. You can monitor these stages in the Setup Audit Trail.
When: This change is available on a rolling basis starting in Summer ’25.
How: No action is required to enable this behavior.
Find the full list of updates here - Sharing
Flow Testing and Debugging
Debug Flows at a Glance with the Element-Level Summaries
The debugging experience for flows now includes element-level summaries to help you understand more quickly what happened at each point in a flow. For example, for an Update Records element, the Debug Details pane shows at a glance how many elements were updated after the element was executed. Previously, element-level summaries were available only when debugging marketing flows.
Configure the Triggering DMO Record for Event-Triggered Flows
When debugging an event-triggered flow, you can select a specific triggering data model object (DMO) record to debug with, or manually enter values that you want to test.
How: In the Debug Flow window, in the Specify Debug Record section, you can select to use an existing record or to manually enter record field values.
Find the full list of updates here - Flow Testing & Debugging
Flow - Send Email Action Updates
Find Send Email Action Inputs Easier with Organized Inputs
Now you can configure your Send Email action with clearly organized input sections for recipients, senders, and email content. Inputs grouped into distinct categories makes it easier to manage and customize your emails. It’s also easier to configure inputs with the include or exclude toggles now removed.
How: In Flow Builder, in the element menu, search for and select Send Email. The input parameters are grouped into three categories: Configure Recipient Details, Configure Sender Details, and Configure Email Content. Enter the necessary information in the respective fields to set up your email.
Manage Email Configuration by Switching Send Email Action Versions
To control the visibility and organization of email content configuration parameters, you can switch between Send Email Action versions. By selecting the latest action version, you can compose the email body directly or use a predefined email template, enhancing your email workflow's flexibility and efficiency.
How: Open or create a flow in Flow Builder. In the element menu, search for and select Send Email. To change the action version, select the required version from the Action Version dropdown.
For existing flows, the default version is 1.0.0. In this version, the Compose Email Content and Use Email Template options under Configure Email Content aren’t available. Add values to the input parameters according to your requirements. To access the Compose Email Content and Use Email Template options, change the version to 1.0.1 from the Active Version dropdown.
For new flows, the default version is 1.0.1. Choose Compose Email Content or Use Email Template options under Configure Email Content. If required, you can revert to version 1.0.0 from the Active Version dropdown. To prevent errors related to the Compose Email Content or Use Email Template options, delete the value or restore the parameter.
Compose Your Email Content or Select Templates Within the Send Email Action
Write and format your email content directly within the Send Email action, eliminating the need to create a separate text template resource. The body text can include merge fields and be formatted to match your company’s brand. Alternatively, you can now select existing email templates by name instead of bringing the ID of the email template into the flow.
How: Open or create a flow in Flow Builder. In the element menu, search for and select Send Email. To write your email content, go to Configure Email Content. By default, the Compose Email Content option is selected.
To enter the email content directly, from the Body dropdown, select Enter Text. Format your content by using the rich-text toolbar, which includes options like Bold and Italic. You can also insert upstream resources into the flow as merge fields. To view the text in rich or plain format in the Body, from the dropdown, select View as Rich Text or View as Plain Text. To display the email in rich text format, set Rich-Text-Formatted Body to True. If this option is not set to True, the email is displayed in plain text.
To use an existing email template, go to Configure Email Content and select Use Email Template. The input fields Subject, Body, Rich-Text-Formatted Body, and Use Line Breaks are hidden. Enter the template ID or search for your email template.
Configure Sender and Content Inputs Easier in the Send Email Action
With the Send Email action, Flow Builder makes it easier to directly choose a sender type, enter a sender email address, select an email template, attach files, and choose a specific record. A more streamlined email configuration process reduces the need for searching, creating a text template resource, or using extra elements.
How: Open or create a flow in Flow Builder. In the element menu, search for and select Send Email. To configure the sender, select the desired Sender Type from the dropdown list, and then enter the sender’s email address in the provided field.
To use an email template, select the Email Template option under Email Template ID, and then select the template that you created from the list.
To attach files to your email, select the File option under Attachment ID. Search for and select the file that you uploaded. You can attach multiple files by selecting them one by one.
To select a non-recipient record, select the Record option under Related Record ID. Search for the desired object and choose a specific record.
Attach Files to Emails in Flow Builder Without Extra Processing
Attaching files to emails in Flow Builder is easier now that you can provide a text collection variable in the Attachment ID Collection field in the Send Email action. Converting text collection variables to single-value text variables is no longer necessary.
How: To send an email with attachments, open the flow in Flow Builder. In the Add Element menu, find and select Send Email. Under Configure Email Content, in the Attachment ID Collection field, select a text collection variable that holds the list of attachment IDs.
Find the full list of updates here - Flow Email Action updates
Supported Browsers and Devices
Consider these browser restrictions when working with Lightning Experience.
-
Salesforce doesn’t support non-browser applications that embed WebView or similar controls to render content for Lightning Experience. Examples of approaches that embed this type of control include Salesforce Mobile SDK, Microsoft’s WebBrowser Control, Electron’s embedded Chromium browser, iOS’s UIWebView and WKWebView, and Android’s WebView.
-
Lightning Experience doesn’t support incognito or other private browsing modes.
See the supported browsers and devices for Lightning Experience
Desktop and Laptop Browsers
|
MICROSOFT EDGE (NON-CHROMIUM) |
|
|
|
|
|
---|---|---|---|---|---|---|
Lightning Experience |
Not supported |
Not supported |
Supports latest stable browser version. Internet Explorer mode for Microsoft Edge Chromium isn’t supported. |
Supports latest stable browser version |
Supports latest stable browser version |
Supports latest stable browser version |
Experience Builder sites |
Not supported |
Not supported |
Supports latest stable browser version. Internet Explorer mode for Microsoft Edge Chromium isn’t supported. |
Supports latest stable browser version |
Supports latest stable browser version |
Supports latest stable browser version |
Special setup considerations? |
Not supported |
Not supported |
No |
No |
No |
No |
Limitations? |
No |
Tablet Browsers
Use Apple Safari on iPadOS (iOS 13.x or later). Lightning Experience on iPad Safari doesn’t support portrait orientation and orientation switching. Use landscape orientation, and maximize your Safari browser to full width. To prevent the tablet from switching orientation, turn on the iPad rotation lock.
APPLE® SAFARI® |
GOOGLE CHROME™ |
OTHER BROWSERS |
SALESFORCE MOBILE APP |
|
---|---|---|---|---|
iPadOS |
Supported |
Not supported |
Not supported |
Supported |
Android |
— |
Not supported |
Not supported |
Supported |
Salesforce treats touch-enabled laptops, including Microsoft Surface and Surface Pro devices, as laptops instead of tablets. Users can’t access the Salesforce mobile app on these devices. Users are redirected to the full site experience that’s enabled for them—Lightning Experience or Salesforce Classic. Only standard keyboard and mouse inputs are supported on these types of devices.
Phones
For the best experience, use the Salesforce mobile app.
Third-Party Browser Extensions and JavaScript Libraries
Before using a third-party browser extension or JavaScript library, Salesforce recommends that users check AppExchange for browser extensions and apps from Salesforce partners or the Component Reference for base components that match requirements.
Although some third-party browser extensions can personalize and enhance the Salesforce experience, it is not recommended to use browser extensions that manipulate the DOM. Using third-party browser extensions is at the user’s risk. Salesforce can’t prevent these extensions from accessing users’ Salesforce data, nor can it detect that there’s any attempt to access data. Additionally:
-
Browser extensions that insert or remove elements in the DOM can interfere with the stability of Lightning Experience and lead to unexpected behavior.
-
Browser extensions that don’t follow Salesforce security standards can fail to work properly in Lightning Experience.
-
The internal DOM structure of Lightning Experience can change in a future release, and compatibility with a third-party browser extension isn’t guaranteed.
To use a third-party JavaScript library with custom Lightning components, upload it first as a static resource. Use the JavaScript library by loading it in the component, depending on which model you’re using.
-
Lightning Web Components: Load a third-party JavaScript library via
lightning/platformResourceLoader
-
Aura Components: Load a third-party JavaScript library via
ltng/require