The short answer
Turn on 2FA first for business email — it receives the password-reset links for everything else. Then protect the password manager itself, banking and payment accounts, your website, domain and hosting, social and review accounts, and the register/POS. Prefer an authenticator app or a security key over text-message codes where the service allows it. Save the backup codes in the password manager at the moment each account is set up, give every person their own sign-in and their own second factor, and write down which accounts are done. An account nobody listed is an account nobody protected.
Never share a second factor. A code texted to one person's phone and read out to the team is not 2FA for the team — it is a shared password with extra steps, and it leaves with that person. Where a service offers roles or individual accounts, use them. Where it truly offers only one login, the owner enrols the second factor and stores the backup codes in the team password manager.
The setup order, account by account
Work down this table. Each row takes minutes, and the order matters: the accounts at the top can reset or unlock the accounts below them.
| Order | Account | Why it ranks here | Preferred second factor |
|---|---|---|---|
| 1 | Business email / workspace (Google Workspace, Microsoft 365) | Receives password-reset links for almost every other tool | Authenticator app or security key; owner and every staff account |
| 2 | Password manager (the team vault itself) | Guards every other credential the business owns | Authenticator app or security key, per person |
| 3 | Banking, payment processors, accounting and payroll | Where money can actually move | Whatever the provider offers — app, key or text — turned on, not optional |
| 4 | Website admin, domain registrar and hosting | Whoever controls the domain controls email delivery and the site | Authenticator app; recovery contacts confirmed as the owner's |
| 5 | Social media, Google Business Profile and ad accounts | Public-facing: a hijacked page talks to your customers in your name | Authenticator app per person with a role, not a shared login |
| 6 | Register / POS, booking and customer tools | Hold customer data and daily takings | App or text code per staff login; deactivate leavers the same week |
| 7 | AI tools and automations connected to business accounts | A connected assistant can reach whatever its account can reach | Same 2FA as the account it connects through; review its access, too |
Choosing the second factor
Authenticator app — the default choice
A free app generates a new code every 30 seconds on the person's own phone. It is not tied to a phone number, works without signal, and is supported by most business tools. Enrol each person separately, on their own device.
Hardware security key — the strongest option for key accounts
A small physical key you tap or plug in. Worth it for the owner's email, the password manager and banking, where one account opens everything. Keep a spare key enrolled and stored in a locked place, or a lost key becomes a lockout.
Text-message (SMS) codes — better than nothing, last in line
A code sent by text depends on control of the phone number, which can be moved or swapped by an attacker dealing with the carrier. Use SMS where it is the only option offered, and switch to an app or key when the service adds one.
About push approvals and biometrics: approving a sign-in prompt on your own phone, or unlocking an authenticator with your fingerprint or face, is fine — the proof still lives on that one device. What matters is that the second factor is personal, physical and not forwarded around the team.
Backup codes: the step everyone skips
Most lockouts are self-inflicted: a phone is replaced, the app is not transferred, and the only second factor is gone. Prevent that in the same sitting as the setup.
- Generate the backup / recovery codes the service offers at setup time — not later, when you are already locked out.
- Store them in the team password manager, attached to the entry for that account, labelled with the date.
- For the top three accounts (email, password manager, banking), also print the codes and keep them in a locked place the owner controls.
- Never store codes in the inbox they protect, in a shared chat thread, or in a photo on the same phone as the authenticator app.
- Test one recovery path on a low-risk account so the team has done it once before it is urgent.
Rolling it out to staff in one afternoon
- Owner first. Set up your own email, vault and banking, including backup codes. You are the recovery path for everyone else.
- One person at a time, phone in hand. Each staff member enrols their own authenticator on their own accounts while you watch it work — a successful sign-out and sign-in is the proof, not a promise to do it later.
- Shared logins get a decision, not a code. Replace them with individual accounts or roles where offered. Where not offered, the owner holds the second factor and the vault holds the backup codes.
- Write the list. Account, person, method, backup codes stored — yes or no, date. That list is your record, and it is also your offboarding list when someone leaves.
- Set the leaver rule now: when a person leaves, their accounts and second factors are removed the same week — see our employee offboarding access checklist.
Five mistakes that quietly undo 2FA
- 2FA on email, but not on the registrar: whoever resets the domain can reroute the email itself. Protect the accounts that can reset other accounts.
- One phone holds every code for the whole team — including for people who have left.
- Backup codes in a screenshot in the same photo library, on the same phone, as the authenticator app.
- “Remember this device” on shared computers at the register or front desk, which skips the second factor for the next user too.
- No record of what was set up, so nobody knows which accounts are still password-only until one of them is used against the business.
One-page summary
- Email first — it resets everything else.
- Then the password manager, banking and payments, website and domain, socials, POS and AI tools.
- Authenticator app or security key preferred; SMS only where nothing else is offered.
- Every person: their own sign-in, their own second factor. No shared codes.
- Backup codes generated at setup and stored in the password manager; printed copy for the top accounts.
- Test sign-out and sign-in on the spot — proof, not promises.
- Keep an account list: account, person, method, codes stored, date.
- When someone leaves, remove their access and factors the same week.
- 2FA is layer one of seven — not the whole shield.
Not sure which of your accounts are still password-only?
Two-factor sign-in is the first of the seven layers in the CyberShield audit — a written $99 review of your business’s public-facing setup and questionnaire answers, with no passwords or account access needed. Every weak spot, how risky it is, and what to fix first, in plain English. If you want the fixes done for you, the report quotes the done-for-you Setup (from $299) before you decide; the Care Plan is $49/month if you want monthly check-ins after that. Full refund if we have not started the work; once work has begun, payments are non-refundable, as described in our Refund Policy.
Start with the free 2-minute cyber checklist, or go straight to the audit:
Start the $99 auditCommon questions
Which account should get two-factor authentication first?
Business email. Password-reset messages for almost every other tool land in that inbox, so a protected email account protects the reset path for everything else. After email, protect the password manager itself, then banking and payment accounts.
Is an authenticator app better than text-message codes?
Usually yes. An authenticator app or a hardware security key is not tied to your phone number, so it is not exposed to SIM-swap or number-porting tricks. Text-message codes are still far better than no second factor at all — use them where nothing else is offered, and upgrade when the service allows it.
How should a small team handle shared accounts?
Avoid shared logins where the service offers individual accounts or roles — each person should sign in as themselves and use their own second factor. For the few services that only allow one login, store the credential in the team password manager and enrol the second factor in a way the owner controls, so a staff change does not lock the business out.
Where should backup or recovery codes be stored?
In the business password manager, under the account they belong to — and for the most critical accounts, also printed and kept in a locked place the owner controls. Never in a shared chat thread, a sticky note, or the same inbox the codes protect.
What happens if someone loses their phone?
Use a backup code or an admin reset to sign in, then immediately re-enrol the second factor on the new phone and revoke the old device. Plan for this before it happens: every critical account needs a second recovery path that does not depend on one person's handset.
Does two-factor authentication make us safe?
No single setting makes a business safe. 2FA closes the most common door — a copied or reused password working on its own — but phishing, device theft and accounts without 2FA remain. It is layer one of seven in a basic small-business checkup, not the whole shield.