Use cases → Admin and governance
Hand over a departing employee's mail and files
Transfer ownership, set forwarding and preserve what matters before the account is suspended.
| Who it is for | IT and managers handling departures. |
|---|---|
| APIs | Admin SDK, Drive API, Gmail API |
| Typical scopes | admin.directory.user, drive, gmail.settings.basic |
The problem
Suspend too early and live work is lost. Leave it too long and an unmonitored mailbox quietly buries customer messages for months.
How it works
- Transfer Drive ownership to the manager or a durable account.
- Set forwarding or delegation so inbound mail reaches a person.
- Export what compliance requires.
- Only then suspend.
What changes
Nothing is lost, and no customer writes into a mailbox nobody reads.
Questions people ask
What about shared aliases on their account?
Move them first. Aliases living on a departing person's mailbox are the most commonly missed step.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Automate joiners, movers and leavers
Create accounts, set group membership, provision Drive and hand over mailboxes without a manual checklist.
Continuously verify your delegation still works
A scheduled probe that proves every API still answers under every tenant, before a customer finds out otherwise.
Reduce an over-broad delegation grant safely
Find out which scopes your automation genuinely uses, then cut the grant down to them.