How to Remove Access to Company Apps When an Employee Leaves (Step by Step)

How to Remove Access to Company Apps When an Employee Leaves (Step by Step)

•

thumbnail-blog-accessowl-how-to-remove-access-to-all-company-apps-when-an-employee-leaves

To remove someone's access to every app when they leave, keep a live list of the apps they use, including the ones they signed up for on their own. Suspend their main workspace account in Google Workspace or Microsoft 365. Then remove their access to third-party SaaS apps like Notion, Slack and Claude, and check the internal tools they can reach from their laptop.

Many teams stop after suspending the workspace account. Suspending a Google account blocks Gmail, Docs and new "Sign in with Google" logins. It doesn't close their accounts in other SaaS apps unless those apps are connected through SCIM. Large companies with a dedicated IT team usually connect their apps that way. For teams with a small IT team, or none, a lightweight SaaS access management tool like AccessOwl is a better fit.

Whatever the tool, a good offboarding flow in one line: the end date in the HR system starts it, the app list is current, the workspace account is suspended, every SaaS account is removed by a tool or an admin, a shadow IT scan catches what's left, and each removal is logged. All on their last day.

Why manually removing access breaks down

manual-offboarding-breaks-accessowl-graphic

Without a tool, offboarding usually starts with a message to IT that someone is leaving. Without an IT team it lands on whoever pulls the short straw. Often an HR, operations, or technical (non IT) team member. From there, it looks like this:

  • A list from memory: whoever offboards works from a spreadsheet, or from what managers remember giving to the person.

  • One app at a time: someone logs into each app's admin page, finds the user and removes them.

  • Apps nobody assigned: tools the person signed up for with "Sign in with Google", signed up with username/password aren't on any list.

  • Waiting on app admins: apps owned by other teams stay open until their admin gets to it.

  • No way to validate: at the end, nobody can say for sure that every account is gone.

  • OAuth connections stay live: more people connect AI agents to their work email, calendar and files. Each connection needs to be revoked, and the AI tool can still hold copies of company data.

Based on conversations with 115 companies that evaluated offboarding automation tools, offboarding one employee by hand take about 1 hour (2026 State of Access Management). And that hour only covers the apps someone remembered.

The accounts that get missed are where security and compliance problems start. A former employee can still sign into a tool that holds customer data. More likely, an attacker tries to take advantage of access that still exists and no one is closely monitoring. An auditor asking for proof that access was removed gets a spreadsheet that's out of date. Drieam saw this before they moved to a central tool:

"The manual way of logging access created anxiety over potential security risks — such as forgetting to offboard leaving employees promptly."

Tom Lamers, Strategy & Operations Lead, Drieam Case Study

Step 1: Keep a live inventory of the apps the employee has access to and who manages each one

Start with the apps you know the person uses beyond Google Workspace or Microsoft 365. For each one, write down who can remove users from it. That's usually the manager of the team that uses the app, not IT.

The easiest time to start this list is when someone joins. If you create software accounts for new hires from role templates, each person's app list builds itself.

The list is longer than most people expect. From our data sample of 100 companies, full-time employees had to be removed from a median of 17 apps beyond their main workspace when they left. Access to those 17 apps sat with a median of 8 different app admins.

If you don't have a list, your finance data is a good place to start. Card statements and expense reports show the paid tools, and invoices often show whose name is on the seat.

Step 2: Suspend their Google or Microsoft account

Suspend the account at the end of their last working day. Suspending blocks new sign-ins with their work account and keeps their files and email in place, so you can hand them over to their manager before deleting anything. Our guides for Google Workspace and Microsoft 365 cover the handover.

Suspending the main account closes the sign-in. It doesn't remove the account inside each app. Two kinds of apps stay open:

  • Third-party SaaS apps not connected through SCIM: the account still exists. If the app allows a separate password, they can still log in. Some apps, like Slack, keep people signed in until the account is removed.

  • Shadow IT: apps nobody assigned don't get touched at all, because nobody knows they're there.

A cofounder and CTO at a data analytics startup we work with told us what this looked like for them:

"I don't feel confident that I got rid of everything. And I've seen people insist they saw someone with admin access to Sentry last week, who hadn't been in the company for like three months."

Cofounder & CTO, data analytics startup

Step 3: Find shadow IT

Shadow IT means the apps people use without the company managing them. They don't show up in your app list or on the company card, because nobody bought them. Someone signed up with "Sign in with Google", or a teammate invited them to a free workspace.

These apps are easy to miss and there are a lot of them. Only about 3 in 10 apps employees sign into are managed. The median company has about 70 shadow apps.

To find the ones the leaver used, check their connected apps in the Google Workspace or Microsoft 365 admin console. Every time someone uses "Sign in with Google" or "Sign in with Microsoft", or gives an app access to their email or files, it shows up there.

