What happens to a license’s reminders when someone leaves the company

A license doesn’t stop needing to be renewed just because the person who held it, or the person who was responsible for renewing it, has moved on. What happens to its reminders at the exact moment someone leaves the workspace matters as much as what happens to their login — a renewal that quietly goes silent because its owner was removed is worse than one that was never assigned in the first place, because it looks handled right up until it isn’t.
Instant, not eventual
Removing a team member cuts their access to the workspace immediately, and any license that was assigned to them is reassigned at the same time rather than left pointing at an account that no longer has access — to the workspace’s owners by default, the same rule that covers any license with no one named on it at all.
This happens automatically, the moment the removal is confirmed, which is the part that matters: there’s no gap between someone losing access and their licenses still quietly waiting on them.
What to check right after
The default keeps nothing orphaned, but it also isn’t necessarily where the license should end up long-term — the owners now technically hold it, but they’re probably not the ones who should be doing the actual renewal work going forward.
Right after someone leaves is the moment to go back through what was reassigned and hand each license to whoever is actually taking over that part of the work, rather than leaving everything sitting with the owners by default indefinitely. It’s a five-minute cleanup task that’s easy to skip in the moment and awkward to discover was skipped three months later.
A good habit for any departure
Treat the reassignment step as part of offboarding, the same as collecting a laptop or revoking a badge: before removing someone, or right after, review what’s assigned to them and decide where it goes. That turns a system default into a deliberate handover instead of an accident you discover later.
The same logic applies to a role change, not just a departure
Someone doesn’t have to leave the company for this to matter — a staff member moving to a different part of the business, or taking on a different set of responsibilities, is the same moment to revisit what’s assigned to them. The default reassignment rule only triggers on removal, so a role change within the team is a manual check worth doing deliberately.
Why the instant handoff matters more than it seems
The alternative — a license sitting assigned to someone who no longer has access, with reminders going to an inbox nobody checks anymore — is the kind of gap that’s invisible until the renewal is already overdue. There’s no dashboard warning for “assigned to someone who left”; the reassignment rule exists precisely because that situation should never be allowed to happen in the first place.
A short checklist for the week someone leaves
- Confirm what was reassigned to the owners, and reassign it again to whoever’s actually taking it over.
- Check whether the person who left was the only recipient on any reminder, not just the assigned owner.
- If they were a watcher on anything, decide who should pick that up too.