IT Glossary
Shared accounts are logins used by several people. Why they break accountability, offboarding and MFA, when they are acceptable and how to replace them.
November 2, 2026
Shared accounts are logins that several people use with the same username and password, instead of each person signing in with a named account. Typical examples are a company social media profile, a supplier portal, an admin@ mailbox or a single SaaS seat bought for a whole team. They save setup time, but they erase the link between an action and the person who performed it.
Some cases are legitimate: a social media platform that allows only one login, a vendor portal that issues a single customer account, or an emergency account kept for break-glass situations. ISO/IEC 27002:2022 guidance for control 5.16, Identity management, says shared identities should only be permitted where necessary for business or operational reasons, with dedicated approval and documentation. In practice, that means a named owner, a recorded reason and a way to tell who used the account, such as the check-out log of a vault.
There is also a licensing angle. When a SaaS license is sold per named user, sharing one seat across a team can breach the vendor's terms, and the saving is lost the day the vendor enforces them.
A 150-person e-commerce company has, for example, five people posting from one social media account, a carrier portal with a single login used by the logistics team, and one seat of a design tool shared by three freelancers. When a logistics coordinator leaves, nobody changes the carrier portal password. Weeks later an order is canceled from that account, and nobody can tell who did it.
The fix is made account by account: the design tool moves to named seats behind SSO, social posting goes through a tool with individual logins, and the carrier password goes into a vault with check-out. Corma supports the named-account side: its inventory of accounts per application lists generic logins next to named users, self-service access requests with approval workflows give each person their own access, and access reviews keep audit evidence for the exceptions that remain.
Yes, in most cases. They remove individual accountability, complicate offboarding and weaken MFA, so they should be limited to documented exceptions with an owner.
It depends on the contract. When a license is sold per named user, sharing one seat across several people can breach the vendor's terms.
A shared account is used by several people. A service account is used by a program or an integration, not by a person, and should not be used for interactive sign-ins.
Give it an owner, store its password in a vault with check-out and logging, rotate the password when someone leaves, and document the approval and the business reason.