A staff departure can reveal how much information depends on one person’s account. Customer threads, planning documents, and shared links need a deliberate handover. Rushing to delete an account can make a manageable transition much harder.
Identify the work that needs continuity
Before changing access, list ongoing customer conversations, files, calendars, and tools connected to the account. Decide who will take responsibility for each. Ask the business owner about retention needs and any limits on access to the departing person’s information. Record these decisions rather than leaving a replacement employee to search through everything later.
Separate access changes from information handling
Account sign-in, file ownership, and incoming messages are related but different tasks. Have an authorised administrator plan them in the right order. Team files in shared drives remain with the team when someone leaves; files in personal working areas need a separate review. Do not assume that removing a person from one shared folder removes every route of access.
Test the handover from the replacement’s account
Check that the new owner can reach the agreed documents and respond through the intended channel. Review outside collaborators, shared links, and third-party tools as part of the agreed scope. Document what was transferred and what was retained. Apply the same checklist to future departures so that business continuity does not depend on an improvised cleanup.
Agree what happens before deletion
An administrator can suspend an account to block the user's access while its data remains. Google also blocks new email and calendar invitations for an administrator-suspended account, so suspension alone is not an incoming-mail handover. Agree how future messages will reach the responsible team, which existing information must be retained and who may access it. File ownership transfer does not by itself move Gmail messages or every connected application. Have the administrator confirm the required transfers and retention arrangements before deletion, then test the approved mail route and documents from the replacement account. Record the authorised decision and outcome without putting passwords or private message content in the handover note.
Make it actionable
Your next steps
- Name the owner of ongoing work and future incoming messages.
- Review files, mail, calendars and connected tools separately.
- Agree retention and verify required transfers before deletion.
- Test the replacement's access and approved incoming-mail route.
Official reference
Google: Delete or remove a user from your organization
Guide date: September 29, 2026. Product features and requirements can change. The business checklists above are practical suggestions from Cyber Bounds.
Put the next step into practice
Help with google workspace.
Business email, shared files, and calendars set up around the way your team works. Tell us about your situation and we’ll discuss a suitable scope and quote.
Email us about this guide