Never miss an app when a colleague leaves.
A former colleague who can still get into an app can get to the data, and the license keeps running. A security risk and unnecessary costs. Offboarding in Mapit lets you revoke access on a chosen date and then check off, per app, whether the license has been cancelled.
What offboarding with Mapit gives you
One overview of all apps per employee
Apps behind the work account can be found in the workspace. Apps with a separate password are not listed anywhere, so only that colleague knew which ones they were. In Mapit they are together on one list, for each departing employee.
No more figuring out who did what
When someone leaves, one person handles the access and another the license, and who that is differs per organization. Figuring out who does what and what the status is takes the most time. From now on everyone looks at the same overview and sees which step is still open.
From revoking access to cancelling the license
Revoking access is the first step, cancelling with the vendor the second. Skip that second step and the payments continue while the license goes unused. You click through to the vendor for each app and then check it off, so the count of cancelled licenses is accurate.
Proof that the process was followed
An auditor wants to see which steps you took, and when. You export the activity log per employee and the overview in which former employees remain listed as evidence. See also SaaS inventory.

Connect and done: one connection to Google Workspace or Microsoft 365 plus a browser extension, no IT project. The overview stays accurate without anyone maintaining it. No lists, no credit card statements, no finance admin, no digging around.
Every last working day wrapped up, down to the cancelled license.
Frequently asked questions
Why do accounts stay open after someone leaves?
Because nobody has a complete picture of what that person used. Apps someone bought on their own or used with a separate password are not on any list, so there is nothing to check off. What nobody sees does not get revoked.
What does Mapit do when a colleague leaves?
All the apps that person had access to are in Mapit. On the date you choose, the access is revoked, and for each app you check off whether the license has been cancelled with the vendor. If anything is still open, you get an email reminder about it.
Does this also work for apps with a separate password?
Yes. Apps behind the work account close along with that account, through SSO. Apps with a separate password are separate actions and are listed as tasks, so they are not forgotten and you can track the progress.
What if someone still signs in somewhere after leaving?
Revoking access breaks the link between that person and the app. As long as the account exists with the vendor, someone can sign in again. If that happens, Mapit flags it on the dashboard for that app. That is your signal to delete the account with the vendor or cancel the license there, because only then is it really closed.
Can I show in an audit that it was done?
Yes. For each employee there is an activity log with a timeline of what happened and when, and you export it together with the overview as CSV.
What if someone left months ago?
Mapit shows everyone who could ever sign in to an app and whose access was never revoked or whose license was never cancelled, even if they left a long time ago.
