What the Recent Salesforce Security Update Means for your Nonprofit
Salesforce has introduced new security requirements for certain AppExchange applications that connect to Salesforce using Connected Apps or External Client Apps.
While the update is primarily aimed at software vendors, nonprofits should also understand how these changes may affect the applications connected to their Salesforce environment.
Many nonprofits rely on Salesforce-connected apps for payments, fundraising, donor management, integrations, and supporter engagement. These new requirements are designed to strengthen security and better protect sensitive data.
What has Salesforce announced?
Salesforce introduced four mandatory security controls for AppExchange partner applications that use Connected Apps or External Client Apps across multiple customer environments.
These include:
PKCE (Proof Key for Code Exchange)
Refresh Token Rotation
Idle Refresh Token Time-to-Live (TTL) limits
Refresh Token IP Allow Lists
Salesforce advised that partners must implement these controls by May 11, 2026, or risk AppExchange delisting or suspension of application interoperability with Salesforce services.
While these requirements are technical in nature, the goal is straightforward: improving protection for customer accounts and sensitive data.
Why does this matter for nonprofits?
This update is not just something for software vendors to manage in the background. It is something nonprofits should be aware of too.
If an app connected to Salesforce does not meet the new security requirements by Salesforce’s deadline, it may stop working properly with Salesforce. This is particularly important for organisations using older or legacy apps that may no longer be actively maintained by their vendors.
For nonprofits, even a short disruption can create real challenges. Donations may not process, supporter data may not sync correctly, staff may need manual workarounds, and reporting could be affected.
What nonprofits should do next
While Salesforce has directed these updates to software vendors, nonprofits should still take proactive steps to protect their Salesforce environment and reduce the risk of disruption.
Speak with your Salesforce admin or partner
If they are not already aware of these upcoming changes, make sure your internal Salesforce administrator or external Salesforce partner knows about the new Salesforce security requirements.
Review connected apps in your Salesforce environment
Your Salesforce administrator or Salesforce partner should review the Connected Apps and External Client Apps in your Salesforce environment.
They can help identify which applications are actively used, which vendors manage them, and whether any may be affected by Salesforce’s new security requirements.
Confirm vendors are actively maintaining their applications
Do not assume that every AppExchange product is automatically keeping pace with Salesforce platform changes.
Ask your vendors:
Have you implemented Salesforce’s new mandatory security requirements?
Is your application actively maintained and regularly updated?
How do you monitor and respond to Salesforce platform changes?
Do you have a dedicated Salesforce development team?
Have you tested your application against Salesforce’s new requirements?
Where Payments2Us stands
Payments2Us has already implemented Salesforce’s new security requirements and is fully aligned with the upcoming changes.
As a Salesforce-native solution, Payments2Us actively monitors Salesforce platform updates, release changes, and security advisories to ensure ongoing compatibility and reliability for our customers.
Our customers are not at risk of disruption related to these security changes.
Final thoughts
This update is a timely reminder that Salesforce environments require ongoing review and maintenance, not just initial setup.
For nonprofits, now is a good opportunity to review connected applications, confirm vendor readiness, and ensure critical systems will continue operating smoothly as Salesforce’s security standards evolve.
.png)