Five blank employee ID badges on separate lanyards laid side by side on a dealership parts counter
Resources / Blog

Shared Logins at the Dealership: Why Every User Needs Their Own Account

By Rex MarchantNovember 20, 2026 · 11 min read

Shared logins are single accounts that several people at a dealership sign in with, such as one workstation login, one department inbox password or one vendor account. They hide who did what, which is why every user should have an account of their own.

Last updated: November 20, 2026

Say someone calls our help desk from the parts counter. The counter’s shared login is locked, and they need it back before the next customer walks up. Fair enough. We’ll verify who they are first, the same as every caller. That part works. Then it stops. What we can’t tell is who else signs in with that login, or which of them did what on it. The account doesn’t belong to anyone. It belongs to the counter.

I’ve spent more than 25 years leading managed services teams. I think every support and security process starts with knowing which person is behind an account. A shared login takes that away. Nothing downstream puts it back.

Our managed IT for dealerships team supports more than 35,000 dealership employees. When we talked this topic through on a content call this month, the team’s position was short. Everybody needs their own login. PCs, applications and email, all of it.

Two parts counter employees at a car dealership at shift change, each wearing their own blank ID badge

What Is a Shared Login, and What Forms Does It Take?

A shared login is one username and password used by more than one person. Nobody owns it. Everybody uses it. And because the password has to be known by everyone who signs in with it, every one of those people can pass it on to someone else, and the sign-in log would still show only the account.

Forms it can take:

  • A workstation sign-in that several people use as they step up to the same PC during a shift.
  • A department mailbox, like a service or sales inbox, that people sign in to directly with its own password.
  • One login to a business application, shared by everyone in the department.
  • A remote access account several people connect with.
  • An outside vendor’s credentials, used by the vendor’s whole staff. We’ve seen this one firsthand, and it’s below.

None of these feel dangerous when they’re set up. They feel convenient. That’s the appeal.

What Does a Shared Login Hide?

A shared login hides which person signed in, which person changed something and which people still know the password. Sign-in logs and per-user reports record the account, not the person behind it, so when several people share one account, they point at the account and stop there.

Take Microsoft 365. Microsoft says its sign-in logs record “the identity (User) performing the sign-in.” When five people use one account, that line names the account. Which of the five? It can’t say. NIST’s SP 800-53 security controls make the same point from the other direction, telling organizations to “uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.”

Managers feel it first. Our team put it in their terms on that call: shared logins hurt the auditing managers rely on, along with the per-person statistics that come out of those systems. If five people work under one name, the report shows one very busy person. That’s not a measure.

The help desk is a different story. I want to be precise here. Since November 17, 2023, we’ve verified the identity of every person who calls our help desk for support. The preferred check is a one-time code sent to the email address or mobile number already on that person’s contact record, never to details the caller gives on the call. So we verify the person, whatever login they’re using, but what verification can’t do is tell us who else has been using the account they’re calling about, or what any of those other people did while they were signed in. A password reset on a shared account also changes it for everyone who uses it, and the new password then has to be passed around again. Our help desk caller verification post walks through the full method.

The questionEach person has an accountSeveral people share one
Who signed inThe sign-in log names the personThe sign-in log names the account
Who changed a setting or a recordThe account name answers itAnyone who knew the password
Who still has access after someone leavesDisable one accountEveryone who knew the password, until it’s changed
Who approved the multifactor promptThe person signing in, on their own phone or appWhoever holds the phone or app registered to the account
Per-person reports for managersAccurateSeveral people’s work under one name

Each row is a question someone eventually needs answered. A shared login answers none of them.

Help desk technician with a headset taking a support call and writing notes on a paper pad

The Vendor Who Shared One Login

Several years ago, a vendor approved to help a dealership’s corporate office with an accounting function let several of its own employees use one login to reach the dealership’s environment. The dealership knew the vendor’s main contact. It didn’t know who the others were. Neither did we, until something stopped working and they needed support.

Two of them called our help desk posing as dealership employees. Both were refused. Neither got access. Neither got support. Our team told the dealership and handed over the call recordings, and the dealership made its own decision. It replaced the vendor.

I want to be clear about what went wrong, because it wasn’t the work. The work was legitimate. How it was being done wasn’t. One shared login let people the dealership didn’t know reach its systems, and neither the dealership nor our team knew who they were until one of them needed help and called. Credit goes to our service desk. They refused both callers.

A known name in front. Unknown people behind it.

Dealership controller meeting an outside accounting vendor across a desk with a closed folder between them

Why Do Dealerships Share Logins in the First Place?

When our team talked this through, two reasons came up, and the first is the workstation several people use, where nobody wants to sign in and sign out every single time they step up to it between customers. The other is cost, since one account is cheaper than a license for every person who touches the system.

Both are real. I get it. Neither is a reason to keep the shared account. I think the better question is the one I ask about any workaround: are we fixing the cause, or are we working around the symptom? The cause at the counter is the time it takes to sign in and out between customers, and the cause on the budget is the license count, so a shared login works around both of them and fixes neither one.

