Skip to main content
sharing passwords
Cybersecurity

Sharing Passwords at Work: Why Shared Logins Put Your Business at Risk

The bookkeeper is out sick. An invoice has to go out today. So somebody texts the QuickBooks login to the office manager, the invoice goes out, and everybody moves on. Nobody thinks of it as sharing passwords. It was just getting the job done.

A year later, five people know that password. Two of them no longer work there. It is saved in three browsers and one old text thread. And when a customer’s bank details get changed and nobody remembers doing it, the history just shows the same username every time.

That is how it nearly always goes. Let me walk through why sharing passwords at work causes more trouble than it seems to, the five risks that build up quietly, and how to give people access without passing the password around.

Sharing passwords usually starts with one reasonable favor

Nobody sets out to build a business on shared logins. It happens one shortcut at a time.

The software was bought when the company had two people, so one login was plenty. The team grew, and handing over the existing password was faster than adding users. Sometimes extra users cost more. Sometimes the software can do it and nobody ever set it up. And very often several people need the same inbox, like accounts@ or info@, so everyone just signs into it directly.

The username might be admin, or office@, or the name of someone who left in 2019. The password lives on a sticky note, in a shared spreadsheet, or in a text from three years ago.

It works. That is the trouble. Sharing passwords can work fine for years, right up until the day something goes wrong and you need to know who did what.

5 hidden risks of sharing passwords at work

1. Nobody can say who did what

When five people use one login, the software records everything under that one name. You can see that the account changed a record, downloaded a report, or updated a payment. You cannot see which of the five people did it.

That is annoying for honest mistakes, because tracking one down means asking everybody what they were doing last Tuesday. It is serious when something looks like fraud. If bank details change on a vendor record, you need to know whether it was an employee, a former employee, or a stranger who got hold of the password. Sharing passwords takes that answer away.

The UK’s National Cyber Security Centre recommends giving every employee their own work account for exactly this reason, in its guidance on creating separate user accounts.

2. One password, everybody’s access

Sharing passwords means the password has to reach everyone who needs it. So it gets emailed, texted, typed into a group chat, written in a document, and saved on a bunch of different computers. Every copy is one more place for it to leak.

Office team gathered around one laptop

One person types it on a home computer with something nasty on it. Another saves it in a personal browser. A third uses it on some other website. If any of those leak, the attacker gets the same access everybody has.

And here is the part nobody thinks about. When an unfamiliar sign-in shows up on a shared account, people assume it is just a coworker on a new phone. On a personal account, a strange sign-in stands out. On a shared one, it blends right in.

3. Someone leaves, and the password stays with them

When a person with their own account leaves, you turn off their account and you are done. Nobody else is affected.

When you are sharing passwords, the person who left still knows them. The only way to cut them off is to change those passwords and give the new ones to everyone who is staying. That is another round of texts and saved passwords, and if some device or program uses that login, changing it can break that too.

So the honest truth is that a lot of businesses just do not change it. The former employee’s access then depends on whether they remember it. Australia’s cyber agency says shared credentials should change whenever the group using them changes, in its guidelines for system access. That is hard to keep up with when sharing passwords is the only system you have. We cover the rest of the exit checklist in our post on employee offboarding.

4. Multi-factor sign-in stops making sense

Multi-factor sign-in is the code or phone approval you get after typing your password. It is meant to prove the person signing in is the person who owns the account. The National Cyber Security Centre describes it as something only the account holder can access, in its guidance on passwords and shared access.

When a team is sharing passwords, the code goes to one person’s phone no matter who is signing in. So people start texting codes to each other, approving prompts for each other, or leaving a “login phone” in a drawer at the office. At that point the extra protection is mostly theater.

5. Everyone gets the most powerful permissions

When people are sharing passwords, every one of them gets whatever that login can do. Someone who only needs to look up a customer can also export the whole customer list. Someone who updates the website can also change the billing and security settings.

Individual accounts let you match access to the job. The bookkeeper gets the money side without being able to change every setting. Security folks call this least privilege, which just means everybody gets what their job needs and nothing extra. Australia’s cyber agency recommends it, along with regular access reviews, in its advice on securing user accounts.