You can do this yourself, for free. But if you are non technical and want an immediate scan with a report you can use AccessOwl's free shadow IT scan.

Ethan Yu, cofounder and COO at Motion, saw how apps end up outside the official process:

"...what happened was we basically had a shadow IT system where people got added to the service first before a ticket was created."

Ethan Yu, Cofounder & COO, Motion Case Study

Step 4: Remove the account inside each SaaS app (deprovisioning)

Deprovisioning means removing a person's account and permissions in each app. This is most of the work in offboarding, and teams usually handle it one of three ways:

  • By hand: someone logs into each app, or messages each app admin, and removes the user. It works up to 30 employees. Past that, accounts get missed.

  • With an identity provider and SCIM: like Okta, JumpCloud or Microsoft Entra ID. They remove accounts in apps connected via SCIM. Many apps only offer SCIM on their enterprise tier, known as the SSO tax, so only a fraction of apps are covered.

  • With a SaaS access management tool like AccessOwl: it removes accounts across your apps on the leave date set in your HR system. It handles deprovisioning without SCIM through integration accounts.

For the full setup, including onboarding, see our guide to automating SaaS access for onboarding and offboarding.

Step 5: Keep track of access removal

Removing access is only half the job. You also need to prove it happened.

For every app, keep a record of three things:

  • What was removed: the app and the access level the person had.

  • Who removed it: the automated tool, or the name of the admin who did it.

  • When: the date and time, so you can show it happened on their last day.

Once that's in place, check the person's connected apps again a few days later. A new sign-in after their leave date means an account is still open somewhere.

This record is also what an auditor asks for. For SOC 2 or ISO 27001, you need to show that access was removed on time for everyone who left. A SaaS access management tool like AccessOwl keeps this log as it goes.

Comparing 4 Ways to Remove App Access When Someone Leaves

Each method covers part of the steps above. They differ in which apps they reach and whether they find apps nobody assigned. For a side-by-side of specific products, see the best tools for automating offboarding.

Method

Removes accounts in

Finds apps you didn't assign

Who runs it

Good fit if

SaaS Access Management Tool (AccessOwl)

Your apps, without requiring Enterprise plans for apps

Yes

HR, Ops or IT

You want every app covered, with a setup that takes a few days

Identity provider with SCIM

Apps with SCIM on your plan

No

A dedicated IT team

Most of your apps are on enterprise plans

HR system IT add-on

Apps in its catalog

No

HR or Ops

You're removing 3 to 5 apps that are in its catalog

Manual checklist and spreadsheet

Whatever is on the list

No

Whoever offboards

You only manage 5-10 apps and few people leaving

SaaS access management tool (AccessOwl)

AccessOwl is a SaaS access management tool, a focused part of IAM (identity and access management). Enterprise IAM suites are built for large IT teams. AccessOwl covers the everyday access work that small IT teams, or HR and Ops, run themselves: creating accounts, removing them and handling requests. It connects to 500+ apps through integration accounts, so no SCIM is needed and you don't have to move apps to enterprise plans.

  • HRIS-triggered offboarding: setting a leave date in your HR system schedules the offboarding. Nobody has to remember it on the day.

  • Wider app coverage: AccessOwl removes accounts in 500+ apps through integration accounts. There's no code to write and no API connections for you to maintain.

  • Removal in every app: accounts are removed in each connected app at the scheduled time. Apps without an integration go to their admin as a task.

  • Shadow IT discovery: AccessOwl's shadow IT discovery finds the apps each person signed into with their work account, so apps nobody assigned are part of the offboarding too.

  • Audit-ready records: every removal is logged with who did it and when.

Shane Fritts at Maxio schedules each offboarding when the request comes in, then lets it run:

"I can call it an early day on a Friday. It's 3 PM, there's nothing going on. 'Guys, clock out. I'll watch our escalation channel, and the offboarding's gonna just kick off when it kicks off.'"

Shane Fritts, Senior IT Manager, Maxio Case Study

The same access templates handle onboarding too. See how AccessOwl compares with other onboarding automation tools.

AccessOwl is built for teams of 30 to 1,000 people. It runs alongside Google Workspace, Microsoft 365 or Okta, so you keep what you already use for sign-in. Pricing is public, and you can test it with your own HR system in a 7-day free trial.

Identity provider with SCIM

An identity provider is the system your team signs in with, like Okta, JumpCloud, Microsoft Entra ID or Google Workspace. With SCIM, it can also remove accounts in connected apps.

Works well for: companies with most apps on enterprise plans and a dedicated IT team to run it.

