A shared login can look like the sensible option when three people need to use the same production computer before the next shift starts. It avoids delays and may be the only way an older machine or specialist application has ever worked. But are shared logins secure? Usually, no. They remove accountability, make it harder to control access and can turn one leaked password into a wider production problem.
For a manufacturing or engineering business, this is not just an IT housekeeping issue. A shared account may give access to ERP or MRP data, CAD drawings, machine settings, customer specifications or a supplier portal. If something is changed, deleted or accessed improperly, you may have no reliable way to establish who did it. That creates security, operational and customer assurance concerns at the same time.
Why shared logins create a business risk
The main problem is simple: a login identifies an account, not a person. When several people know the same password, the audit trail stops being useful. An entry showing that “Workshop” or “ProductionAdmin” made a change tells you almost nothing.
This matters when a batch record is amended, a CAD file is downloaded, a machine parameter changes or a purchase order is approved unexpectedly. Your team may be acting entirely in good faith, but it becomes much harder to investigate an error or prove what happened to a customer, insurer or auditor.
Shared passwords also tend to travel. They are written on a label, sent in a message, saved in a browser, passed to an agency worker or retained by someone who has left. Changing the password after every staffing change is possible, but rarely happens consistently when production is under pressure.
The security impact can be larger than expected. If the same password is reused across a workstation, Microsoft 365 account, remote-access service or supplier system, one compromised credential can give an attacker several routes into the business. Ransomware groups do not need dramatic Hollywood-style hacking when a valid password will do.
Are shared logins ever acceptable?
There are limited cases where a shared login may be unavoidable in the short term. Older machinery-connected computers sometimes support only one local account. A specialist CAM package may be licenced to a named workstation rather than designed for individual user access. On a busy shop floor, staff may rotate between a small number of terminals.
That does not make the arrangement secure. It means the risk needs to be understood, reduced and documented while you work towards a better option. Treat it as a controlled exception, not as the default way of operating.
A shared account can be less risky where it has no access to email, cloud storage, financial systems, customer data or the wider network. A restricted local account on a segregated machine is very different from a shared administrator account used across several systems. Context matters.
The worst arrangement is a single shared account with administrative rights, internet access and a password known by current staff, former staff and at least one external supplier. That is not a login policy. It is an invitation for an expensive Monday morning.
The operational cost of poor accountability
Security conversations can become overly focused on passwords. The bigger question is whether your business can keep operating when something goes wrong.
Imagine a hypothetical example: an engineering firm finds that a machining programme has been overwritten on a shared terminal. The team restores an earlier version, but cannot tell whether the change was accidental, whether an external engineer was involved, or whether other programmes were affected. Production pauses while files are checked. The immediate cost is lost time. The wider cost is uncertainty, missed scheduling and a management team pulled away from more useful work.
Individual user accounts help contain that uncertainty. They allow access to be removed quickly when someone changes role or leaves. They show who accessed a system. They also make it easier to give people only the permissions they need, rather than handing every user the keys to everything.
This principle is often called least privilege. In plain terms, it means a warehouse colleague should not need the same access as the finance director, and an external machine supplier should not have permanent access to your network just because they might need it one day.
Better alternatives to shared accounts
The best replacement depends on the application and the working environment. For systems that support it, give each user their own account and use role-based permissions. A production operative might access job instructions and record completion, while a supervisor can amend schedules and an administrator can manage settings.
On shared Windows devices, separate accounts can still be practical. Staff can sign in at the start of a shift, or use a fast sign-in method where the equipment supports it. The extra few seconds are usually less disruptive than investigating an unexplained change later.
For shared credentials that genuinely must exist, use a business password manager with controlled access, rather than a spreadsheet or a note in a drawer. The password can be changed without manually telling every person, and access can be withdrawn when it is no longer needed. It does not remove all risk, but it is a clear improvement.
Where a legacy production computer only supports one local login, focus on containment. Remove unnecessary administrator rights, restrict internet access, block access to business systems it does not need, keep it on a segregated network and maintain tested backups of its configuration and critical files. If patching is not possible because the software is unsupported, compensating controls become even more important.
Remote supplier access needs the same care. Use an approved remote-access method, require multi-factor authentication where possible, limit access to specific systems and make it time-bound. Permanent remote access is convenient until it becomes somebody else’s route into your network.
A practical way to reduce shared-login risk
Start by finding the accounts you already share. This is often more revealing than expected. Ask department heads about production PCs, warehouse terminals, engineering workstations, supplier portals, email inboxes, cloud applications, routers, Wi-Fi and remote-support tools. Include accounts used only “once in a while”. Those are frequently the ones nobody owns.
Then record what each account can access, who knows the password, whether it has administrator rights and whether multi-factor authentication is available. Identify the accounts that could stop production, expose designs or allow access to financial and customer information.
Prioritise the highest-risk cases rather than trying to fix everything in a week. A sensible order is:
- shared administrator accounts and remote-access accounts
- accounts connected to Microsoft 365, finance or customer information
- ERP, MRP, CAD, CAM and production-control accounts
- legacy or machinery-connected computers with wider network access
- lower-risk shared devices with restricted local access
For each account, decide whether to replace it with named user access, restrict it, place it in a password manager or formally accept it as a temporary exception with a remediation plan. Assign an owner and a review date. Without both, exceptions have a habit of becoming permanent.
Shared logins and customer security requirements
Many larger customers now ask suppliers how they control access to systems and protect sensitive information. A shared-login arrangement can raise awkward questions because it weakens identity management and auditability.
Good practice such as named accounts, multi-factor authentication, controlled administrator access and prompt removal of leavers supports a stronger security position. It may also help when preparing for Cyber Essentials or responding to cyber insurance and supply-chain questionnaires. However, do not assume that replacing one shared password automatically meets every requirement. Your wider configuration, device management, patching, access controls and evidence all matter.
The aim is not to force office-style processes onto a working factory floor. It is to design access controls that fit how people actually work while protecting production and intellectual property. That may mean a managed shared terminal, quick individual sign-in, clear shift handovers and a tightly restricted legacy machine rather than a one-size-fits-all rule.
If shared accounts have built up around your workshop, warehouse or office systems, start with a short access review before an incident forces the issue. Syn-Star can help you map critical accounts, protect legacy equipment and create an access plan that improves security without putting unnecessary friction into production.
