What happens if a Salesforce user misplaces the laptop they typically use for login? Or when an executive needs reliable access to Salesforce but switches between a PC at work, or a laptop at home? Security teams need a way to safeguard access without creating an IT ticket for each device. That is where multiple verification methods become useful.
Salesforce allows a single user to register multiple MFA verification methods. These techniques can include third-party authenticator apps, Salesforce Authenticator, and passkeys such security keys and built-in authenticators. Salesforce multiple passkeys for one user can give employees a secure backup when their primary authentication method is unavailable. For executives, the bigger issue is not simply how many authentication methods a user has. It is whether the organization can keep access secure, resilient, and manageable as people, devices, and business needs change.
This blog describes the best practices executives should take into account for safe, adaptable, and reliable Salesforce access, as well as how to set up numerous passkeys and MFA methods for a single user.
What are Salesforce Passkeys?
Salesforce treats two MFA methods as passkeys: built-in authenticators and security keys. Built-in authenticators include services such as Windows Hello, Touch ID, and Face ID. Salesforce also supports FIDO2/WebAuthn-compliant passkeys managed through compatible password managers or cloud keychains. Passkeys employ cryptographic credentials instead of just a password or one-time code. Using a fingerprint, PIN, facial or iris recognition, or device credential, built-in authenticators can confirm a user’s identity. Security keys use a physical device to complete the verification.
Can One Salesforce User Have Multiple Passkeys?
Yes. A Salesforce user can register more than one MFA verification method. A user can register one method in each of Salesforce’s supported categories such as built-in authenticators, security keys, Salesforce Authenticators, and third-party TOTP authenticator app. This implies that an employe might utilize a company laptop’s built-in authenticator while maintaining a backup security key. If the employe frequently works from a different computer, they can also register a built-in authenticator on that device if the browser and device satisfy Salesforce’s specifications.
Why Use Salesforce Multiple Passkeys for One User?
Maintain Backup
Salesforce advises users, especially Salesforce admins, to register a minimum of two verification methods. If a primary device is misplaced, replaced, broken, or just unavailable, a backup solution can assist the user in regaining access to the account, without causing a hardware issue to interfere with business operations.
Strengthen Salesforce Passkeys MFA
Salesforce passkeys MFA gives organizations a phishing-resistant option for authentication. Built-in authenticators and security keys satisfy Salesforce’s phishing-resistant MFA requirement for privileged users.
Support Multiple Work Devices
Reduce Login Friction
Passkeys can use a fingerprint, face scan, device PIN, or physical security key in place of repetitive code entry. This results in a login procedure that is intended to be more robust and user-friendly for staff members.
Salesforce Passkey Setup: How to Add Multiple Passkeys
Step 1: Set Up the Verification Techniques
From Setup > Identity Verification, Salesforce administrators can control MFA verification techniques. Four MFA verification categories are supported by Salesforce:
- Built-in authenticators
- Salesforce authenticator
- Physical security keys
- Third-party authentication apps
Admins may need to activate passkey methods for organizations founded prior to Summer ’25. According to Salesforce, organizations founded after Summer ’25 are automatically permitted to use the supported verification methods.
Step 2: Register the First Method
Step 3: Add Another Verification Method
Step 4: Select a Reasonable Backup
It is not necessary for the backup to be exactly the same as the primary approach. In fact, employing a variety of techniques can strengthen the overall access strategy. A practical setup might look like this:
- The employee’s primary laptop has an integrated authenticator.
- Physical security key as a backup
The right combination depends on the user’s role, devices, and your organization’s security policy.
How Does Salesforce Choose Between Multiple Passkeys?
Once multiple verification methods are registered, Salesforce does not require the user to guess which verification method to use first. The method with the highest importance is automatically prompted. When necessary, users can switch to a different registered method.
For instance, Salesforce asks for the built-in authenticator first if a user has both a security key and a built-in authenticator. The user can choose the security key and select Use an alternative verification method if that isn’t feasible.
Salesforce Passkeys MFA vs. Password-less Login
Salesforce Passkeys MFA | Password-less Login with Passkeys |
The passkey acts as an additional layer of identity verification | The passkey is used as the primary authentication method |
Built-in authenticators and security keys can provide phishing-resistant MFA | Salesforce supports password-less login with registered built-in authenticators and security keys for eligible internal users |
The user signs in with their Salesforce credentials and then uses a passkey as the MFA verification method | The user signs in using a registered passkey without entering a password. |
Useful when an organization is implementing or strengthening its existing MFA strategy | Useful for organizations moving eligible internal users toward a password-less authentication experience |
Conclusion
Employes can maintain a single Salesforce identity while strengthening authentication with a well-thought-out passkey arrangement. When their preferred method isn’t accessible, users can switch to another registered method. The platform enables several MFA verification methods for a single user. For businesses, the right question is not simply, how many passkeys should we give each user? It is, what authentication strategy gives our people secure access without creating unnecessary operational friction?
That means prioritizing phishing-resistant passkeys, offering workable backup solutions, safeguarding privileged accounts, preparing device modifications, and integrating authentication management with the larger identity strategy. When those pieces are in place, Salesforce multiple passkeys for one user can do more than improve login security.