Skip to content

Blog

Offboarding software: what to look for

Offboarding software comes in two kinds: HR tools for paperwork and IT tools that remove access. What to require, what to ask vendors and what it costs.

· 9 min read

Offboarding software comes in two kinds: HR offboarding software, which handles the paperwork (resignation records, final pay, exit interviews, document sign-off), and IT offboarding software, which removes the person's access to accounts and devices. For a small business the second kind is where things go wrong, and what to buy depends mostly on whether your tools' plans support automated removal.

Most products sold as "offboarding software" do one kind well and gesture at the other. This guide sorts them into categories, lists what the access side must do, gives the questions to ask a vendor, and shows where the money goes.

Two kinds of offboarding software

HR offboarding is about the employment ending: a leaving date, a final payslip, vacation owed, equipment to return, an exit interview, documents to sign. It lives in an HR system, and it ends when the paperwork is filed.

IT offboarding is about access ending: the person's accounts in every tool, their sessions, their tokens, their devices. It ends when nothing they had still works. The IT offboarding checklist lists the steps.

The two meet at one moment: HR records that someone is leaving, and that should start the access removal. In a lot of small companies, nothing connects them except a Slack message.

Within those two kinds, five categories of product compete for the job:

CategoryWhat it does on offboardingWhat it removesWhat it needs
HR system (HRIS)Leaving workflow, tasks, documents, payroll endUsually nothing, unless it has an IT moduleYour employee records in it
Identity provider with SCIMDeactivates accounts in connected tools when the person is removedAccounts in tools connected through SCIMSCIM on each tool's plan, often with SAML SSO too
SaaS management platformFinds the tools in use and who has accounts; some run removal workflowsVaries by vendor and by toolConnections to your directory, finance or browsers
Browser-based automationDoes the removal on each tool's admin pageAccounts in tools you can administer in a browserAn admin signed in, and a browser that is open
Checklist or task toolReminds a person what to do, in orderNothing; a person does itSomeone who keeps the list current

Does HR software remove tool access?

Usually not on its own. An HR system knows that someone is leaving and when. It can assign tasks to the manager, IT and payroll, and it can collect signatures. What it does not usually have is a connection into your Slack, your GitHub or your CRM that can deactivate an account.

Some HR platforms sell an IT module that provisions and removes app accounts from the same employee record. That is a real option if you are already buying the HR side, and it moves the question rather than removing it: for each of your tools, how does the module remove a person, and on which plan? If you are considering one, the Rippling pricing post shows how that kind of bundle is priced.

The useful thing an HR system almost always provides is the trigger. "Marked as leaving, last day Friday" is exactly the event your access removal should start from. If the HR system can tell your directory, or tell a person who then suspends the directory account, you have connected the two halves.

Must-haves for the access side

Whatever category you pick, the access side should do the following. If a product cannot, you will still be doing that part by hand.

It knows who has what. A current list of accounts per person per tool, with roles. Without this, removal is guesswork, and the orphaned accounts stay.

It starts from one trigger. The person is suspended in your directory, or marked as leaving in HR, and offboarding begins. Nobody should need to remember.

It covers the tools without SCIM. For most small companies, that is most of their tools. Ask what happens for each of yours, by name.

It deactivates rather than deletes, unless you choose otherwise. You want history kept and the seat freed.

It finds accounts under other emails. Contractors and early employees often signed up with personal addresses. Matching only on company email misses them, so at minimum the product should flag accounts that match nobody.

It reports failures. A removal that silently fails is worse than one you know you have to do.

It keeps a record. What was removed, where, when and by whom. That record is your evidence in a security questionnaire.

Questions to ask vendors

Take your actual tool list into the demo. Then ask about coverage first: for each of my tools, how do you remove a person, through SCIM, the tool's API, or something else? And which plan of each tool does that need, and will any of my tools need an upgrade? That second question is the one that changes the total. A product that "supports 300 apps" through SCIM supports your tools only on the plans of yours that include SCIM.

Next, ask about depth. What happens when a removal fails, how am I told, and what do I see? Do you end the person's open sessions and revoke their API tokens, or only the account? Do you find accounts that don't match anyone in my directory?

Then ask about trust. Where is the audit log, and can I get it out of your product? What data of mine do you store, and do you have a SOC 2 report or similar to show for it? If your customers send you security questionnaires, the answer to that last question may matter more than any feature.

