Salesforce MFA: Setting Up Multi-Factor Authentication for Your Org
Salesforce made multi-factor authentication (MFA) a contractual requirement for anyone signing in to a Salesforce product, and for good reason: a password alone is no longer enough to protect the customer data sitting in your org. If you are the admin who has to roll MFA out, here is a practical plan that gets everyone enrolled without a revolt.
1. Pick the verification method first
Salesforce supports three methods: the Salesforce Authenticator app, a third-party TOTP app such as Google Authenticator, and a physical security key. The Salesforce Authenticator app is the smoothest default — it pushes a notification the user approves, and it works offline with time-based codes as a fallback. Security keys are the strongest option and make sense for system admins and anyone with broad data access. Let users choose between the app and a TOTP app, but require security keys for your admin team.
2. Turn it on in stages, not all at once
Go to Setup → Identity Verification and enable MFA for the profiles that need it, starting with System Administrators and a small pilot group of friendly users. Run the pilot for a week, fix the friction points (usually: users who never got the enrollment email, or people on shared devices), then roll out profile by profile. A big-bang rollout on a Monday morning is how MFA projects earn a bad reputation.
3. Handle the exceptions properly
Some users genuinely cannot use a phone app — a shared service account, a kiosk login, an integration user. For those, use a security key or a dedicated hardware token, and document the exception with an owner and a review date. What you should never do is exempt a human user's profile "temporarily" and forget about it — that exemption becomes permanent, and it becomes the attacker's easiest door in.
4. Don't forget your integration and API users
MFA applies to interactive logins, but your integrations log in too. API-only users should use OAuth flows or a dedicated integration user with a strong password, IP restrictions, and login hours locked down. A good habit is to review the Login History report monthly for any login that bypassed MFA — Salesforce flags these, and every one of them deserves a look.
5. Train users on the recovery flow before they need it
The number one MFA support ticket is "I got a new phone and I'm locked out." Before rollout, publish a one-page guide: how to register a second verification method, who to call when locked out, and how the admin resets MFA for a user (Setup → Users → the user's record → reset the MFA registration). Admins who can reset MFA quickly turn a crisis into a two-minute fix.
Good data hygiene starts with knowing your data is clean — our guide to why every AI strategy needs data cleaning first explains why bad data undermines every automation you build on top of it. And if you're tightening access more broadly, our permission sets with expiration dates walkthrough shows how to grant powerful access that switches itself off.
MFA is not a project you finish and forget. Review enrollment monthly, chase the stragglers, and re-check your exception list every quarter. The orgs that get breached are rarely the ones without MFA — they're the ones where MFA was enabled for everyone except the one account that mattered.
Originally published at Way2Force — practical guides on Salesforce Flow, automation, and CRM.
Top comments (0)