Removing a person from a team is not complete if their old session can still export customer records. Offboarding needs a defined access boundary and tests that cover more than the member list.
Separate removal of one organisation membership from deletion of the person's entire account. A consultant may leave one client while retaining legitimate access to another.
Inventory the access that can outlive membership
Review sessions, cached permissions, API credentials, shared links, file URLs, export jobs, scheduled tasks, and support access. For each, record whether removal should revoke it, how that happens, and the expected propagation interval.
Use your identity provider's current session and membership behaviour as an input to the design. Do not assume a valid token always reflects a recent membership change. The application needs a revocation policy that matches its customer commitments.
Test a fictional agency offboarding
Create an account with editor access to Juniper and viewer access to Willow. Before removal, open a Juniper request in one tab, start an export, and retain an attachment link. Then remove only the Juniper membership.
Try reading and changing the Juniper request, submitting the old form, downloading the export, opening the attachment, and using a fresh browser session. Confirm Willow access remains as intended. These checks distinguish targeted offboarding from disabling the whole account.
Decide what happens to work already queued. A report requested while the user was authorised may still finish after departure. The application must define who can retrieve it and whether the job should continue. Rechecking access at delivery can matter even when the original request was valid.
Preserve ownership and history without preserving access
Reassign operational work such as open requests, scheduled reports, or billing responsibilities where necessary. Retain an appropriate historical actor reference for audit records rather than making every past action anonymous when membership ends.
Historical data retention and deletion depend on the organisation's policy and applicable requirements. Keep those decisions explicit; removing access does not automatically imply erasing every record associated with the person.
The tradeoff is revocation freshness versus repeated membership checks and operational complexity. Test the actual interval and document it. A dashboard that updates immediately can still conceal a backend cache that grants access longer than intended.
OWASP's authorisation guidance provides broader review principles. The StackFlight portfolio page supplies related private-workspace context; this offboarding scenario is illustrative.
Questions about SaaS offboarding
Is hiding the organisation enough?
No. Direct requests, file retrieval, exports, and old forms still need the current access decision enforced.
Should all sessions be terminated?
That depends on whether the user is leaving one workspace or the whole service and on the security policy. Avoid breaking legitimate unrelated memberships without a reason.
What proves removal worked?
Record allowed access before removal, denied access afterward, the observed delay, and unaffected legitimate access. Use failures in a permission lifecycle review.