Salesforce MFA and PRMFA Changes: How Nonprofits Can Prepare

From June 2026, Salesforce plans to introduce stronger authentication requirements to help protect customer environments from unauthorised access, phishing, and credential-based attacks.

For nonprofits, this is more than a login change. Salesforce often holds supporter records, donation history, campaign activity, payment-related records, reports, dashboards, and operational workflows. If your users are not prepared, these changes could create avoidable disruption for fundraising, finance, administration, and leadership teams.

What is changing?

Salesforce is strengthening authentication requirements in two key areas:

  1. Multi-factor authentication (MFA) for all users

  2. Phishing-resistant multi-factor authentication (PRMFA) for admins and privileged users

These changes are designed to reduce the risk of unauthorised access, especially where users have broad access to data, configuration, reports, integrations, or sensitive operational processes.

1. MFA will become mandatory for all users

Beginning June 2026, Salesforce plans to require multi-factor authentication for all employee licence users. For many organisations MFA may already be in place however, this update makes it important to check that every required user is properly covered.

MFA can be enforced directly through Salesforce or through a Single Sign-On provider, such as Okta, OneLogin, Ping, or Google Workspace.. If your organisation uses SSO, this requirement still applies. It simply means MFA needs to be enabled through your identity provider instead of directly in Salesforce.

It is also important to note that one-time passcodes sent by email, SMS, or phone call do not meet Salesforce’s MFA requirement. Users should be set up with an approved method, such as an authenticator app, built-in authenticator, security key, or another supported option.

Salesforce has also confirmed that some sensitive actions may require users to verify their identity again after login. This is known as step-up authentication. For example, a user may already be logged in, but Salesforce may still ask them to reauthenticate when they perform certain actions, such as accessing reports or other sensitive areas.

2. Phishing-resistant MFA will be required for admins and privileged users

Salesforce is also introducing a stronger requirement for users with powerful access. This includes users with the System Administrator profile or permissions such as Modify All Data, View All Data, Customise Application, or Author Apex.

For these users, standard MFA will not be enough. Salesforce is requiring phishing-resistant MFA (PRMFA) as it is much harder for attackers to trick, steal, or intercept. It helps protect against attacks such as fake login pages, stolen passwords, and push notification fatigue.

Salesforce identifies built-in authenticators, such as Touch ID or Windows Hello, and WebAuthn-based security keys as phishing-resistant MFA methods. Physical security keys, such as YubiKey 

Salesforce also refers to these methods as passkeys and recommends passwordless login with passkeys for a faster and more secure login experience.

What you should do now


Start with an access review 

A useful starting point is Salesforce’s own MFA Requirement Checker. This tool can help you understand whether your current setup is likely to meet Salesforce’s MFA requirements and where you may need to take action.

You should also review users with broad system access, users who manage configuration, and users who regularly access sensitive reporting or payment-related data.

This review will help you understand the size of the change, who needs support first, and whether your organisation needs to update its MFA approach before enforcement begins.

Identify privileged users

Start by reviewing who has priviliged access in Salesforce. Navigate to Setup → Profiles → System Administrator → Assigned Users to pull a list of everyone assigned the system admin profile. Beyond that, review any permission sets or permission set groups that grant high-level access particularly those including "Modify All Data" or "Manage Users." Anyone falling into these categories should be prioritised when rolling out phishing-resistant MFA.

Choose the right PRMFA method

Once you've identified your admins and privileged users, determine which phishing-resistant MFA method best suits your organisation. The two main options are built-in authenticators like Touch ID or Windows Hello, or physical security keys such as a YubiKey. The best choice will come down to how your team operates day-to-day. Factors like whether staff work on-site or remotely, and whether they're using shared machines, personal laptops, or company-managed workstations are all worth considering.

Follow the “rule of two”

One practical principle to build into your planning is what's sometimes called the "rule of two" ensuring there's always a backup route if access is lost. In practice, this might mean each admin registers two different authentication methods, such as a built-in authenticator alongside a physical security key. It also applies at the team level: aim to have at least two admins with full access, so that if one person gets locked out, someone else can step in because if no backup exists and access is lost, getting back in through Salesforce support can mean significant downtime for your organisation.

Act before the deadline

The best way to navigate this transition smoothly is to start now. Review who has access, confirm your MFA configuration, settle on the right authentication methods for your team, and test your critical workflows before June 2026. Just as important is keeping your users informed along the way. Getting ahead of the deadline reduces the risk of disruption and helps ensure the Salesforce data your organisation depends on stays protected.

Final Thoughts

The June 2026 deadline may feel distant, but for nonprofits managing supporter data, donations, and critical operations inside Salesforce, the time to act is now. It's also a good prompt to ask whether the right people still have the right level of access, something many organisations may have not revisited in years.

The good news is that none of this needs to be overwhelming. A structured review of who has access, the right MFA methods in place, and clear communication with your team will go a long way toward a smooth transition. Small steps taken today mean far less disruption when enforcement arrives.