Salesforce Authenticator

What differentiates Salesforce Authenticator from other similar products?

Push notifications are faster, easier to use than code

What is your favorite aspect of this product?

on Ios - can hard-touch the push notification and approve from my lockscreen

What do you dislike most about this product?

If my authenticating device is using cellular and my device (that i am trying to authenticate) is using wifi, the approval does not work. both devices need to be on the same network the "remember this device / auth automatically" does not work for me

What recommendations would you give to someone considering this product?

easy to use, simple. no frills.

What differentiates Salesforce Authenticator from other similar products?

I appreciate that it focuses on reducing friction during authentication while maintaining strong security. Features like push notifications and contextual login information make the approval process straight forward.

What is your favorite aspect of this product?

My favorite aspect of it is how simple it makes the MFA process. Instead of repeatedly entering verification codes i can receive a push notification on my phone, review the login request and approve it with just a tap. It provides good security without adding too much friction to the daily workflow.

What do you dislike most about this product?

The main thing i dislike is that the experience is most convenient when the phone and push notifications are working properly. If notifications are delayed or there are connectivity issues then authentication can become a little frustrating.

What recommendations would you give to someone considering this product?

I’d recommend testing the authentication flow with a small group of users first. Pay attention to enrollment, push notification reliability, recovery options and how easily users can authenticate across different devices.

What differentiates Salesforce Authenticator from other similar products?

The differentiator is how deeply it ties Salesforce identity and session management. It’s not just validation a login–it’s part of a broader identity layer that understands Salesforce sessions, policies, and user behavior. And where it really differs, through, is its “ecosystem-first ” design philosophy. It’s not trying to be a universal authentication for every possible service.

What is your favorite aspect of this product?

The thing I appreciate i show well it fits into the broader Salesforce ecosystem. When identity management is tightly integrated, it removes lot of the glue work engineers usually have to deal with–configuring multiple MFA providers, handling edge cases across systems, or troubleshooting inconsistent login experience. And I also like the subtle context it provides during approvals, such as recognizing known device or location.

What do you dislike most about this product?

The drawback is that the push-based approval flow, while convenient, can sometimes feel a bit too “binary.” And I’ve also notice that because it’s so closely tied to Salesforce sessions and identity behavior, it doesn’t offer much flexibility outside that context.

What recommendations would you give to someone considering this product?

The recommendation is to pay attention to user experience and training early on. While the push-based approval flow is simple, users still need to understand what a legitimate login request looks like and how to respond safely. A short onboarding session or internal guideline can go a long way in preventing confusion or accidental approval. And I’d recommend evaluating how it fits into your broader identity and access management setup.