Loading

Salesforce Authenticator Troubleshooting

Udgivelsesdato: Sep 23, 2026
Beskrivelse

This article helps you troubleshoot common issues with Salesforce Authenticator, the mobile app used for multi-factor authentication (MFA) with your Salesforce account. Use the sections below to find fixes for login problems, location-based automation issues, slow approval responses, and new phone setups.

Løsning

This article answers the question: what should you do when Salesforce Authenticator isn't working as expected, whether you can't log in, the app won't remember your trusted location, approvals are slow to arrive, or you've switched to a new phone? Use the sections below to find the fix that matches your situation.

Can't Log In and Need Immediate Assistance

Salesforce Authenticator Not Remembering Your Location

  • Ensure Location Services is set to "Always" and Background App Refresh is enabled in iOS, or enable Improve Location Accuracy in Location Services in Android. See Automate Multi-Factor Authentication with Salesforce Authenticator for more help.

  • Ask your Salesforce administrator if automation is configured to only work on certain networks.

  • Remove all previously trusted locations, and re-add them.

  • Confirm that "Let Salesforce Authenticator automatically verify identities using geolocation" is enabled, and "Let Salesforce Authenticator automatically verify identities based on trusted IP addresses only" is disabled in Setup under Identity Verification.

  • Note that the following criteria must be met for auto-approval to take place:

    1. Same user
    2. Same action (login, download reports, add new verifier, etc.)
    3. Same device (browser)
    4. Same location (within 100 meters)

  • For more troubleshooting tips, see Optimize and Troubleshoot Automation in Salesforce Authenticator.

Salesforce Authenticator Is Slow to Respond, or the Approval Button Isn't Displayed

  • Check your phone's network connection. Slow Wi-Fi or cellular connections will affect the speed of push notifications.

  • On the Salesforce Check Your Mobile Device page, tap "Having Trouble?" and then tap "Use a Different Verification Method." Enter the 6-digit code from Salesforce Authenticator. This works even when your phone is offline.

New Phone, Lost Phone, or New Installation of Salesforce Authenticator

  • If you previously backed up your connected accounts, you can restore your configuration. See Restore Connected Accounts in the Salesforce Authenticator Mobile App to learn how.

  • If necessary, remove the account from Salesforce Authenticator, re-configure Salesforce Authenticator, and then (optionally) turn on backup. See Connect Your Salesforce Account to Salesforce Authenticator for setup steps.

  • If your phone is lost or stolen, or you have a new phone and the previous one is unavailable, follow the steps in the "Can't Log In and Need Immediate Assistance" section above. Your Salesforce administrator can remove the connection from the inaccessible phone. Contact Salesforce Support if your administrator can't assist.

Why You're Sometimes Asked for a Two-Word Phrase

Salesforce Authenticator connections are paired with devices, not phone numbers. When you change devices, the new installation doesn't know about your existing connection, so you're shown a two-word phrase to set up a new one. Since your old device still has an active connection with Salesforce, we ask for that phrase to confirm the switch — this is why a Salesforce administrator should remove the old connection first.

In the reverse scenario, if Salesforce asks for a two-word phrase, it usually means the Authenticator app still has a connection to an old account, a sandbox account, or a different account, and the account you're signing in to doesn't yet have a connection. In that case, the connection needs to be added.

See also:

Still Need Help?

Vidensartikelnummer

000380378

 
Indlæser
Salesforce Help | Article