Finally, ask about money. How is the price calculated: per employee, per tool, or flat? What does it come to for my headcount, in writing, and what happens to it when we grow?

A good demo test is to give the vendor a fake leaver. Pick one real person's set of tools, and ask the vendor to walk through, tool by tool, what would happen on their last day. The gaps show up fast.

Costs

Offboarding software is mostly priced per employee per month. Two prices we read today, as examples of the ranges.

On Okta's pricing page, as we read it on 27 October 2026, automated provisioning (Lifecycle Management) is included from the Essentials suite at $17 per user a month, and is an add-on on Starter. There is a $1,500 annual contract minimum. More in Okta pricing.

For an HR platform with IT, Rippling's pricing page, on the same day, says plans start at $8 per employee per month, with a monthly base fee it does not state. The IT modules are quoted separately.

The cost that does not appear on those pages is the tool side. SCIM-based removal needs each tool on a plan that offers SCIM, which is usually the plan that also has SSO. That upgrade, multiplied by every seat, is often bigger than the identity provider's bill. The SSO tax calculator shows it for your own tools.

If a vendor does not publish a price, ask for one in writing for your headcount, and ask what happens to it when you grow.

Do you need offboarding software for 10 people?

Often not. Under about 15 people, you may not need offboarding software at all. You need three things you can build from what you already have.

Google Workspace as the trigger. Suspending the person there is the first step of every offboarding, and it already ends their Google sign-ins.

An access list. A sheet with one row per person per tool, updated whenever anyone is invited. This is the expensive part of offboarding software, done by hand.

A checklist with an owner. The offboarding process post covers who does what and when.

What breaks first as you grow is the access list, because it depends on everyone updating it. That is usually the moment software starts paying for itself. A useful test: if the last leaver's offboarding missed a tool, or took someone more than an hour of hunting, the sheet has stopped working.

At 50 people the calculation is different. Someone leaves most months, several people send invites, and the tool count has grown past what anyone can list from memory. The question then is not whether to automate, but which category fits your tools' plans. Automating offboarding without an Enterprise plan compares the routes, and SaaS management for small businesses covers the wider category if you also want to track which tools you pay for.

Common buying mistakes

The first is buying for the logo wall. A long list of integrations says nothing about whether your plan of each tool supports them. Ask about your tools, by name and by plan.

The second is buying the identity provider and forgetting the tool upgrades. The identity provider's invoice is the visible part. The Enterprise plans it needs in each tool can be the larger part.

The third is buying HR software and assuming it removes access. Check whether the IT side is included, sold separately, or missing.

The fourth is skipping the trial run. A product you have not watched remove one real person from your real tools is a product you are trusting on faith.

Where SmashSSO fits

SmashSSO sits in the browser-based automation category. It reads your people from Google Workspace with read-only access and shows an access grid of who has an account in each tool, with what role, matched by email; accounts that match nobody in your directory are flagged. When someone is suspended in Google Workspace it alerts you and shows where they still have access. Removals run through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, in tabs where you are signed in as an admin. Every change is recorded in an audit log.

Measured against the list above, be clear about the gaps. It is not SSO and not an HR system. It needs Google Workspace as your directory. Agent-run removals need your Chrome open, are slower than an API, and can fail when a tool redesigns its screens; a failed run says so and shows its last screenshot. Some tools' terms restrict automated use. It has no SOC 2 report, no spend tracking and no CSV export. It costs a flat fee from $199 a month, billed annually, however many people and tools (pricing). For the full leaving process around it, start from the employee offboarding checklist.

FAQ

What is offboarding software?
Software that runs the steps when someone leaves. HR offboarding software handles the paperwork, such as leaving dates, final pay and documents. IT offboarding software removes the person's access to accounts and devices, through an identity provider, a SaaS management platform or browser-based automation.
Does HR software remove tool access?
Usually not on its own. HR systems record that someone is leaving and run tasks for people to do. Some HR platforms sell an IT module that also removes app accounts, priced on top of the HR product.
How much does offboarding software cost?
Most of it is priced per employee per month. On 27 October 2026, Okta listed its Essentials suite, which includes automated provisioning, at $17 per user a month with a $1,500 annual minimum. SCIM-based removal can also require upgrading each of your tools to a plan that offers SCIM, which often costs more than the software.
Do I need offboarding software for 10 people?
Often not. At that size, Google Workspace as the trigger, a current list of who has access to which tool, and a checklist with a named owner cover most of it. Software starts to pay off when keeping that access list current by hand stops working.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google