Shadow IT is any software your team uses for work without the company having decided to use it: the free trial someone started with their work email, the app connected through "Sign in with Google", the subscription on a personal card that gets expensed every month. Nobody hid it. Nobody in charge of security, money or offboarding knows it is there.
In a small company most shadow IT is not a rule being broken, because there were no rules. It is people solving problems quickly. The trouble starts later: when the tool holds customer data nobody secured, when it renews on a card nobody checks, and when someone leaves and keeps their account because it was never on the list.
What shadow IT is
The term covers more than paid apps. In a company running on Google Workspace, the biggest group is plain SaaS sign-ups: a design tool, a survey tool or a transcription service, created with a work email and used by a few people. Close behind are OAuth connections, apps someone allowed to read their Gmail, Drive or Calendar through Google's consent screen. Those may never appear on an invoice at all.
Then come the quieter kinds. Personal accounts used for work put company files in a personal cloud drive, or a client conversation on a personal messaging app. Browser extensions can read the pages people work in. AI tools are where people paste customer emails, code and contracts to get a summary or a draft.
The last kind surprises people: abandoned official tools. The company did choose it, but its owner has left and nobody manages it any more. It started legitimate and became shadow IT by neglect.
What they share is that nobody accountable can answer three questions about them: who has access, what data is in there, and who pays.
How it starts
Shadow IT is mostly a product of how SaaS is sold. Modern tools are built so that one person can start without asking anyone.
It begins with free plans and trials, which need nothing but an email address. "Sign in with Google" makes the sign-up one click, using the company account. Then invites spread it: the first user invites their team, and within a month a tool has eight company accounts and one owner.
Cards make it permanent. When the free plan runs out, someone puts it on a card. Now it renews automatically, sometimes on an annual plan. If asking for a tool takes two weeks, or there is nobody to ask, people stop asking.
Finally, people leave. The person who chose the tool and knew how it was set up is gone. Their account is the owner, attached to an email that no longer works.
None of this needs bad intent, which is why blaming people for it rarely works.
The risks: data, spend, offboarding
Data. Every tool holding company data is a place that data can leak from. Shadow tools are the ones nobody configured: no MFA requirement, public sharing links left on, an "anyone at your domain can join" setting, no admin who would notice an odd login. OAuth connections deserve their own mention, because a single click can give a third-party app ongoing access to someone's email or files. That access continues whether or not the person still uses the app. The wider picture is in SaaS security for small businesses.
Spend. Duplicate tools (three note-taking apps, two video tools), seats for people who left, annual renewals nobody intended. It is rarely one big number. It is many small ones that nobody adds up. Where SaaS spend goes breaks the money down.
Offboarding. This is the risk small companies feel first. Your offboarding checklist covers the tools you know about. A leaver's account in a tool nobody knew about simply stays. If they signed up with Google, suspending their Google account stops new Google sign-ins, but if the tool also let them set a password, that password still works. And if they were the owner, nobody else may be able to get in at all. Orphaned accounts covers what happens next.
Is shadow IT always bad? No. It is often the first sign of a need the company has not met: people adopted a tool because it made their work better. Some of today's shadow IT is next year's standard tool. The aim is not to stamp it out but to see it, then decide what to keep.
Shadow IT discovery
There is no single place that lists everything. Each source catches some shadow IT and misses the rest, so use several. The guides to SaaS management and SaaS sprawl cover building the inventory itself. Here is what each discovery source is good for, in the order we would use them.
Start with Google Workspace's connected apps. In the Admin console, under Security > Access and data control > API controls, the Accessed apps list shows third-party apps your users have authorized with their Google accounts, with the number of users for each and the Google services each one requests, according to Google's help page as we read it on 27 October 2026. Google notes the list updates 48 hours after access is granted or revoked. Read it two ways: the long tail of apps with one or two users is your shadow IT, and any app requesting Gmail or Drive access is where to look first. It catches tools people signed into with Google, and add-ons that read mail, files or calendars. It misses tools created with a work email and a password, and anything on personal accounts. The Google Workspace security checklist shows the rest of that page's settings.
Then follow the money. Company card statements, but also expense reports: tools on personal cards show up as reimbursements, often under vague categories. Look for small, regular amounts. Twelve months back catches annual plans. Money catches everything paid and misses everything free, which is often the riskiest, because free plans rarely have admin controls.
Then read your domain's DNS records. Many tools ask you to prove you own your domain by adding a TXT record, and email-sending tools add themselves to your SPF record. Run dig TXT example.com (with your own domain), or open your DNS provider's dashboard, and you will see verification records left by tools someone connected at company level, some long forgotten. This catches tools set up seriously enough to verify the domain or send email as you. It misses lightweight sign-ups.
Ask people to search their own inboxes. Everyone can search their own mail for "invited you to", "welcome to" and "your trial", and send you the list. Searching other people's mail as an admin is a bigger step, with privacy and legal implications, and usually the wrong first move.
Ask, with an amnesty. A short message works: "List every tool you use for work that is not on this list. Nobody is in trouble; we want to make sure it is secure and paid for properly." People will tell you, if telling you does not lead to losing the tool.
Check browsers and devices last. If you manage company laptops or the Chrome browser centrally, your management console can report installed extensions and apps. Most small companies do not, which is fine; the first five sources find the bulk of it.
SaaS discovery tools
Discovery products, sold as SaaS management or "SaaS discovery" platforms, automate some of these sources by connecting to your identity provider, finance tools, email or browsers. They are mostly built and priced for larger companies, often per employee and through a sales call.
For under 50 people, an afternoon with the sources above usually finds most of what matters. The test for buying one is simple. If you would run the manual sweep every quarter and it takes more than a day, a tool may pay for itself. If you would run it once and forget, a tool will not fix that habit either.
What it looks like at 5 people and at 50
At five people, shadow IT is mostly the founders' own sign-ups. Everyone knows roughly what everyone uses, and the real risk is concentration: one person created the accounts for the domain registrar, the payment provider and the email-sending tool, with their personal phone as the second factor. Finding it takes an hour. Fixing it means moving ownership to a company-controlled address and adding a second admin.
At fifty people, nobody knows what everyone uses. Teams have their own tools, contractors have come and gone, and the Accessed apps list runs to dozens of apps. The risk shifts from concentration to volume: many small tools, each with a few accounts that outlive the people who made them. Here the quarterly sweep and a named owner per tool matter more than any one discovery source.
Bringing it in
Finding tools is half the job. For each one, decide:
| Decision | When | What to do |
|---|---|---|
| Adopt | People rely on it and nothing official does the job | Name an owner, move billing to the company, add it to your inventory and onboarding/offboarding |
| Replace | An approved tool already does the same job | Agree a date, export what is needed, move people, then remove every account |
| Retire | Unused, or the risk is not worth it | Export if needed, remove accounts, cancel billing, revoke its connection to Google |
For tools you adopt, "bringing it in" means four things: a company-controlled owner account (not a personal one), an admin who is a current employee, the company paying for it, and every account in it belonging to someone in your directory. If the tool's owner is a generic login several people know, treat it like any other shared account: into a password manager, with a named owner. Then set it up properly, with MFA where available, sensible sharing settings, and the right role for each person.
The common mistake is stopping at the decision. A tool marked "retire" in a spreadsheet still has live accounts until someone removes them, and a tool marked "adopt" is still shadow IT until it shows up in onboarding and offboarding.
How to prevent it
To prevent the next round, make the official path faster than the shadow one.
Publish a short list of approved tools for common jobs, so people pick those first. Then give requests one place to go, and answer within a day or two. A fast "yes, with these settings" beats a slow "no".
Restrict risky app access in Google Workspace. The same API controls page lets you mark apps as trusted, limited or blocked, and decide what happens with apps you have not reviewed. One option, per Google's page, allows only apps that request basic sign-in information, so users can still "Sign in with Google" but new apps cannot read mail or files without review. Test it with a small group first.
Repeat discovery every quarter. Shadow IT comes back; it is how SaaS is designed to be adopted. Fold the sweep into your quarterly user access review, so the new tools and the people in them get checked together.
Where SmashSSO fits
SmashSSO is not a discovery tool. It does not scan card statements, DNS or browsers; you add the tools you use, from its catalog or by hand. What it does is the "bring it in" step for access. It reads your people from Google Workspace with read-only access, reads who has an account in each tool you add and with which role, and matches them by email. Accounts that match nobody in your directory, such as personal emails, ex-contractors and shared logins, are flagged, and people suspended in Google Workspace show every tool where they still have access.
From the same screen you can invite people by role and remove leavers, through a tool's member API where you have added a token or an agent in your own Chrome otherwise. That agent needs the browser open, is slower than an API, and can fail when a tool changes its screens. SmashSSO does no spend tracking. It is not SSO, and it costs a flat fee from $199 a month, billed annually (pricing).