A team password manager is the single most impactful security improvement most SMEs can make. It addresses credential reuse (the primary cause of credential stuffing attacks), removes plaintext passwords from spreadsheets and emails, provides an off-boarding mechanism for leavers, and gives IT a centralised view of credential health. The implementation cost is low and the security benefit is high.
Choosing a Business Password Manager
Most SMEs end up comparing Bitwarden, 1Password, Dashlane and Keeper. The feature sheets are long, but four questions settle most of the decision.
- Can you enforce MFA for every user from the admin console? If protection depends on each person switching it on themselves, it is not enforced.
- Does it support SSO and provisioning? Directory sync means a leaver loses access when their account is disabled, not when someone remembers to remove them.
- Can you see an audit log? You need to know who viewed or copied which credential, and how long the log is retained.
- What happens when the service is unavailable? Offline access and emergency recovery matter more than a polished interface on the day something breaks.
Do not repurpose a free personal tier for work. Those plans usually lack admin visibility, shared collection controls and central revocation, which is precisely where incidents happen. Self-hosting, which Bitwarden offers, suits firms with strict data residency rules, but it moves patching and backup onto you. Without a dedicated administrator, a managed business tier is the safer trade.
Step-by-Step Team Deployment
- Choose and create an organisation account (Bitwarden Business or 1Password Teams recommended for most SMEs)
- Create shared collections, group credentials by category: "Email systems", "Cloud services", "Social media", "Finance", "Admin accounts". Assign access by role, not individually, where possible.
- Import existing credentials, export from browsers (Chrome, Edge), any spreadsheets, or LastPass if migrating. Clean up duplicates and weak passwords during import.
- Invite staff via email. Enforce MFA on the manager itself, this is critical; a compromised password manager account is a single point of failure.
- Create and enforce a usage policy, all new work credentials must be generated by the manager; no work credentials in personal password managers; use the manager's sharing feature for all shared credentials.
- Test the off-boarding process before you need it, simulate a leaver, revoke access, and verify shared credentials are still accessible to remaining team members.
Admin Settings to Change Before You Invite Anyone
Configure the account before the first invitation is accepted. Retrofitting policy across a live team is slower and noisier than setting it once.
- Enforce MFA. This is the control that protects everything else, including the vault itself.
- Set master password requirements and a session timeout. Twelve hours suits most office teams; a shared terminal should lock far sooner.
- Enable emergency access for at least two people. Otherwise one forgotten master password can lock the business out of its own credentials.
- Decide whether personal vaults are allowed. If they are, state that work credentials must still live in shared collections where they can be recovered.
- Connect SSO and provisioning if you already run an identity provider. Deprovisioning is the most valuable automation the tool offers.
- Check audit log retention against your own policy. If an insurer or assessor expects twelve months, confirm the plan includes it.
Access Controls by Role
Not all staff need access to all credentials. A typical SME access structure:
| Role | Access |
|---|---|
| IT Administrator | All collections + admin console access |
| Finance team | Finance collection + general company collection |
| Marketing/social | Social media collection + general collection |
| General staff | General company collection only |
| Contractors | Specific collection only, time-limited access |
Design Shared Collections Around Jobs, Not Departments
One collection per department ages badly. Finance ends up holding the payroll provider, the bank portal and the marketing analytics login because nobody knew where else to put them.
Group by what the credential does instead:
- Money movement: banking, payroll, payment gateways
- Identity and email: domain registrar, DNS, Google Workspace or Microsoft 365 admin
- Customer data: CRM, support desk, analytics
- Publishing: website administration, social accounts
- Infrastructure: hosting, backups, monitoring
Then grant by role. An IT administrator needs everything, a marketing coordinator needs publishing and perhaps analytics, and nobody outside finance needs money movement. Contractors get a time-limited collection and nothing else.
Two rules prevent most of the mess: never share a credential by email or chat when a collection will do, and never let a collection grow without an owner. Assign a named owner to each one and review the list quarterly.
Rollout in Three Stages
A single all-staff launch produces a spike of locked-out users and a quiet return to old habits. Staging it costs a fortnight and avoids both.
Week one, pilot. Pick five to eight people across departments, including the most sceptical. Import their credentials, enforce the policy and let them break things. Fix what they find before anyone else meets the tool.
Weeks two to four, one team at a time. Move a single department, with a named person in that team who can answer questions. Enable self-service recovery first, so a forgotten master password does not become an IT ticket every morning.
Week five onwards, enforcement. Turn off browser password saving on managed devices, retire any spreadsheet holding credentials, and require the manager for every new work credential. Enforcement before the earlier stages is what makes people resent the tool.
What Goes Wrong
The failures are predictable, and most of them are organisational rather than technical.
- Nobody owns it. Without a named owner the vault drifts until it is a stale copy of last year's passwords.
- Shared credentials stay shared. If three people still know the admin password by heart, the risk has been documented rather than removed.
- The leaver process is untested. Deprovisioning works right up until the first resignation, when someone discovers the departing employee owned the only collection. Test it with our employee offboarding guide before that happens.
- Recovery was never configured. No emergency access, no offline recovery codes, and the master password lives in one person's head.
- Enforcement lands too early. Switching policy on before training produces workarounds, usually a personal vault holding the team's real passwords.
Measuring Whether It Worked
Three numbers from the admin console tell you whether the rollout is real.
- Users with MFA enabled. Below 100% means the policy is not being enforced.
- Credentials in shared collections versus personal vaults. A healthy team keeps work credentials in collections.
- Time from a leaver's last day to access revocation. If you cannot answer this without checking, the process is still manual.