Why Shared Logins Are a Security Risk Your Business Can Fix
Shared logins usually start with a small, practical decision. Someone needs access to a system, and forwarding the existing username and password seems like the quickest way to get the job done. The employee signs in, finishes the task, and gets back to work. From their point of view, it worked fine.
The problems tend to appear later. A payment instruction changes, a customer record disappears, or the account logs in from an unfamiliar location. You pull up the account history, and every action is recorded under the same username. Several current staff know the password, former employees may still remember it, and nobody can say with any confidence who was actually in the account.
This is an extremely common situation, and it creates four specific problems worth understanding before you decide how to deal with it.
You lose the ability to see who did what
When five people share one login, the software records all activity under that single account. You can usually see that the account signed in, edited a record, downloaded a report, or changed a payment detail. What you cannot see is which of the five people did it.
That gap matters even when nothing suspicious is happening - tracing a simple mistake takes longer when you have to ask several people what they were doing at the time. It becomes much more serious when the activity might be fraudulent. If someone exports customer data or changes bank account details, you need to know whether that was an employee, a former employee, or an attacker who got hold of the shared password. With a shared account, the audit trail often cannot tell you. This kind of accountability gap is exactly what a managed cybersecurity service is designed to help businesses close.
IT Stuffed ran a full systems cyber security audit for us, which was very eye-opening! They helped us implement the necessary changes and gave us some strategic advice on future steps. Daniel and the team are incredibly dedicated, great communicators and a real pleasure to deal with.
Ruby Williams
When faced with a cyber-attack a year ago we greatly appreciated the immediate and ongoing support we received from IT Stuffed. Happy to recommend this service.
Maggy Tai Rākena
Removing someone's access becomes a problem for everyone
When an employee with their own account leaves, your IT support can disable that account without affecting anyone else. A shared login works differently. The former employee still knows the password, so the only way to remove their access is to change it and distribute the new one to everyone who remains authorised. That creates another round of messages, saved passwords, and browser updates across the team.
Because of the inconvenience, businesses sometimes leave the password unchanged. The former employee's access then depends entirely on whether they still remember it or have it saved on a personal device.
The same issue applies to MFA - multi-factor authentication, the second verification step that asks for a code or approval after you enter a password. MFA is designed so that the second factor belongs to the person signing in. With a shared account, that falls apart quickly. The MFA prompt goes to one employee's phone while someone else is trying to sign in. Staff start forwarding codes to each other, or a shared device gets left in the office so anyone can approve a login. The security benefit is largely undermined.
Shared accounts give everyone the same access level
When several people use one login, each of them can do whatever that account is permitted to do. An employee who only needs to view customer records may also be able to export them. Someone who needs to publish a website update may also have access to billing, user accounts, or security settings.
Individual accounts let you match access to the person's actual role. Your bookkeeper gets the financial access they need without becoming an administrator. A marketing employee can update content without being able to change system settings. This principle - giving each person only the access their work requires - is one of the most effective ways to limit the damage if an account is compromised or misused. For a broader look at how this fits into reducing risk, ten practical steps that lower your exposure covers it alongside other controls worth having in place.
Administrator-level shared logins deserve particular attention. If several employees use the same administrator account for everyday tasks, a single stolen password or careless action can affect the whole business. Each administrator should have a named account wherever the system allows it, and administrator access should be used only when a task genuinely requires it.
A shared email address doesn't require a shared password
Several staff members may legitimately need to read and reply to messages sent to an address like accounts@yourbusiness.com or support@yourbusiness.com. That doesn't mean they all need to sign in with the same password.
Microsoft 365 shared mailboxes, for example, allow each authorised employee to open the common mailbox through their own account. Microsoft recommends keeping direct sign-in blocked for the mailbox account itself - each person signs in as themselves, and an administrator grants them access to the shared mailbox. When someone leaves, that permission can be removed without changing anything for the rest of the team. Most other business platforms offer something similar, whether it's called delegation, team access, user roles, or shared inboxes. It's worth checking whether your software already supports this before passing around a password.
When shared access genuinely cannot be avoided
Some older applications and devices only support a single account. If you cannot replace or reconfigure them immediately, the shared password should live in a business password manager rather than in an email thread, a shared document, or someone's browser. Access should be restricted to the smallest group that actually needs it, and the password should be changed whenever someone moves on or changes roles.
A business password manager still requires each employee to sign in with their own account and MFA before they can retrieve any stored credential. Some also log when a user views or copies a password, which at least gives you a partial audit trail. It is a better arrangement than an unmanaged shared password, even if individual accounts remain the right goal.
Assign a named owner to every shared account that cannot be eliminated. That person should know who has access, what the account controls, where the recovery details are stored, and what would break if the password changed unexpectedly.
Starting the review
Most businesses that have been operating for a few years have more shared accounts than they realise. Accounting software, customer management systems, social media tools, website administration, cloud storage, and specialist applications are all common places to find them. Old email threads and internal spreadsheets can reveal accounts that were set up and largely forgotten.
Once you have a list, the question for each account is straightforward: does the software support individual users, delegated access, or a shared mailbox? If it does, set those up and migrate people across before removing the shared login. If it doesn't, move the password into a business password manager and document who is authorised to use it.
Make the same check part of your process when someone joins, changes roles, or leaves. Shared accounts tend to come back when a new employee needs access quickly and nobody knows the right way to provide it.
For businesses handling patient information, legal records, or financial data, the accountability gap created by shared logins is also a privacy compliance consideration under the NZ Privacy Act 2020. If a breach occurs and you cannot show who accessed what and when, that is a problem beyond the IT layer.
If you're not sure where your business currently stands with this, ITstuffed can review your environment and help you work out the safest way to give staff access. Book a 15-minute IT Fit Check to get started.