Where it stops:

  • Apps without SCIM: the identity provider blocks the sign-in but can't remove the account, so someone still does it by hand.

  • SCIM on enterprise plans: many apps only offer SCIM on their top tier. Connecting them means paying the SSO tax for each one.

  • Shadow IT: apps people signed up for on their own aren't connected, so they aren't removed.

  • Built for a full identity setup: Okta and JumpCloud need someone to run them. See what Okta costs for a small team.

HR system IT add-on

If your HR platform sells an IT module, like Rippling IT or Deel IT, it can remove accounts when you mark someone as leaving. It's a natural first place to look, since the leave date already lives there.

Works well for: a short list of apps in its catalog, with no extra system to connect.

Where it stops:

  • A limited catalog: apps outside the add-on's catalog stay manual, and so does shadow IT.

  • Often runs through your identity provider: some HR add-ons pass the leaver on to Okta or Entra ID, which removes accounts through SCIM. That brings the same SCIM and enterprise-plan limits.

  • Priced as an add-on: it's billed on top of your HR plan, so the total can cost more than a dedicated tool. The Maxio Case Study describes how they avoided a $28K Rippling IT mistake.

  • Tied to your HR vendor: if you switch HR systems, you rebuild your offboarding.

Manual checklist and spreadsheet

Most teams start here. A shared checklist lists the apps, and someone ticks them off as they remove the person.

Works well for: a small team with a handful of apps and few people leaving.

Where it stops: the checklist only has the apps someone added to it. It goes out of date as soon as a team starts using a new tool. Each offboarding takes about an hour, and there's no way to confirm every account is gone.

Every App Closed on Their Last Day, with AccessOwl

AccessOwl helps you automate onboarding and offboarding from your HR system. It removes accounts in 500+ apps, with no SCIM needed. Shadow IT discovery adds the apps nobody assigned, and every removal is logged for your next audit. Start a 7-day free trial and set up your next offboarding.

FAQs

How to Remove App Access When an Employee Leaves

Start from the end date in your HR system. Keep an up-to-date list of the apps they use, suspend their Google or Microsoft account and remove their account inside every other app. Then check for shadow IT and log each removal. A good benchmark is to have it all done on their last working day.

If I suspend an employee's Google account, can they still get into company apps?

In some apps, yes. Suspending their Google account blocks Gmail, Docs and "Sign in with Google". Their accounts inside other apps still exist. If an app allows a separate password, or keeps people signed in, they can still get in until the account is removed in that app.

Does blocking a Microsoft 365 account remove access to other apps?

Not on its own. Blocking sign-in stops new sign-ins with their Microsoft account, including "Sign in with Microsoft". Revoke their sessions too, so they're signed out of Microsoft apps right away. Accounts inside other apps stay open until they're removed, unless those apps are connected through SCIM. Our Microsoft 365 offboarding guide covers the Microsoft side.

How do I find which apps a former employee still has access to?

Start with your app list and check each app's user list for their email. Then check their connected apps in the Google Workspace or Microsoft 365 admin console. That shows the apps they signed into with "Sign in with Google" or "Sign in with Microsoft", including ones nobody assigned. AccessOwl's free shadow IT scan does this for your whole company.

How do I revoke OAuth access when an employee leaves?

In the Google Workspace admin console, open the person's account and remove the apps listed under connected applications. In Microsoft 365, revoke their sessions and remove the permissions they gave apps in Microsoft Entra ID. Look closely at AI tools. Assistants and note-takers connected to their email, calendar or files can keep copies of company data in their own accounts.

Do I need Okta or SCIM to remove access to company apps automatically?

No. An identity provider with SCIM is one option, and it only reaches apps that support SCIM on your plan. AccessOwl removes accounts in 500+ apps through integration accounts, with no SCIM or identity provider needed.

How do I remove access to SaaS apps for contractors when their contract ends?

Set the end date from day one. Add contractors to your HR system or access tool with their contract end date, so removal is scheduled automatically. Check guest access too. Contractors are often added as guests or get files shared to a personal email, and those don't show up in your normal user list.

How quickly should access be removed when an employee leaves?

By the end of their last working day. Scheduling removals from the end date in your HR system makes that the default. SOC 2 and ISO 27001 auditors check removals against the deadline set in your own access policy.

Who should remove app access when an employee leaves, HR or IT?

HR usually starts it, because they set the end date. The removals sit with whoever administers each app, often managers across different teams. A SaaS access management tool connects the two: the end date in HR triggers the removals, and app admins only handle the apps without an integration.

How do I show an auditor that access was removed?

Keep a record for every person who left: which apps they were removed from, who removed them and when. Auditors for SOC 2 and ISO 27001 check that access was removed on time. A tool that logs each removal as it happens gives you that record without building it by hand.

Get an AI summary of this article

Table of contents

    Get an AI summary of this article

    Table of contents