Orphaned accounts are user accounts that no longer belong to anyone who should have them: a former employee's login that was never removed, a contractor's account that outlived the contract, a test user, or an account in a tool nobody remembers owning. They still work, they may still hold paid seats, and nobody is watching them.
You find orphaned accounts by comparing each tool's member list with the list of people who work for you, by email. Anything in a tool that does not match a current person is a candidate. The rest of this post covers where they come from, why they matter, and how to find, clean up and stop them.
What makes an account orphaned
An account becomes orphaned when the link between it and a responsible person breaks. There are a handful of usual ways.
The most common kind is the leaver who was missed. They were suspended in Google Workspace, and they are still a member in the analytics tool, the design tool and the support desk. Close behind are personal-email accounts: someone joined a tool with their own Gmail address because the invite went there, or a contractor never had a company address. When they leave, nothing in your directory connects that account to them.
Contractors and agencies produce the next batch. They were invited for a project and never given an end date. The project ended; the access did not. Contractor access management covers how to stop that at the source.
Then there are accounts that never had a real person behind them. Test and demo users were created to try a feature or reproduce a bug, with a made-up name and an email nobody reads. Service and integration accounts, a "bot" user or an API token, were created by an employee who has since left. They run something important, and nobody knows which password or key they use.
Some tools are orphaned whole. Someone signed up for a trial, then stopped using it. Every account in it is orphaned, including the admin. And finally there are old addresses: people who changed names, or a company that changed domains, and kept accounts under the old address alongside the new one.
Orphaned accounts vs stale accounts
"Stale accounts" is a related term: accounts that have not been used for a long time. Most orphaned accounts are stale, but not all stale accounts are orphaned. An employee on long leave has a stale account that is still theirs. A salesperson who has not opened the analytics tool in six months has a stale account that they still own, and that you may simply be overpaying for.
The difference is ownership, not activity. An orphaned account needs removal. A stale account needs a question: does this person still need this? That makes stale accounts a license management problem first and a security problem second, while orphaned accounts are both at once.
The reverse case also exists: an orphaned account that is not stale. A former employee who still logs in, or an integration under a departed person's token that runs every hour, is fully active and fully unowned. Those are the ones to look for first.
Why they matter
There are three reasons, in rough order of how often they bite.
They cost money. Many tools charge per seat. An orphaned account on a paid plan is a seat you pay for and nobody uses. Some tools stop charging for inactive members automatically, but many do not, and you only find out by reading the bill. Even suspending someone in Google Workspace does not stop the charge there: Google says suspended accounts are billed at the same rate as active ones (Google's suspension help). And removing the person is not always enough either. GitHub's help page on removing a member says that under volume licensing, the paid license count does not drop automatically when you remove someone, as we read it on 27 October 2026.
They are a way in. An orphaned account is a working login. If it belongs to someone who left on bad terms, they can still use it. If its password was reused somewhere that leaked, someone else can. And because nobody owns it, nobody notices unusual activity. Accounts with admin rights or API tokens are the worst case, since they can create more access. Revoking access properly covers what a live login actually allows.
They break your records. If an auditor, a customer's security questionnaire or your own user access review asks who has access to customer data, an orphaned account is an answer you cannot explain. "We don't know whose that is" is not a good line in an audit.
None of this needs a dramatic breach to matter. Paying for seats you do not use and not knowing who can read your CRM are problems on an ordinary Tuesday.
Finding them
There is no single place that lists orphaned accounts, because each tool keeps its own user list. Finding them is a matching exercise.
Start with your list of people. Your directory is the source of truth: Google Workspace or Microsoft 365. Export current users, and separately note suspended and deleted ones. Add contractors who legitimately have access, with their email addresses, since they will not be in the directory.
Then get each tool's member list. Most tools let an admin see or export members with their email, role and, often, last active date. Do this for every tool you pay for, and for the free ones that hold company data. If you do not have a complete list of tools, start with the ones on your card statements and the ones people sign into with Google. Shadow IT covers finding the tools you do not know about.
Match by email. For each account in each tool, look for a current person with that email. Sort what is left into buckets:
| What you find | Likely cause | Action |
|---|---|---|
| Email of someone suspended or deleted in the directory | Missed offboarding | Remove |
| Personal address (Gmail, Outlook) on a work tool | Personal sign-up or contractor | Find the person; replace or remove |
| Your domain, but no such user in the directory | Old address, typo or test user | Investigate, then remove |
| Generic name: admin@, bot@, test@ | Shared or service account | Find an owner; document or remove |
| Current employee, no activity for months | Stale, not orphaned | Ask whether they still need it |
Once the leftovers are sorted, look at roles. Check orphaned candidates with admin or owner roles first. Then those in tools with customer data or money. Then the rest.
Finally, look for credentials, not just users. API tokens, OAuth app grants and integration users created by people who left. In tools that list tokens with their creator, filter by people no longer in your directory.
The first time takes a while. The second time is mostly diffing against last quarter.
What it looks like at 5 people and at 50
At five people with a dozen tools, the whole exercise fits in an afternoon, and the founder can usually name every account from memory. The candidates tend to be trial tools and test users.
At fifty people with several dozen tools and a few years of leavers, matching by hand becomes a real project. The candidates tend to be missed offboardings, contractors and integrations built by people who moved on. That is the size where a tool that keeps the match current, rather than a quarterly spreadsheet, starts to earn its place.
Cleaning up
Do not delete first. An account you think is orphaned might be running an integration, or own the files a team relies on. Work through it in order.
Find an owner. For each candidate, ask the team that uses the tool. Someone usually knows.
Move what matters. Transfer ownership of files, projects, workspaces and billing to a current person. Replace integrations running under an orphaned account with a service account owned by someone staying.
Deactivate. Most tools offer deactivation, which keeps history and blocks sign-in. That is reversible if you were wrong. What is deprovisioning? explains the difference between deactivating and deleting.
Lower the seat count in tools that do not do it automatically. Otherwise you have removed the person and kept paying for them.
Wait, then delete if you want to. After a few weeks with no complaints, delete if the tool's data handling requires it. Many teams never need to.
Write it down. Which accounts, in which tools, what you did. This is the evidence that cleanup happens.
For a tool nobody owns at all, decide whether the company still needs it. If not, export what you must keep and cancel the subscription; that removes every orphaned account in it at once.
Shared logins are a special case. An account like social@ or a supplier portal login that several people know the password to has no single person to remove. If one of those people leaves, the account is not orphaned, but their access to it is. Change the password, and check where the two-factor codes go. Shared accounts covers how to replace them.
Stopping new ones
Cleaning up is a one-off. Orphaned accounts come back unless the causes are fixed.
Start by offboarding every tool, every time. Most orphaned accounts are offboarding misses. A written offboarding process with one named person responsible for access, plus the employee offboarding checklist, fixes most of them.
Next, invite with company emails only. Ask people to accept invites with their work address. For contractors, either give them a company account or keep a list of their external addresses with an end date, and use guest-account expiry where a tool offers it.
Then name an owner for every tool, one person who knows who is in it. Unowned tools are where orphaned accounts accumulate. The same goes for service accounts: every bot user, integration and API token gets a named human owner and is written down.
Finally, check on a schedule. Repeat the matching exercise regularly; quarterly is a reasonable default for a small team, and more often if people come and go a lot. Also check every time someone leaves, a few days after their last day, by searching each tool for their email.
What to do this week
Pick your five most expensive or most sensitive tools. Export each member list, match it against your Google Workspace users, and sort the leftovers into the buckets above. Deal with the admins and the leavers today. Then put a date in the calendar three months out to do it again, with one more tool added each time.
Where SmashSSO fits
SmashSSO does the matching exercise continuously. It reads your people from Google Workspace with read-only directory access and builds an access grid: who has an account in each of your tools and with what role, matched by email. Accounts that match nobody in your directory are flagged, which is the list of orphaned candidates without a spreadsheet. When someone is suspended in Google Workspace, it alerts you and shows where they still have access.
From the grid you can remove accounts across tools, through a tool's member API where you have added a token, or through an agent in your own Chrome where you are signed in as an admin. Any change that would add a paid seat stops for approval, and every change is recorded in an audit log. The limits: it needs Google Workspace as the directory, the Chrome agent needs that browser open and can fail when a tool redesigns its screens, it does not track spend, and it has no CSV export, so the record lives in its audit log. It is not SSO. It costs a flat fee from $199 a month, billed annually (pricing); the tools page lists what it works with.