Why Shared Logins Put Your Small Business at Risk

Free Black and white image showcasing a door lock with a key inserted, casting shadows. Stock Photo

Most shared logins start with a reasonable shortcut. A new hire needs into the accounting system today, so a coworker sends over the password everyone uses. The task gets done, and nobody thinks about it again.

Months later, a payment detail changes or a customer record disappears. You open the activity log, and every action shows the same username. A handful of current staff know the password, a few former ones might too, and nobody can say who did what.

How small businesses end up with shared logins

Nobody plans a pile of shared accounts. Usually, the software was bought when the company had two people, and one login got passed along as the team grew.

In other cases, the software does not support more users, extra seats cost more, or nobody had time to set them up. Shared inboxes such as sales@ or accounts@ are another common source, because staff simply sign in to the address itself.

The setup may run fine for years. Even so, working is not the same as safe.

You cannot see who did what

When five people share one login, the software logs every action under that one account.

You might see that the account changed a bank detail or pulled a report. However, you cannot tell which of the five people did it.

That slows down even honest mistakes, since you have to ask everyone what they were doing. It matters far more when the change could be fraud. Then you need to know whether it came from a current employee, a former one, or an attacker.

For exactly this reason, the UK’s National Cyber Security Centre advises giving each employee a separate work account.

One password, many copies

A shared password has to reach everyone who uses it. As a result, it ends up in emails, chat threads, shared files, and browsers on several computers. Each copy is one more place to steal it from.

More people also means more chances for a slip. One person types it on an infected laptop. Another saves it in a personal browser. A third reuses it somewhere else.

Once an attacker has it, they get the same access as everyone else. Worse, a strange login may be brushed off as someone on the team working from home.

Named accounts make odd activity much easier to spot. With a shared account, by contrast, locking the login to look into a problem can also lock out your whole team.

Offboarding gets messy

With individual accounts, your IT provider turns off one person’s login when they leave. Nobody else notices.

With a shared login, the person who left still knows the password. So the only fix is to change it and hand the new one to everyone who stays. That means another round of messages and saved passwords, and it may break any app or device that uses the login.

Because that is a hassle, many businesses simply skip it. In that case, a former employee’s access depends on whether they remember the password.

MFA works best when it belongs to one person

Multifactor authentication (MFA) asks for a second proof after the password, such as an app code, a security key, or a phone prompt. The idea is that only the account holder has that second factor.

Shared accounts break that idea. The prompt goes to one person’s phone while someone else is trying to sign in. Soon, people are forwarding codes or approving prompts for each other, which defeats the purpose.

Some services allow several passkeys or security keys on one account, which helps. Still, separate accounts are simpler, because you can remove one person without touching anyone else.

Everyone gets the same access

On a shared login, every user gets every right that account has. So someone who only needs to view customer records can also export them. Similarly, someone who updates the website may also reach billing and security settings.

Separate accounts let you fit access to each role. Your bookkeeper gets the money side without admin rights, and your marketer can post content without changing system settings. This is called least privilege: each person gets what their role needs and nothing more.

A shared inbox does not need a shared password

Several people may need to answer accounts@ or support@. That does not mean they all need the same password.

In Microsoft 365, for example, each person opens a shared mailbox through their own account. Microsoft recommends keeping direct sign-in to the shared mailbox blocked. When someone leaves, you remove their access and everyone else carries on.

Most business platforms offer something similar, called delegation, roles, groups, or team access. Before you share a password, check whether one of these options already exists.

Keep admin logins out of circulation

Shared admin logins need extra care. They can change security settings, add users, and remove other people’s access, so one mistake or one stolen password reaches much further.

Give each admin their own named admin account. Staff should do everyday work in a standard account and switch to admin access only when a task needs it.

It is also worth asking your IT provider who holds admin rights today. People often keep rights from old roles because nobody took them away.

When the software only allows one login

Some older systems and devices just do not support separate users, and replacing them takes time. In the meantime, lower the risk:

  • Store the password in a business password manager, not in email or chat.
  • Limit access to the people who truly need it, and review the list when roles change.
  • Have each person sign in to the password manager with their own account and MFA.
  • Change the password whenever someone leaves the approved group.
  • Name an owner who knows who has access, what the account controls, and where its recovery details live.

The NCSC recommends shared access through each person’s own login over passing a password around, and gives the same advice for the cases where sharing cannot be avoided.

If you cannot name who used a login, you cannot tell a mistake from an attack.

Service accounts are a different case

Your IT provider may mention service accounts. These are logins used by software or automated tasks, not by people. For instance, a backup tool may use one to reach a server.

A well-run service account is not the same as a password your staff pass around. It should have only the rights its job needs, a named owner, a written purpose, and a plan for replacing its password if it leaks. Ask your IT provider to identify these before anyone turns them off, since other systems may depend on them.

How to replace shared logins without slowing your team down

  1. List every shared account. Check accounting, customer, social media, website, email, cloud storage, and specialty apps. Old spreadsheets and saved browser passwords often turn up forgotten ones.
  2. Note who uses each one and why. That tells you whether you need individual users, delegation, a shared mailbox, or something else.
  3. Start with the riskiest. Tackle admin accounts first, then anything holding customer, employee, or financial data.
  4. Create named accounts with the right access. Give each person MFA, and confirm the new login works before you retire the old one.
  5. Move any leftover shared passwords into a business password manager, with an owner and a short access list.
  6. Build it into onboarding and offboarding, so shared logins do not creep back in.

A business password manager makes all of this far easier. We set up and manage Bitwarden for small teams, and an access review is part of Business Security Essentials.

Frequently asked questions

Are shared logins ever acceptable?

Sometimes a device or older app only supports one account. Until you can replace it, keep the access list small, store the password in a password manager, watch how it is used, and change it whenever access changes.

Can we share a login if MFA is turned on?

MFA lowers the risk of a stolen password, but several people still share one identity. You still cannot tell who did what, so use separate accounts where you can.

Are shared email addresses unsafe?

The address is not the problem. The shared password is. Let staff open the shared inbox through their own accounts instead.

Do we have to replace every shared login at once?

No. Start with admin accounts and anything holding sensitive data, then work through the rest.

What do we do when someone leaves the company?

Turn off their accounts and remove any shared mailbox access. Then change any shared passwords they knew, and check for devices, sessions, or recovery options they may have added.

Free Coffee Break

Ready to retire the shared passwords?

Book a free Coffee Break, and we will help you map your shared logins and plan the switch, one account at a time.

Book your free Coffee Break →

Related articles

You may also be interested in

Cookie policy
We use our own and third party cookies to allow us to understand how the site is used and to support our marketing campaigns.

Headline

Never Miss A Story

Get our Weekly recap with the latest news, articles and resources.

Headline

Never Miss A Story

Get our Weekly recap with the latest news, articles and resources.
Cookie policy
We use our own and third party cookies to allow us to understand how the site is used and to support our marketing campaigns.

Hot daily news right into your inbox.