CyberShield · Password manager guide

How to set up a password manager for a small business team

Paper notes, a shared spreadsheet and one password used everywhere all fail the same way: you cannot take them back. This is the setup order that moves a small team into one password manager in an afternoon — master keys first, everyday tools last.

Start the setup orderFree 2-minute cyber checklist

The short answer

Create the team account under the owner's business email, protect it with a unique master passphrase and two-factor sign-in, then move logins in risk order: owner email and money tools first, customer-facing accounts next, everyday tools last. Give every person their own sign-in, share logins through team vaults instead of messages, and make one rule permanent: a new login is born in the manager, never on paper.

Why order matters. If you move the everyday tools first and run out of afternoon, the business is still one copied spreadsheet away from losing its bank and email logins. Move the accounts that can reset or spend first — everything else is convenience.

Before you start: choosing the tool

This guide is deliberately tool-neutral — the setup order matters more than the brand. Whatever you pick, it should have these five properties:

  • A business or team plan with individual seats — not one shared account for the whole shop.
  • Shared vaults or folders you can grant per team, so the register login and the bookkeeping login do not live in the same pile.
  • Two-factor sign-in for the manager itself, and recovery codes you can store offline.
  • Admin controls: invite and remove people, see who has access to what, and recover the vault if the owner is locked out.
  • Apps and browser extensions your team will actually use on the phones and computers they already have — a manager nobody opens gets bypassed by sticky notes within a week.

The setup order, group by group

Four groups, in this order. For every login you move: generate a fresh unique password in the manager (do not import the old reused one), turn on two-factor sign-in where the account offers it, and note who needs access.

1. The master keys: owner email and the manager itself

  • Create the team password manager under the owner's business email — never a personal or shared inbox.
  • Set a unique master passphrase, turn on two-factor sign-in for the manager, and store its recovery codes offline (sealed envelope in a locked place the owner controls).
  • Name one backup admin — a second trusted person who can help if the owner is unreachable, with their own sign-in, never the owner's.

2. Money and identity: banking, payments, domain, hosting

  • Move banking, payment processors, accounting and payroll logins in next — these are the accounts a copied password spends from.
  • Add the domain registrar, website hosting and business email admin. Whoever controls these controls the business's public face.
  • For each one: generate a fresh unique password inside the manager, turn on two-factor sign-in, and store the backup codes in the manager entry.

3. Customer-facing accounts: socials, reviews, booking, POS

  • Move the Facebook Page, Instagram, Google Business Profile, review sites, booking system and register/POS logins.
  • Where the platform supports roles or team access, give people roles under their own names instead of sharing one login.
  • Check whose phone number and email the recovery messages go to — it should be a current team member, every time.

4. Everyday tools: cloud files, chat, marketing, AI tools

  • Finish with file storage, team chat, email marketing, supplier portals and the AI assistants and chatbots the business runs.
  • AI tools belong in the manager too: their accounts often stay connected to email, files and the store after the person who set them up has moved on.
  • Delete or archive entries for tools the business no longer uses — a vault full of dead logins hides the live ones.

Structure: three vaults are enough to start

  • Owner vault (private): banking, registrar, hosting, email admin, the password manager's own recovery information. Owner and backup admin only.
  • Team vault (shared): the logins the whole team genuinely shares — supplier portals, the register, shared service accounts. Shared through the manager, never pasted into chat.
  • Personal vaults (one per person): each person's own work logins under their own sign-in. When they leave, their vault goes with their seat — and nothing else is affected.

Resist building a folder for every tool on day one. Three vaults that everyone understands beat twelve that nobody does; you can split the team vault later, when a real boundary appears.

The five rules that keep it working

  • New logins are born in the manager. Creating an account somewhere? The password is generated and saved in the manager at that moment — not written down "temporarily".
  • Never send a password in chat, email or text. Share the vault entry instead. A password in a message thread lives there forever, on every phone that ever joined the thread.
  • One person, one sign-in. No shared manager accounts, no shared master passphrase — individual sign-ins are what make removal and accountability possible.
  • Leaving means rotation. When someone leaves, remove their seat and rotate every shared password they could see. The offboarding access checklist covers the full sweep.
  • Review access quarterly. Fifteen minutes, four times a year: who is in which vault, which entries are dead tools, whose recovery phone is outdated. Access lists rot quietly; the review is the fix.

Two things not to do. Do not store the manager's master passphrase inside the manager itself, and do not make the spreadsheet the "backup" — exporting the vault back into a shared file recreates the original problem. The offline recovery codes, stored sealed, are the backup path.

One-page summary

  • Create the team account under the owner's business email.
  • Unique master passphrase + two-factor on the manager; recovery codes offline.
  • Name a backup admin with their own sign-in.
  • Move logins in risk order: email and money, customer-facing, everyday tools.
  • Fresh unique password for every login as you move it — never import a reused one.
  • Three vaults to start: owner, team, personal.
  • Share vault entries, never passwords in messages.
  • New logins are born in the manager, starting today.
  • Quarterly 15-minute access review on the calendar.

Not sure which of your logins are still on paper?

The password manager is layer two of 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 across all seven layers, 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. Full refund before work begins.

Start with the free 2-minute cyber checklist or the two-factor setup guide, or go straight to the audit:

Start the $99 audit

Common questions

Does a small business really need a password manager, or is a spreadsheet enough?

A spreadsheet — even a password-protected one — is usually shared as one file with one password everyone knows, and it cannot be taken back when someone leaves. A team password manager gives each person their own sign-in, lets you share a login without showing the password, and lets you remove one person without changing every password in the business.

What should go into the password manager first?

Start with the accounts that can reset or spend: the owner's business email, banking and payment tools, the domain registrar and website hosting, and the social and review accounts customers see. Then work through the everyday tools. The order matters for the same reason as two-factor setup: email first, because email resets everything else.

Should staff share logins through the manager?

Share the access, not the password itself. Put shared logins in a shared vault or folder for the team that needs them, and keep personal logins in each person's private vault. Where a tool offers individual accounts, use those instead of one shared login — individual accounts are what make removal clean when someone leaves.

What makes a good master password?

A long passphrase the owner has never used anywhere else — several unrelated words plus numbers is easier to remember and harder to guess than a short complicated string. Turn on two-factor sign-in for the password manager itself, and store its recovery codes offline, somewhere only the owner (and one trusted backup person) can reach.

What happens when an employee leaves?

Remove their seat from the password manager, then rotate every shared password they could see. That second step is the one businesses skip — and it is the step that makes removal real. Our employee offboarding access checklist walks through the full same-day sweep, account by account.

Is this legal or security advice for our specific business?

No. This guide covers the general setup order and habits for a small team. Regulated businesses — health, finance, legal — may have extra rules about which tools they can use and how access must be logged; check your industry's requirements or ask a professional in your field.