There’s a habit underneath this that I see across technology. People expect speed, and the speed they expect isn’t realistic if doing things correctly and securely matters. The quickest setup on day one isn’t always the one that holds up when an employee leaves or a vendor’s people change. Doing it right takes longer. It’s worth it. I mean that.

Quick fix versus lasting solution. The shared login is the quick fix.

What Happens When Someone With the Shared Password Leaves?

When someone with their own account leaves, you disable that account. Done. Nobody else is affected. When someone who knew a shared password leaves, the password has to change for everyone who uses it, and the new one has to reach each of them. Until it changes, the person who left still knows a working password. That’s the risk.

Security frameworks treat this as a known risk. NIST’s account-management control lists shared and group accounts among the types of accounts organizations may wish to prohibit because of increased risk. Where shared accounts are used anyway, the same control calls for a process to change the shared password whenever someone is removed from the group, which puts a password change on the departure list of every person who ever knew it. Our dealership employee offboarding checklist says it in five words about shared logins and door codes: “if they knew it, change it.”

Multifactor authentication has the same limit. MFA adds a second step on a phone or app registered to the account. On a shared account, that step proves someone has the registered phone or app. It doesn’t show which of the people sharing the account is signing in. Microsoft’s security defaults guidance says that, based on its learnings, more than 99.9% of common identity-related attacks are stopped by using multifactor authentication and blocking legacy authentication. Microsoft applies the same idea to shared email: its shared mailbox guidance says sign-in for the shared mailbox account itself should be blocked and kept blocked, so that people reach the mailbox through their own accounts instead.

There’s a compliance side. The FTC’s Safeguards Rule guidance tells covered businesses to “implement multi-factor authentication for anyone accessing customer information on your system.” Our FTC Safeguards Rule checklist covers the rest. From where I sit, the operational reason comes first. You can’t protect an account you can’t tie to a person.

How Do You Move Each Role to Its Own Account?

Move one shared account at a time, starting from a list of every login more than one person uses. Give each person and each vendor employee a named account, move department inboxes to shared mailboxes people open from their own accounts, turn on MFA per account and keep each person’s contact details current with your help desk.

  1. Make the list. Every shared username, what it reaches and who uses it.
  2. If the store runs on Microsoft 365, department inboxes become shared mailboxes. Microsoft says one can store up to 50 GB without a license of its own, but each person who opens it needs their own licensed Exchange Online mailbox, and it supports at most 25 users.
  3. Workstations: each person signs in under their own account.
  4. Vendors get one named account per person who connects. Never the owner’s credentials, handed around.
  5. MFA on every named account as it’s created.
  6. Each person’s own email and mobile number go on file with your help desk, so they can be verified when they call.
  7. Put the rule in writing for employees. Our dealership acceptable use policy template already has the line: “Your login is yours.”
  8. Retire the old shared login and change its password, so it can’t quietly come back.

Who owns the work? Your IT team or provider builds the accounts and retires the old ones. Department managers confirm who needs what, because they’re the ones who know which person on the counter, in the office or at a vendor actually needs each system to do the job. Licensing is a real line item, so price it with whoever signs off on it before you start, not after.

One account at a time is how it gets done.

IT manager and service manager reviewing a printed list of accounts together at a dealership conference table

Things Dealers Ask About Shared Logins

Our service drive has one PC that five advisors use. Do they really each need an account?
Each advisor should sign in as themselves, even on a shared PC. Otherwise nothing done on that PC can be tied to the person who did it, in the logs or in the manager’s reports.
Isn’t a shared department email the same thing?
Only if people sign in to it directly with its own password. A Microsoft 365 shared mailbox works differently: people get access through membership, and Microsoft says sign-in for the shared mailbox account itself should be blocked. Each member needs their own licensed mailbox.
What if a vendor insists on one login for their team?
Ask for one named account per person instead. The vendor story above is why. When an approved vendor’s staff all used one login, nobody knew who they were until two of them called the help desk posing as dealership employees.
Will the help desk still help someone on a shared login?
Every caller is verified first, whatever login they’re using. We verify the person against their own contact record, not the account. What verification can’t show is who else has been using that account, which is why moving them to their own account matters.
Where should we start if there are dozens of these?
With the list. Then rank each shared account by what it can reach, and move the ones that reach customer information or allow remote access first. Those are where the FTC’s MFA line and the vendor case above both point.

Start With the Login List

A shared login looks like a convenience until the day you need to know who used it. Then it’s a blank. Nobody can fill it in. Not later, either. Our complimentary IT and cybersecurity assessment reviews your current technology setup and security posture, and the findings come back to you in writing. Bring your login list to it.

Every account should have one person behind it.

About the author

Rex Marchant

Vice President of Service, Helion Technologies

Rex Marchant is Vice President of Service at Helion Technologies, where he leads the service desk, field service, systems engineering, proactive managed services and VoIP. He has more than 25 years leading managed services teams and holds ITIL Foundation and COBIT 5 certifications.

Rex Marchant on LinkedIn

Confidence in your current setup and actual protection aren't always the same thing. The only way to know which one you have is to look.

Get Your Complimentary IT & Cybersecurity Assessment →