When somebody suggests the company should adopt a password manager, an owner's first reaction is often this: there are only a handful of us, so why can we not just keep passwords in our own browsers or a spreadsheet? Why install another tool for that?
If you think of a password manager as a small convenience that saves staff some typing, then it does look optional. But for an owner, the problem this tool solves was never whether daily typing is slow. It is this: on the day somebody leaves or an outside vendor closes a project, can you quickly establish which company passwords they have seen, and take that access back in one move? This is the thirteenth piece in our security basics series. Following Security Basics 01|An advisory just landed: how do you know whether it affects you and the pieces on closing accounts at departure, the list of top-level access and two-step verification, this one looks at password managers from the angle of handover and getting control back.
With no central tool, where your company's passwords are sitting right now
Think back to the last time a new colleague started, or a marketing agency needed to set something up on a platform for you. How did the password actually reach them? On a team without a password manager, passwords drift to three places where nobody is in control:
- Into chat history: to save time, someone pastes the username and password straight into a group or a direct message. The trouble is that once a message has been sent, it stays sent. Long after that person has left, scrolling up the thread on their phone still shows the password sitting there.
- Into one shared spreadsheet or note: every platform's credentials end up on the same sheet. Anyone who can open that sheet can also see the finance and server passwords they have no business touching, and nobody can tell who copied it, or when, and took a version away.
- Into staff members' own browsers: everyone clicks "remember this password", and then after an important third-party service has its password changed, only the machine belonging to the colleague who changed it can get in. Even the copy the owner is holding is out of date.
Why official security guidance recommends handing passwords to a tool
Asking people to memorise many long, random and entirely different passwords is, in practice, a task set against human nature; and when a rule works against human nature, people quietly find the least troublesome shortcut, which is usually also the most dangerous one.
The UK's National Cyber Security Centre (NCSC) is explicit in its 10 Steps to Cyber Security: Identity and access management guidance: an organisation should reduce the number and complexity of passwords users have to remember as far as possible, by allowing the use of password managers or single sign-on, and so reduce insecure behaviour such as reusing the same password, picking easily guessed ones, or writing them down. Its 2026 update to the Small organisations guide to cyber security: Secure your email says the same thing directly: creating and remembering a different password for every important account is genuinely hard, so it recommends using a password manager to generate strong passwords, and to create and store passkeys centrally and securely.
Once a member of staff only has to remember the one master password that opens the tool, and every site's complex password is generated and filled in for them, nobody has a reason left to set every site to the same password, and nobody needs a sticky note on the edge of the monitor.
The biggest benefit for an owner: no searching when somebody leaves
Beyond generating strong passwords for staff, a business or team password manager gives an owner three things a spreadsheet cannot:
- Access granted per folder, so each person gets only the key they need: you can split passwords into separate safes, such as general administration, marketing and social, and technical infrastructure. Marketing colleagues see only the social safe and cannot reach the servers; an outside vendor sees only the items for one project, not everything the company owns.
- One switch on the day they leave, with the list already in front of you: when a member of staff leaves, you disable their password manager account and they immediately lose read access to every shared safe. Better still, the tool lists exactly which safes they belonged to, so your technical people can rotate the shared passwords in those safes and nothing else, instead of digging through years-old chat logs guessing which passwords they ever held.
- Handover documents kept safely apart from the passwords themselves: as we wrote in Don't Let Handover Become a Black Box: A Minimal Documentation Set to Leave Behind, when you write the page about who can sign in, "this page says only where to fetch the password; the password itself lives in the password manager". That way the handover document can sit in the company's shared space and be kept up to date without worry, while the real passwords stay locked in a tool with access control.
One table: how three ways of storing passwords differ on the day somebody leaves
Put the three everyday habits side by side on the day of a departure and the gap is obvious:
| How the password is stored | How colleagues get it day to day | What happens the day that colleague leaves |
| 1. Pasted into a chat group or direct message | Copy and paste on the spot, fastest and easiest | The history cannot be deleted, and nobody remembers which passwords were ever sent to them |
| 2. Written in a shared spreadsheet or document | Grant them access to the whole sheet | They could copy the entire sheet while employed; on departure every password on it has to be reset |
| 3. A team password manager | Grant the safe matching their role to their own personal account | Disabling their account cuts read access; passwords are rotated precisely, following the list of safes they were in |
Two simple principles you can start on today
Adopting a password manager does not have to become a large IT project. You can start with the two easiest principles:
- From today, no company password or key is ever posted in plain text in a chat: set that one rule and people will naturally start using the secure sharing feature of the password manager instead.
- Put the four top-level accounts and the emergency backup codes in first: you do not have to move every small site in the company across on day one. Lock the domain, the cloud server, the code repository, the website back office and the emergency backup codes for two-step verification into a safe shared by the owner and the technical lead, and you have already protected the part of the foundation that matters most.
Nerd Technic is a systems software company that came out of custom development, and what we do now is the long-term maintenance of AI systems. As we noted in Don't Let Handover Become a Black Box: A Minimal Documentation Set to Leave Behind, bringing accounts and passwords into somewhere the company controls is the groundwork that stops a system turning into a black box. What long-term maintenance has to look after is this: security updates run to a fixed rhythm, and when the engagement ends every document and record is left with you. If the passwords to your systems are currently scattered across a former engineer's mailbox and old chat groups, a system health check is a place to start: Book a system health check