It’s that time again - Summer has bloomed for our northern hemisphere neighbours, and so have the latest Salesforce updates! We’ve dug through the Summer ‘26 release notes and handpicked the most exciting features for business users and admins.
Check out our latest blog, where we break down the highlights and what they mean for you! Keep reading below for the Enforced Updates.
The following items may impact some clients. For those who are impacted, please check the date by which they will need to be reviewed and rectified. Enrite recommends creating a sandbox to enable the relevant changes and performing the necessary regression tests
What’s Changing?
Salesforce now requires verification of email-sending domains used within Salesforce. Emails sent from unverified domains may no longer be delivered, even if the email address itself has already been verified.
What Does This Mean?
This change may affect automated emails, notifications, workflows, and organisation-wide email addresses that are sent from your company domain. Without proper domain verification, Salesforce could block outbound emails from those domains.
Recommended Actions:
➡️ For technical details, see this link.
What's Changing?
Salesforce is enforcing MFA for all employee logins across production and sandbox orgs, including direct logins and Single Sign-On (SSO).
What Does This Mean?
Employees who do not already use MFA may be prompted to register a supported verification method when logging in. Organisations using SSO should also confirm that MFA signals are correctly passed to Salesforce.
Recommended Actions:
➡️ For technical details, see this link.
Who is affected?
This applies to users with elevated access, including:
What's changing?
Standard authenticator apps (such as Salesforce Authenticator and similar MFA apps) will no longer be sufficient for affected users.
Affected users must use a phishing-resistant login method, such as:
These provide stronger protection against phishing and account compromise.
Enforcement dates:
What you need to do:
We strongly recommend reviewing this now to avoid login disruption.
Key actions:
➡️ For technical details, see this link.
These updates are worth being aware of as they may relate to your current Salesforce setup or connected applications.
What's Changing?
Chatter will be turned off by default in Salesforce orgs created from Summer ’26 onward. Existing orgs are not affected by this change.
What Does This Mean?
This change mainly impacts new Salesforce orgs. If your organisation relies on Chatter functionality (such as Case Feed, Experience Cloud communities, or APIs), you may need to enable it manually in Setup. Existing implementations will continue to work as normal.
Salesforce is also continuing to evolve collaboration tools, with Salesforce Channels and Slack becoming the preferred options for internal collaboration in Lightning Experience.
Recommended Actions:
➡️ For technical details, see this link.
What's Changing?
Salesforce recently enforced new security requirements for all AppExchange applications, including the implementation of PKCE and Refresh Token Rotation (RTR) for Connected Apps.
As part of this change, Payments2Us released version 11.4 on May 11, 2026, which may have required re-authorisation by your Salesforce Administrator.
What Does This Mean?
If you are using Payments2Us, we recommend confirming that the re-authorisation step has been completed and checking for any payment or authorisation-related issues.
Since this is a Salesforce-wide security directive, it is also worth reviewing any other AppExchange applications used within your organisation to ensure any required updates or actions have been completed.
➡️For technical details, see this link.
If you think the Summer '26 release may affect your setup or wish to get ahead, reach out to us as soon as possible. We can review your environment and take action or provide advice to address any issues. To contact us, please raise a ticket in our portal.
Also, consider joining the Release Readiness Trailblazers group for more information, or sign up for the Salesforce Release Readiness Live Webinars to stay updated.
As EOFY approaches, now is a great time to review your Salesforce environment and make the most of any remaining budget. This can also help avoid unused funds impacting next year’s allocation. It’s a great opportunity to consider pre-purchasing Customer Success hours, which can be used for enhancement projects, support, or even a Salesforce Health Check.
Use these hours to identify areas for improvement and highlight any urgent issues before they become bigger challenges. It’s also a practical way to plan ahead for upcoming projects, enhancements, or support needs while making the most of your available Client Success hours.
As many teams begin planning new initiatives for the new financial year, our project capacity can fill up quickly. Securing your hours early helps ensure your team has the support you need when priorities ramp up.
Salesforce Summer ’26 Release Date & HighlightsThe Salesforce Summer ‘26 release is here, and it's a significant one! There is a strong focus on AI-powered automation, enhanced service capabilities, deeper Slack integration, and platform security improvements, all aimed at improving how organisations build, manage, and secure their Salesforce environments. Depending on your instance, you'll be upgraded on one of the following […]
What to Look for in a CRM for Nonprofits?What Can a CRM Do for Your Nonprofit? We’ve worked with hundreds of nonprofits, and while every organisation is different, they often face similar struggles. These include keeping track of donors and stakeholders, administering programs, managing different communication channels, or organising events and fundraising. Most of these challenges come down to one thing: bringing all […]
Beyond the Salesforce Health Check: 5 Steps to Full System MaturityWhen most organisations begin their journey toward system optimisation, they start with the Salesforce Health Check. It is the industry-standard starting point, and for good reason. But a "healthy" org isn’t just one that is secure; it’s one that is purpose-built to scale. True System Maturity is the transition from a passive database to an […]
