Password Manager for a Small Team and How to Roll It Out
Your team shares the hosting login in a chat thread, the registrar password lives in one founder's head, and nobody remembers who still has the old billing account.

Your team shares the hosting login in a chat thread, the registrar password lives in one founder's head, and nobody remembers who still has the old billing account. A password manager for a small team fixes that mess, but only if the rollout is planned so people actually move their credentials into it instead of keeping a spreadsheet on the side.
This guide covers how to pick one, how to structure vaults, and how to run the migration in about two weeks for a team of three to fifteen people. It assumes you run some of your own infrastructure: servers, a mail domain, a few SaaS dashboards, and a pile of API keys.
What a password manager for a small team has to do
Personal password managers are built around one person and one set of devices. A team product adds three things you cannot fake with a shared login to a personal vault:
- Shared vaults with permissions. The contractor who builds your landing page should see the CMS login and nothing else.
- Offboarding. When someone leaves, you revoke their access in one place and get a list of every credential they could see, so you know what to change.
- Recovery that does not depend on one person. If the owner account is lost, at least one other admin must be able to restore access.
Everything else, browser autofill, TOTP storage, breach alerts, is nice but secondary. Judge products on those three points first.
Hosted or self hosted
Readers of this site often want to self host everything, and Vaultwarden (a lightweight server compatible with the Bitwarden clients) runs happily on a 1 GB VPS. It works well. The real question is if your team should be the one responsible for it.
A self hosted vault adds a backup job, TLS renewal, upgrades, and a hard dependency: if the server is down, nobody can log in to the server panel that would fix it. Teams that already run monitoring and tested backups can handle that. Teams that do not should pay for hosted. Business plans for the common products cost roughly 4 to 8 US dollars per user per month, so a team of six pays around 300 to 600 dollars a year.
If you do self host, keep an encrypted export of the vault on a separate machine, refreshed weekly, and make sure the restore steps are written somewhere outside the vault itself. Our step by step guide to restic backups on a self hosted server covers the backup half.
Designing vaults before anyone imports anything
The most common mistake is importing everything into one shared vault on day one. Six months later, every new hire sees every credential, and nobody wants to untangle it. Spend 30 minutes sketching the structure first.
A layout that works for most small teams:
| Vault | Who has access | Typical contents |
|---|---|---|
| Infrastructure | Engineers on call | Server root recovery, DNS registrar, cloud console, backup encryption keys |
| Mail and domains | Admins only | Mail provider admin, DKIM private key notes, domain transfer codes |
| Business tools | Everyone | Shared design tool seat, analytics viewer, team social account |
| Finance | Founders and bookkeeper | Bank portal, payment processor, accounting software |
| Break glass | Two named admins | Owner account recovery codes, emergency kit for the password manager itself |
Keep personal accounts in each person's private vault. The company never needs to see someone's streaming login, and mixing the two makes offboarding awkward.
The two week rollout plan
Days 1 to 3: admins only
Two admins create accounts, enable two factor authentication on the password manager itself, and store their recovery kits in the break glass vault plus one offline copy each. Then they migrate the infrastructure and mail credentials. Doing the sensitive vaults first means you find awkward items, like SSH key passphrases or API tokens with notes attached, before the rest of the team arrives.
Days 4 to 7: everyone joins
Send invites with a 20 minute call booked for each person or small group. In that call, install the browser extension and the phone app, and move three real logins together. People who leave the call with working autofill keep using the tool. People who are sent a link and a PDF often do not.
Days 8 to 14: hunt down the stragglers
Search your chat history and shared documents for words like "password", "login" and "pw". Every hit is a credential to move, then change, because it has been sitting in plain text. Delete the old messages after the change. This is tedious and it is the step that actually reduces risk.
While you are in there, list any API keys you find. They belong in the vault too, and moving them is a good moment to set up the process in our piece on why rotating API keys still trips up small engineering teams.
Where common advice gets it wrong
A lot of security checklists say the first thing to do after rolling out a password manager is force everyone to change every password immediately. For a small team, that usually backfires.
Mass resets on day one create a flood of lockouts, confused coworkers, and services that send verification codes to an old phone. People get frustrated and quietly keep a copy of the old password "just in case". Change credentials that were exposed, meaning anything found in chat, email, or a shared document, and anything a departed person knew. Leave strong, unique, unexposed passwords alone. This matches the reasoning in our article on why rotating passwords on a schedule stopped being good advice: change on evidence, not on a calendar.
The second piece of advice worth questioning is storing TOTP codes in the same vault as the password. For low value shared tools it is convenient and fine. For the cloud console, the registrar, and the password manager admin account, keep the second factor separate, on a hardware key or a separate authenticator, so one compromised vault does not hand over both factors.
Offboarding with a password manager
When someone leaves, the order matters:
- Disable their password manager account first, so they cannot export anything new.
- Pull the access report for every vault they could read. Most team products show this in one screen.
- Rotate credentials in the infrastructure and finance vaults they had access to, starting with anything that grants admin rights.
- Remove their SSH public keys from servers. With key based login, that is one line per server in authorized_keys.
- Transfer ownership of any items they created so nothing becomes orphaned.
For a team of eight with a sensible vault layout, this takes about an hour. Without a password manager, the same job usually means guessing.
Frequently asked questions
Is a free password manager good enough for a small team?
Free tiers usually limit sharing to one other person or one collection, which breaks down at three or more people. They also tend to lack access reports and admin recovery. For a business, the paid tier at a few dollars per user is cheap insurance compared with one lost registrar account.
What happens if the password manager company is breached?
Reputable products encrypt vaults on your device with a key derived from your master password, so a server breach exposes encrypted data, not readable passwords. Your protection is a long, unique master password and two factor authentication on every account. If a breach is announced, change the master password and rotate the infrastructure vault first.
Should SSH keys and API tokens go in a password manager?
Yes, most team products store secure notes and files, which covers private key passphrases and API tokens. Keep machine secrets used by running applications in your deployment tooling or environment files instead, so production does not depend on someone's browser session. The vault is the human copy, not the runtime source.
More in Security
Security
DDoS Protection for a Small Server Without a Big Budget
The first time one of my game servers got knocked offline, I spent two hours convinced the host had a network fault.
Security
Locking Down Your Domain Registrar Account the Right Way
A founder wrote to me last spring because his company email had stopped arriving. Not bouncing, just silent.
Security
Leaked Secret in Git and How to Clean It Up the Right Way
You pushed a commit, looked at the diff a minute later, and saw an API key sitting in plain text in a config file.