Shared logins are a liability: moving your team off the one password everyone knows

There is one password. Everyone at the front desk knows it. It signs into the point-of-sale, the shared inbox, maybe the social accounts and the accounting software too. It has not changed in years, because changing it means telling six people the new one and fielding a day of “I got locked out” messages. This feels like the practical choice — one login, no fuss, everyone can cover for everyone else. It is also one of the quietest liabilities a small business carries.

Shared logins are convenient, and that is exactly why they spread. But a single account that several people use quietly removes the three things that make an account safe: knowing who did what, being able to cut off access cleanly, and containing the damage when the password leaks. Here is why that matters and how to move off it without stopping work for a week.

Why teams end up here

Nobody sets out to run their business on one shared password. It accumulates. A tool gets bought with one login because that was fastest. A second person needs access, so they get told the password instead of being given their own seat. Per-seat licensing makes individual accounts look like an added cost, so sharing feels thrifty. And on a small team where everyone trusts everyone, the risk feels abstract. So the sticky note stays under the keyboard, and the shared note keeps growing, and the arrangement calcifies until it is simply how things work.

The trust is real and it is not the problem. The problem is that a shared login does not fail because someone on your team is dishonest. It fails because of accidents, departures, and outsiders — and against all three, one shared password offers almost nothing.

The three things a shared login takes away

Accountability. When five people use the same account, the logs only ever show that account. If a customer record is deleted, a price is changed, a refund is issued, or a post goes out that should not have, there is no way to know who did it. That is not about assigning blame — it is about being able to answer a basic question when something goes wrong, and about the fact that people are simply more careful when their own name is attached to an action. A shared login is a room with the lights off.

Clean offboarding. Someone leaves — a seasonal hire, a contractor, an employee who parts on bad terms. With individual accounts, you disable one account and the door is shut in seconds. With a shared password, that person still knows the one secret that opens everything, and the only way to revoke their access is to change the password everywhere and redistribute it to everyone who remains. In practice that is painful enough that most businesses skip it, which means former staff keep working access to live systems for months. That is the single most common way a small business ends up with an account it cannot account for.

A contained blast radius. When the shared password leaks — reused on a site that got breached, phished off a fake login page, or simply seen over a shoulder — it does not expose one person’s access. It exposes everyone’s, everywhere that password is used, all at once. One secret becomes the master key to the whole business. Individual accounts with limited roles mean a single compromised login is a small fire, not the whole building.

Moving to individual accounts without the pain

You do not need to fix this in one heroic weekend. You need an inventory and a sensible order.

• List the shared logins first. Write down every account more than one person uses: the POS, the inboxes, the social accounts, the accounting and banking logins, the domain registrar, the online ordering back end. You cannot untangle what you have not named, and most teams are surprised by how long the list is.
• Give people their own accounts where the tool allows it. Most business software — Microsoft 365, Google Workspace, accounting platforms, most social tools — supports multiple named users. Create one per person. Yes, some charge per seat; the cost of a seat is small next to the cost of an account nobody can close.
• Assign roles, not blanket access. A new hire on the front desk does not need the ability to change banking details or delete customer history. Give each person the access their job needs and no more. Most platforms have built-in roles for exactly this.
• Put a password manager in the middle. A shared password manager — Bitwarden, 1Password, and similar — lets you store credentials centrally, share them with named people, and revoke that sharing the moment someone leaves, without anyone ever needing to know or type the actual password. It is the tool that makes the whole transition realistic.
• Turn on multi-factor authentication as you go. Every account you touch during this cleanup should get a second factor before you move on. Individual accounts plus MFA is the combination that actually holds.
• Write an offboarding checklist. The point of all this is a list you can run in ten minutes when someone leaves: disable these accounts, revoke this sharing, done. Keep it current.

The one system that only allows one login

You will hit a tool or two that genuinely supports only a single account — an older POS, a niche supplier portal, a legacy service. This is where the password manager earns its keep. Store that one credential in the manager and share it to the specific people who need it. They can use it without ever seeing or memorising it, and when one of them leaves you revoke their access to the vault entry rather than reprinting a sticky note. It is not as strong as individual accounts, but it restores the two things you most need: a record of who can reach it and a clean way to cut someone off.

Where this fits

Moving off shared logins is one of those changes that is obvious in hindsight and easy to keep postponing, because nothing is visibly broken until the day it is. Doing it well — individual accounts, sensible roles, a password manager, MFA, and an offboarding routine that actually gets run — is a large part of what a managed device practice handles as ordinary maintenance rather than a project you have to find time for.

If shared passwords are one of several do-it-yourself habits you have quietly outgrown, that is worth reading about in the signs you have outgrown do-it-yourself IT. And if you are weighing a provider to help with this, ask them directly how they handle joiners and leavers — it is one of the questions worth asking any managed IT provider.

Send us two paragraphs about how your team signs in today, and we will reply in writing within one business day.