VicRoads' 5 Million User Passkey Rollout by Corbado
VicRoads Launches Passkeys with Corbado
5 Lessons: Passkey Rollout to 5M Users
Corbado deployed passkeys to VicRoads with its 5 million users!
5 Lessons: Enterprise Rollout at VicRoads
1. Passkey Implementation != Adoption
2. Passkey Adoption = Creation + Usage
3. Know your MFA landscape well
4. Gradual rollout to large user bases
5. User education & support is crucial
Why do these statements hold true?
1. Passkey Implementation != Passkey Adoption
The success of your passkey project depends heavily on how many users actually adopt passkeys. Implementation is usually the easy part - but from the very beginning, you need to focus on achieving the highest possible passkey adoption from your users.
If you want to know how Corbado helped VicRoads get 10x higher passkey adoption, reply to this Substack. I'll share 4 strategies with you.
2. Passkey Adoption = Creation + Usage
True passkey adoption doesn't just come from users creating a passkey. User need to actually use the passkeys for their logins. A passkey that isn’t used provides no real benefit (no operational savings, no protection, no UX uplift). Unfortunately, usage is often overlooked - but there are ways to increase it. Focus on making passkeys the default choice and reducing user friction:
Leverage passkey intelligence
Automatically initiate passkey logins
3. Know your MFA landscape well
If you already offer multi-factor authentication (MFA) through legacy methods (e.g. SMS OTP, TOTP via authenticator apps), you need to carefully consider how passkeys will integrate with these. Important questions to address early in your project:
How do passkeys interact with existing MFA methods?
What are the implications for different user states (e.g. deactivated, blocked, pending)?
Is MFA optional or mandatory?
How will MFA recovery work in a passkey-first world?
Addressing these aspects early on will help ensure a smooth transition.
4. Gradual rollout to large user bases
To catch and resolve issues before they impact your entire user base, roll out passkeys gradually. Consider starting with a small fraction of users (e.g. 1%, 5%, 10%) or targeting specific operating system (versions) or browser (versions). That way you can:
Detect technical bugs in your implementation, the underlying operating system / browser or local authenticators
Exclude problematic versions proactively
Minimize risk while optimizing the user experience
5. User education & support is crucial
Most users just want to log in - they don’t read instructions or click on separate passkey buttons. However, some users will have questions or want to learn more. To avoid overwhelming your support team, provide resources like:
This allows users to educate themselves without flooding customer support with questions.
Learn more about deploying passkeys at scale:
Download your free enterprise passkey whitepaper!
Join the Passkeys Community!
Our mission is to free the world from passwords to make the Internet a safer place - this can only be accomplished together.
Join our passkeys community on Slack to connect with other passkeys enthusiasts, stay up-to-date in the passkeys world, get implementation support and show your passkeys projects!