Skip to main content
Operations

Former Employee Still Has Access? A Same-Day Fix for Service Companies

Most ex-employees keep at least one working login. A same-day offboarding checklist for service companies, and when single sign-on turns most of it into one switch.

Published November 8, 2026 6 min read

Topic: Team, time tracking and inventory

Your dispatcher quit two weeks ago. Friendly exit, laptop handed back, keys on the desk. This morning a customer mentions that "your guy" called her about her maintenance plan renewal. You don't have a guy calling about renewals. You check, and the former dispatcher's login to the scheduling tool still works. So does his email on his phone, and the shared password to the supplier portal nobody changed.

If a former employee still has access to your systems, you're in the majority, not the exception. This post covers how common it is, why service companies are especially exposed, a checklist that closes the gap on the last day, and when single sign-on turns most of that checklist into one switch.

How often a former employee still has access

More often than owners think. In a 2026 offboarding survey of 1,000 U.S. adults by Sagiss, an IT and security services firm, 79% said at least one work account kept working after their last day. Thirty percent said the access lasted more than a month or still works.

Two findings from the same survey matter most for a trades business:

  • Smaller employers left more doors open. People who left companies with fewer than 250 employees had lingering access 82% of the time, against 70% at companies over 1,000.
  • Taking the laptop back didn't fix it. Among people whose equipment was collected, 82% still had at least one working account.

It's self-reported survey data from a company that sells IT services, so treat the exact numbers with that in mind. The pattern is hard to argue with, though: the accounts outlast the job.

Why service companies are exposed

A service business has more logins per person than you'd guess, and more of them are shared:

  • Office staff sign into the scheduling and dispatch board, the accounting system, email, the phone system, supplier portals, the payment processor and maybe a separate booking tool.
  • Technicians carry a company phone or use their own, with the field app, email, a parts supplier app, and often a fuel card.
  • Shared credentials pile up: the truck tablet, the front-desk computer, the supplier account everyone uses.
  • Turnover is normal. Techs move between shops (we dig into why in why field service technicians leave) and seasonal staff come and go, so offboarding isn't rare; it's a monthly job.

The risk isn't only theft. A former employee with a working login can see customer names, addresses and service history, pricing, and sometimes payment records. In the Sagiss survey, 29% could still reach customer or client information after leaving.

A same-day offboarding checklist

Most of this costs nothing but discipline. Do it the day someone leaves, and for a layoff or firing, plan it before the conversation happens.

  1. Name one owner. One person, often the office manager, owns the whole checklist. When it's split between "HR" and "whoever set it up", it doesn't happen.
  2. Keep a list of every account by role. Dispatcher, tech, office, manager. Write down every system each role touches, including supplier portals and fuel cards.
  3. Turn off the person, not just the device. Collecting the laptop and phone is step one. Then disable their account in every system on the list.
  4. Change shared passwords and codes. Supplier logins, the truck tablet, door and gate codes, the alarm code.
  5. Remove company email and apps from personal phones. Especially techs who used their own phone in the field.
  6. Keep their records. Disable, don't delete. The jobs they ran, the notes they wrote and the hours they logged still matter to the customer, to payroll and possibly to a dispute.
  7. Check a week later. Try the old logins, or ask your IT provider to confirm. In the Sagiss survey, some access was still working more than a week after the former employee reported it.

When single sign-on makes it one switch

Steps 2 to 4 are where things slip, because every system is a separate door. Single sign-on changes that. Your staff sign into their work apps with one company account, the same one they use for email. When someone leaves, you disable that one account and every app that uses it stops letting them in.

Automatic account provisioning, which IT people call SCIM, goes a step further. When someone joins, changes role or leaves, the change is made once in your company directory and carried into each connected app.

When it's worth it

  • You already run Microsoft 365. Your staff already have Microsoft work accounts, so you're adding apps to something you have, not buying a new system.
  • You have several branches or a sizeable office. More people and more locations mean more accounts to keep track of.
  • You have an IT person or an IT provider. Someone has to connect each app once. After that, the day-to-day work drops.

If you're comparing software right now, add "can we sign in with our Microsoft accounts?" to your list of questions to ask before you choose field service software.

When it isn't

  • You don't use Microsoft 365. FSM Navigator's single sign-on works with Microsoft Entra ID only, the identity service behind Microsoft 365. If your company runs on another provider, it isn't the right fit today.
  • You're a few people with one office. The checklist above, done honestly, is enough. Disable the user the day they go and change the shared passwords.

Where FSM Navigator fits

Every FSM Navigator plan has role-based access control, multi-factor authentication and an audit log of significant actions, and the Owner can deactivate a user the day they leave. On paid plans, a deactivated user stops using a seat, so you're not paying for the person who left.

On Enterprise, single sign-on with Microsoft Entra ID lets your staff sign in with their Microsoft work account. That's one password to manage and one place to remove access when someone leaves. The Owner or an Administrator sets it up, and you choose whether single sign-on is Optional (staff can still use their FSM Navigator password) or Required. SCIM creates, updates and deactivates staff accounts from Entra and maps your Entra groups to FSM Navigator roles, so a new dispatcher gets dispatcher access and a departing one loses it when IT disables them in Microsoft.

An emergency administrator account keeps a password sign-in that doesn't go through Microsoft, so your business isn't locked out if something goes wrong with single sign-on. When it's used, the other Owners and Administrators are alerted.

And if someone leaves on bad terms, Enterprise also has legal holds: the Owner can place a hold on a team member so deletions that would remove their records wait while a legal matter is open.

FAQ

What should I do if a former employee still has access?

Disable their account in that system right away, change any passwords they knew, and check every other system on your list for the same person. Keep their records; disable rather than delete.

How common is it for ex-employees to keep access?

Common. In Sagiss's 2026 survey of 1,000 U.S. adults who had left a job, 79% said at least one work account kept working after their last day, and 30% said it lasted more than a month or still works.

Is single sign-on only for large companies?

No. It's about how many systems and people you manage, not headcount. If your staff already have Microsoft work accounts and you run several apps, it can save time at any size.

What is SCIM provisioning?

A standard way for your company directory to create, update and deactivate user accounts in other apps automatically, so a change made once in Microsoft Entra ID carries through.

Does FSM Navigator support Google or Okta for single sign-on?

Not today. FSM Navigator's single sign-on supports Microsoft Entra ID only.

Make removing a former employee one switch in Microsoft. Try Enterprise free for 14 days.

Start a 14-day Enterprise trial

A payment method is collected when the trial starts, and nothing is charged until the trial ends. iOS & Android included.