Start with a conversation.
Bring the case into your team’s Switch room. Investigate together, with the person and the provider account in clear view.
A clear exit. A verifiable outcome.
People move on.
Their access
should, too.
Find forgotten access. Review the decision with your team. Know what was removed—and what still needs attention.
Human-approved actions. Independently checked results.
Workflow overview
Offboard.Conversation → evidence
A shared Switch room
The investigation starts here.
Inspect the access
Provider permissions
Review the action
Administrator approval
Recheck. Record. Resolve.
The outcome and everything still open.
One case. A shared understanding.
Less chasing checklists.
More knowing where things stand.
Offboarding brings people, permissions, and decisions together. The evidence should stay together, too.
Make the decision human.
Review the discovered permission and the exact proposed removal. An authorized administrator decides what happens next.
Keep the evidence.
Check the provider again after the action. Keep the result, the approval, and the unresolved scope together.
The record behind the result
“Done” deserves
a little more detail.
A successful API response is a starting point. A verification report should explain the action, the fresh check, and the limits of what was verified.
One verified permission never means every company account is cleared.
- The person
- A confirmed account and stable provider ID.
- The permission
- The organization, access type, and checked scope.
- The decision
- The exact correction and who authorized it.
- The operation
- What was requested and what the provider returned.
- The fresh check
- What a separate scan found after the action.
- The unresolved
- Everything unavailable, unchecked, or still accessible.
Deliberate by design
Keep the conversation open.
Keep the authority clear.
A conversation can start an investigation.
Switch gives your team a shared place to ask questions and review findings. A room message alone cannot authorize a removal.
Approval belongs to an administrator.
Review one account, one permission, and one action in the authenticated workspace. Each approval expires and can be used once.
Uncertainty stays visible.
If access remains or a provider cannot be checked, the case keeps that unresolved scope. A failed check never becomes a green status.
Start with GitHub
The access you can actually inspect.
Connect an organization you administer. Investigate membership and outside-collaborator access using real provider records, with owners and protected accounts kept out of removal targets.
A clear boundary for every check.
The organization, account, permission sources, and check time belong in the report. Other providers and unchecked access remain outside that result.
Bring clarity to the last day.