When an employee or contractor leaves, immediately block their ability to sign in, preserve required business data, transfer ownership of important work and then remove unnecessary access. Do not begin by deleting the email account: deletion can make files, messages, automations and customer records harder to recover.
First, diagnose what the person could access
Create an inventory before making changes. Check the identity provider or email platform, but do not assume it contains every account. Small businesses often grant access directly inside websites, social networks, accounting tools and vendor portals.
| Area | What to identify |
|---|---|
| Core identity | Microsoft 365, Google Workspace, single sign-on, VPN and remote desktop |
| Business systems | CRM, accounting, scheduling, support, storage and automation platforms |
| Marketing assets | Website, domain registrar, hosting, analytics, advertising, social media and Google Business Profile |
| Privileged access | Administrator roles, API keys, recovery methods and shared passwords |
| Property | Laptops, phones, security keys, storage devices, badges and physical keys |
Review browser password managers, team documentation and expense records for subscriptions that may not appear in the central directory. Ask the employee’s manager which files, client relationships and recurring processes must continue.
Recommended offboarding sequence
1. Coordinate the timing and assign responsibility
HR, management and the person handling IT should agree on the effective time. For an involuntary separation, access may need to be disabled before or during the meeting. Record who is authorized to approve data transfers, mailbox access and changes to customer-facing accounts.
2. Block sign-in and terminate active access
Suspend or block the primary account, revoke active sessions and remove remote access. Reset credentials when a platform cannot invalidate existing sessions promptly. NIST guidance for personnel termination and transfer calls for disabling system access, revoking credentials and retrieving security-related property.
Platform procedures differ. Google documents how administrators can suspend a Workspace user without immediately deleting data. Microsoft provides a broader former-employee removal sequence covering sign-in, email, files, devices and licenses.
3. Remove privileges beyond the main account
Remove administrator roles, delegated mailbox access, VPN certificates, application passwords, OAuth connections, API tokens and recovery email addresses. Check accounts that use a personal email or phone number. If the person knew a shared password, change it and update the approved password manager rather than sending the replacement through email or chat.
4. Preserve and transfer business information
Assign another authorized person to own required documents, calendars, reports, website assets and automations. Redirect customer communications where appropriate, but avoid impersonating the former worker. Confirm retention requirements with qualified legal or compliance advisers before deleting records or wiping devices.
5. Recover equipment and inspect automations
Collect company devices and security keys, then verify encryption, remote-management status and stored business data. Review scheduled reports, form routing, payment notifications, calendar bookings and workflows owned by the departing account. An automation may stop when its owner is suspended, even if the visible website remains online.
6. Monitor and document the result
Review sign-in and administrator logs for unexpected activity. Record the accounts disabled, data transferred, equipment returned, shared credentials changed and unresolved items. CISA’s identity and access management guidance recommends managed account governance and supports automating account disablement where practical.
Common offboarding mistakes
- Deleting the mailbox before transferring files or customer communication.
- Removing a software license without first blocking sign-in and sessions.
- Forgetting website, domain, social media or Google Business Profile access.
- Leaving the former worker in groups, shared drives or password vaults.
- Failing to change shared credentials and recovery methods.
- Assuming returned equipment contains the only copy of company data.
What to verify after the changes
- The former account cannot sign in from a private browser or managed device.
- Another authorized user can reach required email, files and calendars.
- Forms, bookings, notifications and automations still reach the right team.
- No customer-facing profile lists the former employee as an owner or manager.
- Logs, devices, licenses and outstanding tasks have been documented.
- A follow-up access review is scheduled after several business days.
This checklist is operational guidance, not legal or regulatory advice. Retention, privacy, labor and contractual requirements vary by organization and data type.
Need help closing access gaps?
CyberTek Group can review account administration, cloud access, devices and offboarding procedures as part of an IT and cybersecurity engagement. Explore additional implementation checklists in our business technology resource center.






