Before reps switch to passkeys, check device support, syncing, verification prompts and company sign-in rules on the phones and laptops they use.
Key takeaways
- Check each device against its password manager's minimums.
- Test syncing and any passkey-based 2FA your reps need.
- Record verification prompts on phones and laptops.
- Get written answers from your IT owner about company sign-in rules.
A passkey lets someone sign in without typing a password. Whether that works for your team depends on three things: the devices your reps carry, the password manager or app they use to store passkeys, and the sign-in rules your company applies to the accounts reps use every day.
The cost is the work of making sure the devices, the apps and the company's rules all line up, and that work falls on you before any rep is asked to change how they sign in. The checks below show where the gaps are, so the decision rests on evidence rather than enthusiasm for a new method.
There are four checks in this post. Each one points to an official page.
You do not need to be a security engineer to run these checks. You need a short list of your reps' devices, a list of the sign-in apps your team uses, and a test account you can use without touching anyone's live customer data. Give yourself a short block of time for the first three checks, and bring in your IT or security owner for the last one. Treat the result as a planning guide, not a replacement for your company's own security review.
Confirm each phone meets its operating system minimum
Each phone has to run an operating system version that your password manager supports. The vendor's help page on storing passkeys publishes the minimums for its own app. According to the autofill passkeys help page, "You can save and use passkeys from Bitwarden with iOS version 17.0+." The same page says, "You can save and use passkeys from Bitwarden with Android version 14.0+."
Those figures belong to that app alone. If your reps use a different password manager, find that product's own minimums and check each phone against them. Do not carry a number over from one vendor to another, even when the products look alike. A figure that is correct for one app can be wrong for the next.
The minimums also work as a simple filter. A phone below the stated minimum for its operating system falls short, whichever platform it runs. The two platforms have different minimums, so you cannot use one number for both. Check each phone against the line for its own operating system.
Start with a list. Write down each rep's phone model and its current operating system version. A team can look uniform on paper and still include several older phones, so the list is the only reliable way to know. Mark every rep who falls below the minimum. For those reps, you have two practical choices: ask them to update the phone if an update is available to them, or keep them on passwords until they have a device that meets the minimum. Either choice is fine, as long as you make it on purpose and write it down.
Illustrative example: checking a team's phones
The reps who meet the minimum can move on to the next step. The rep with the older phone can wait for an update or stay on passwords for now. The rep with the unchecked phone is not cleared until someone reads the version number off the screen. A list like this takes little time to build and saves a round of guessing later.
Laptops need their own check. The minimums above cover phones only. Ask your password manager vendor which laptop operating system versions it supports before you approve laptop sign-ins, and put that answer beside the phone list so you can compare the two when a rep gets a new device.
Keep the list current. A rep who replaces a phone midyear may arrive at a version that does not meet the minimum, or may carry a device the list does not cover. Make the phone version part of onboarding and part of any device change. A quick check when a rep gets a new phone costs far less than a rep who cannot sign in during a customer call.
A phone that meets the minimum can still fail a later check, so passing this step is a starting point rather than a final approval. Record the result for each rep and carry that record into the tests that follow.
Decide whether passkeys sync or stay on one device
Decide whether each rep's passkeys will sync across devices or stay tied to a single piece of hardware, because the two choices behave differently and suit different jobs. The autofill passkeys help page describes both options: a passkey is "a discoverable FIDO credential that can be synced to allow secure passwordless sign-ins across devices or dedicated to a single piece of hardware as a device-bound passkey."
Read that description as a choice between two setups. A synced passkey is meant to allow sign-ins across devices, which can matter for a rep who works from a phone in the field and a laptop at a desk. A device-bound passkey is dedicated to one piece of hardware. Neither option is right for every rep. Decide which setup fits each role, and write the decision down so a new manager or a new hire can see it later.
Consider two kinds of rep. One visits customers and signs in on a phone between meetings, so a passkey available on that phone may matter most. Another spends the day at a desk and rarely uses the phone for work. Their needs may point to different choices. A choice made without thinking about a rep's day can create problems later, and a choice made on paper should be tested before it becomes policy.
Passkey-based 2FA is a limit you must test rather than assume. The same help page says, "Android does not allow third-party passkey providers like Bitwarden to support passkey-based 2FA, also known as 'non-discoverable credentials.'" That sentence concerns Android and third-party providers, and it describes a limit on what those providers can support. If any sign-in your reps need depends on passkey-based 2FA, run that exact sign-in on an Android phone that uses a third-party password manager. Do not assume it works because the phone meets the version minimum.
Moving passkeys between tools is a separate question. The same page notes that on mobile, passkeys "can also be imported and exported directly using the FIDO Credential Exchange Protocol (CXP), on iOS 26+ and Android 14+." If a rep changes password managers, or your company changes the one it recommends, ask the vendor how passkeys move, and test one move with a test account before you tell reps it is supported.
Give each sync test a clear pass or fail. Record which sign-ins worked, which did not, and what the rep saw on each screen. A failed test is useful information. It tells you which flows to keep on a password while you look for another option, and it keeps the decision tied to what actually happened.
Share the results with the rep and with your IT owner before you decide. Ask the rep what felt slow or confusing, and ask the IT owner whether any failure points to a setting that can be changed. A short conversation at this stage can prevent a larger problem after rollout.
Plan the fallback before you need it. If a sync test fails for a rep, decide in advance what that rep will use: a password, a different manager that passed the test, or a support request to the vendor. A written fallback keeps a rep from being stuck mid-day and keeps you from making a rushed decision under pressure. Include lost-phone recovery in that planning.
Compare each vendor's documentation on syncing, device-bound passkeys and Android limits before you commit to one. A tool that suits a team of field reps may not suit a team that works mostly from one laptop, and the only way to find out is to read the documentation and run the test.
Check which verification prompts reps will see
Reps may be asked to verify themselves when they save a passkey or use one, and the prompt they see depends on what the app or service requests. The autofill passkeys help page says, "Apps and services can request that passkeys created with them are verified with a PIN, password, pattern, or biometric factor when you save or access them." Because the request comes from the app or service, do not assume the same prompt appears in every app your team uses.
Test this on real devices. Pick the handful of sign-ins that matter most to a sales team. Your list might include the customer relationship tool, email, the expense system and any shared file storage your reps use every day. For each sign-in, try it on the rep's phone and then on the laptop. Note which prompt appears: a PIN, a password, a pattern or a biometric check. Note whether the prompt appears when the passkey is saved, when it is used, or both. A table with a row for each app and a column for each device is enough.
The same page includes a setting to check: "Verify that the Ask to save and use passkeys option is checked." That line describes one app. If your reps use a different tool, find the setting that controls saving and using passkeys in that tool, and confirm it on a test device before you explain the process to reps. A setting nobody checked can be the difference between a smooth rollout and a confusing one, so make it a line in your test.
The prompt question matters more for a sales team than it might seem. Reps may sign in to several tools during one customer visit, and each prompt is a moment where a rep can stop or call for help.
Timing matters as well. A verification request that appears in the middle of a customer call is a different problem from one that appears at a desk. You cannot control every moment a prompt appears, but you can notice which prompts land at awkward times and raise them with the vendor or your IT owner before rollout. Note any prompt a rep would find confusing or disruptive, even if it works correctly.
If a prompt fails on one device but works on another, do not assume the app is at fault. Compare the two devices side by side. Check the operating system version against the phone list, check the password manager setting, and confirm the rep is signed in to the same account on both. If the problem continues, send the vendor the exact steps you took so it can reproduce the problem.
Keep a simple record of each test: the rep, the device, the app, the prompt, the result and the date. That record is your evidence when a question comes up later, and it is the easiest way to see whether a fix worked.
Tell reps what to expect. A rep who receives an unexpected PIN or biometric request may think the sign-in is broken and call for help. A one-page note with a screenshot from your own test, showing the prompt each app shows on each device, can answer many of those questions before they arise. Keep it short and update it when a prompt changes.
Match passkey sign-ins to your company's sign-in rules
Passkey sign-ins have to fit the sign-in rules your company already enforces, and some identity systems let administrators require particular methods for sensitive resources. The documentation for one such system is the authentication strengths overview. According to it, an authentication strength "can require users to use only phishing-resistant authentication methods to access a sensitive resource."
The same overview gives two more examples. One describes a resource that requires a passkey (FIDO2) for the authentication strength, along with a 1-hour sign-in frequency. The other describes a user who signed in with a passkey (FIDO2) to access the resource 24 hours ago. These are examples, not rules for your company. They show, however, that the method a resource asks for and the timing of sign-ins can be set together, so a rep may be asked to sign in again on a schedule.
Read those examples as questions for your IT or security owner. Which resources do reps reach, and do any of them carry a rule that asks for a specific method? Does that rule accept a passkey? How often does it ask a rep to sign in again, and does that schedule suit a rep who works across a phone and a laptop all day? You are not expected to answer the technical details yourself. You are expected to ask the questions and get written answers before you approve passkeys for any resource that matters to the business. For related policy checks, see seller logins that skip your password policy.
Write down each answer and keep it with the device list and the prompt table. A decision that rests on written answers from your IT owner is easier to defend later than one that rests on an unrecorded conversation. If an answer is unclear, do not approve passkeys for that resource yet. Ask again, or ask for the documentation that covers it.
Decide who approves exceptions too. When a rep needs a passkey for a resource the rules do not clearly cover, one named person should review the question and record the answer. Without a named owner, exceptions tend to spread quietly across a team, and that is hard to undo.
If your company does not use that identity system, the examples do not apply to you. Read the documentation for the system you do use and check whether its rules accept passkeys for each resource your reps need. Each system has its own settings and vocabulary, so a rule written for one system may not work the same way in another.
Put the four checks together before you decide. A rep should be cleared for passkey sign-in only when the phone or laptop meets the vendor's stated minimum, the sync choice fits the rep's job, the verification prompts work in a test, and your company's sign-in rules accept a passkey for the resources that rep uses. If any one of those fails, keep that rep on a password until the gap is closed, and say so in writing.
A small pilot is a sensible step before full rollout. Choose reps whose phones and laptops differ, give them a clear list of apps to use with passkeys, and ask them to report every prompt, failure and delay over a period you choose beforehand. Compare what they report with your recorded tests. If the pilot matches the tests, widen the group. If it does not, the gap shows you what to fix before more reps are affected.
Once the checks pass, tell your reps what to expect. Explain which devices are covered, which sync choice applies, which prompts they will see, and who to contact when a sign-in fails. Vendor minimums and settings can change, so put a review date on the calendar and check the linked pages again before each rollout or device refresh. A decision that was right last year may need a second look today.
Today, list your reps' phone versions and choose a test account for the first device check.
Questions before rollout
Does meeting the phone minimum mean a rep can switch?
No; device support is only the first check. Syncing, prompts and company sign-in rules still need testing or review.
What should happen when a test fails?
Keep the affected sign-in on its existing method while you investigate. Record the failure and agree on a fallback with your IT owner.