How to Share 2FA Codes With Your Team SecurelyGuide
Four ways teams share two-factor codes, what each one costs, and how to give people the codes they need without handing out the secret behind them.
Blog
How teams share two-factor authentication codes without passing the secret around: practical guides, tool-by-tool walkthroughs and answers to the questions that come up.
Two-factor authentication was designed for one person with one phone. Teams still have to run shared accounts on it. These are the questions that come out of that gap, answered as plainly as we can.
Getting a code to the people who need it, without handing out the secret behind it.
Four ways teams share two-factor codes, what each one costs, and how to give people the codes they need without handing out the secret behind them.
Yes, technically: several devices holding one secret produce the same code. Here is what actually happens when two people use it, and what it costs you.
How to design 2FA access for staff: what to grant per account and per role, what enrolment looks like, and how to handle joiners, movers and leavers.
Five ways to run two-factor authentication on a shared account, compared on setup effort, cost, remote work and offboarding.
The practical ways to give teammates a working TOTP code while the secret stays in one place, and what each approach means for revoking access later.
What Google Authenticator, Microsoft Authenticator and their QR codes can and cannot do for a team.
Google Authenticator has no sharing feature and no notion of a team. The three options that actually work, and how to move an account off one phone.
No, and the useful part is why: who ends up seeing a shared QR code, what they can do with it, and how to judge whether an exposure warrants a reset.
Yes, and it works: the QR code is the secret. Here is exactly what the image contains, what the second phone can do, and what the provider records.
Microsoft Authenticator does two different jobs: a push approval cannot be shared at all, a six-digit code can, without handing out the secret.
Stripe, AWS, social accounts: how 2FA actually gets shared on the tools teams live in.
Most social platforms let people post without ever holding the password. What delegation exists where, and the recovery plan these accounts need.
Nobody should share an AWS login, and the root user accepts several MFA devices instead of one copied secret. What that leaves, and how to run it.
Stripe has team members, roles and restricted API keys, so most shared Stripe logins are unnecessary. What is genuinely left, and how to run 2FA on it.
Practices that hold up for an agency running client accounts, or a team spread across time zones.
Client-owned accounts, forty of them, and staff who rotate. How to ask for proper access, keep clients apart, and hand everything back at the end.
The mechanics behind the six digits, and what follows from them.
How time-based one-time passwords work, which properties of the algorithm cause every shared-account problem, and what a team needs to run TOTP.
What a TOTP secret is as an object, the places copies of it quietly accumulate, and the exact order to reset an account whose secret has already been shared.
What two-factor authentication is, how it protects an account, which methods exist, and why not every form of 2FA offers the same protection.