A shared inbox does not need a shared password

This is the fix that surprises the most people. Several of your employees probably need to read and answer email sent to info@ or accounts@. They do not all need to sign into it with the same password.

In Microsoft 365 that address can be set up as a shared mailbox. Each person opens it from their own Outlook with their own login, and an administrator decides who can see it. When someone leaves, you take away their access and nobody else notices a thing. Microsoft actually recommends blocking direct sign-in to a shared mailbox, in its page about shared mailboxes.

The thing you did not ask about, but should know: a shared mailbox normally does not need its own paid license. We recommend these to every client, and it is one of the cheapest ways to stop sharing passwords on the account that matters most. Other software calls the same idea team access, delegation, user roles, or groups. Check for it before you hand out a login.

Admin passwords are a different level of risk

An administrator login can create users, change security settings, and lock other people out. Sharing passwords is at its worst here. If three people share the admin password and use it for everyday work, one mistake or one stolen password affects the whole business.

Each person who truly needs admin rights should have their own named admin account, and use a regular account for normal work. It is also worth a look at who has admin access right now. People keep access from old roles because nobody took it away when their job changed.

When the software really only has one login

Some older programs and devices genuinely cannot do separate users. Replacing them can take time, especially if the whole business runs on them. So here is the honest answer for those: you will keep sharing passwords there for a while, and the goal is to do it carefully.

Put that password in a business password manager instead of texts and spreadsheets. Each employee signs into the password manager with their own account and multi-factor sign-in, so you control who can pull up the shared login. Many business password managers also record who used it and when. Keep the list short, review it when people change roles, and change the password whenever someone leaves the group.

Give every remaining shared account an owner. That person knows who has it, what it controls, and what breaks if it changes. If you are picking a password manager, our post on password manager security covers what to look for.

Accounts for machines, not people

Your IT provider may mention service accounts. These are logins used by software or devices, not employees. A backup program uses one to reach a server. Two business systems use one to pass information back and forth.

Name badges laid out on a desk

A properly run service account is not the same as sharing passwords. It should only be able to do its one job, employees should not know its password, and somebody should own it and know how to replace the password if it leaks. Ask your IT provider to label these, so nobody turns one off during a cleanup and breaks the backups.

How to stop sharing passwords without stopping work

You do not have to fix everything at once. Start with the accounts that can do the most damage: anything with admin rights, money, or customer and employee information.

Make a list of every account people log into. Accounting software, the bank portal, your customer system, the website, social media, shared inboxes, and any industry software your team uses. Old texts and spreadsheets will turn up a few you forgot. Our post on finding forgotten accounts helps with that part.

Next to each one, write who uses it and why. That tells you whether it needs separate users, a shared mailbox, or a password manager. Set up the new logins with multi-factor sign-in, test them, and only then retire the old shared one.

Then make it part of how you bring people on and send them off. Sharing passwords creeps back in the day a new hire needs access fast and nobody knows the right way to give it. Building that habit into everyone is part of our security awareness training.

Frequently asked questions

Is sharing passwords at work ever okay? Sometimes software only allows one login. Until you can replace it, keep that password in a business password manager, limit it to the fewest people possible, and change it whenever someone leaves.

Can we keep sharing passwords on an account with multi-factor sign-in? It helps against stolen passwords, but you still cannot tell who did what. Use separate accounts whenever the software allows it.

Is a shared email address like info@ a problem? The address is fine. Everyone signing into it with one password is the problem. Set it up as a shared mailbox so each person uses their own login.

Do we have to stop sharing passwords everywhere at once? No. Start with admin accounts and anything holding money, customer, or employee information, then work through the rest.

What should we do about shared passwords when someone leaves? Turn off their own accounts, remove their access to shared ones, and change any password they knew. Check those accounts for devices or recovery details still tied to that person.

If your office has a few passwords that get passed around, you are in good company. Our 7 cyber mistakes cheat sheet covers sharing passwords and the other habits that quietly put small businesses at risk, and we are always glad to talk through what would work for your team.

Featured image: Pexels

Leave a Reply

Ready for a Stronger, More Secure Business?

Let's talk about your goals and how ParJenn Technologies can help.