If you might be scratching your head about recent emails from Salesforce about implementing a Multi-Factor Authentication (MFA) requirement for your organization, you are not alone.
The key challenges we see with product announcements from Salesforce like this one are that they:
- focus on the needs of their medium- to large-scale B2B sales customers, not smallish nonprofits,
- are written for the use of at least moderately experienced in-house Salesforce admins, who can easily identify which parts of the announcement (if any) are relevant for that particular organization.
Many nonprofits don’t fall into these categories. In fact, we have had a few Help Desk clients check in with our team about this email so we thought we would share some information about it so your team can be on top of this Salesforce update.
Our goal with this post is to help nonprofit organizations of various sizes to be able to navigate this change to their MFA with the least amount of headaches.
What is the new MFA requirement in Salesforce?
Beginning February 1, 2022, all Salesforce users will now be required to enable MFA for access to their Salesforce products.
Yep, you have almost an entire year to make sure this change happens.
However, even though this is still a ways out, we don’t want to underplay this update because this changes the way your users login to Salesforce. And you can’t just ignore it until the February 2022 deadline. But don’t panic, because that’s way more time than most nonprofits will need.
What is MFA?
Before we dive into the how, we thought we would actually address what multifactor authentication, or MFA, actually means for your Salesforce users. Read more