Offboarding is where manual project administration gets tense. A user may be present in dozens of projects, some active and some archived. The business wants access removed quickly, but the admin still needs to avoid touching the wrong account or removing the wrong person.
The right workflow is intentionally plain: find the user, review the project list, group the targets, preview the removals, execute in bounded batches, and keep evidence.
Start with visibility
Before removing anything, the operator needs an account-level view of where the user appears. Project-by-project clicking creates gaps because the admin is relying on navigation and memory instead of an inventory.
Group project targets
Not every project should be treated the same. Active delivery projects, archived projects, templates, and exception projects may need different handling. A good offboarding workflow lets the operator group targets before execution.
Use small batches
Even when the final goal is broad removal, small intentional batches are safer than one giant operation. They make failures visible and give the admin a clean pause point if the account state does not match expectations.
Keep the evidence record
When someone asks why access changed, a vague answer is not useful. The useful answer is the operation record: who ran it, when it ran, which projects were targeted, which rows succeeded, and which rows were skipped.