An employee offboarding IT access checklist helps a business close access paths without losing track of important work or records. Disabling a person’s main account is a useful start, but it may not remove direct logins to business apps, end active sessions, or change shared credentials they knew.
Plan the cutoff with the appropriate business and IT contacts. Separate the immediate access change from later tasks such as transferring work, preserving business records, and closing accounts that are no longer needed. For sensitive or involuntary departures, follow the organization’s established procedures and consider the CISA guidance on employee separations.
Before the departure: identify access and owners
Start with a list of the person’s systems, credentials, devices, and physical access. Use an access inventory if one exists, then check with the manager and system owners for anything missing. Look beyond the standard employee account: people often have separate logins for tools they use in a specific role or project.
- Confirm the cutoff plan. Coordinate the effective time and responsibilities with the appropriate business contacts. Decide who will handle the account changes, device return, work handoff, and verification.
- Identify systems and data. Include email, file storage, collaboration tools, finance or operations software, customer platforms, cloud services, vendor portals, and any role-specific applications.
- Find elevated access. Check for administrator accounts, server or network access, cloud consoles, service accounts, and permissions to manage other users.
- Locate physical access. Identify keys, access cards, alarm credentials, and any other method used to enter a workplace or restricted area.
- Note shared secrets. Ask which shared passwords, recovery methods, API keys, or other credentials the person knew or could retrieve.
For organizations with remote staff or multiple locations, include systems and equipment outside the main office. A useful companion is this guide to IT support for remote work, which can help frame the remote-work access paths to review.

At the cutoff: remove access by access path
Identity, email, and business applications
Disable sign-in for the employee’s primary identity account at the agreed cutoff. Then review business applications separately. Some services use a direct username and password or a separate administrator, so they may not follow changes made to a central identity account.
Remove the person from relevant groups, shared mailboxes, file-sharing permissions, collaboration spaces, and application roles. Check account recovery options and delegated access as well. Preserve business records and transfer ownership of work according to company procedures before deleting accounts or data. An account can be disabled while the organization retains the information it needs.
Sessions, tokens, and registered devices
Disabling future sign-ins and ending an existing session are not always the same action. Where the service offers it, revoke active sessions or sign-in tokens and review registered devices. Microsoft’s guidance on revoking user access in an emergency explains the available controls for Microsoft Entra ID. Other services may have separate session or device controls, so check their own administrative settings.
VPN, remote desktop, and other remote routes
Remove access to the company VPN, remote desktop tools, remote management platforms, and any other route into business systems. Check for direct access to servers, network equipment, cloud environments, or a work device that can connect remotely. If the employee used a personal device for work, review the organization’s approved process for removing company access and data from it.
Remote access should be checked independently rather than assumed to disappear with email or a main account. This is especially relevant when work takes place across multiple locations or from outside the office.
Administrator and privileged accounts
Remove elevated roles and disable separate administrator accounts that belong to the departing person. Review access to systems that can create users, change security settings, manage backups, or administer networks and cloud services. If the person controlled an account used by others, assign a new approved owner and confirm the new owner can perform the required work.
Shared passwords, keys, and authentication methods
Disabling a named account does not change a shared credential. Identify shared passwords and secrets the person knew, then rotate or reassign them through the organization’s approved password or secrets manager. Update the record of who owns each credential. Review authentication methods and recovery options associated with business accounts, and remove methods that should no longer be available to the departing person.
Physical access, devices, and tokens
Recover company computers, phones, storage devices, access cards, keys, and authentication tokens. Record what was returned and what remains outstanding, then follow the organization’s process for handling, reviewing, or reassigning each device. If a token cannot be recovered, disable or replace it using the relevant system’s controls.
Also check that company-owned devices are no longer registered for access where the service provides that option. For remote or multi-site operations, arrange a clear return process and confirm which location or contact will receive the equipment.
After the cutoff: verify and document completion
Do not treat a sent request as proof that access has been removed. Ask each system owner or responsible administrator to confirm the change. For every system, record who completed the action, when it was completed, and what evidence supports the closeout. Evidence might include an account status, a session-revocation record, confirmation that a device was returned, or a note from the system owner.
- Compare the completed work with the access inventory and role-specific system list.
- Check for separate logins, administrator accounts, vendor access, and shared credentials that were not covered by the primary account change.
- Confirm that active sessions, tokens, and registered devices were addressed where the system supports those controls.
- Document equipment returned, credentials rotated, business ownership transferred, and any open follow-up task.
- Arrange a follow-up review for systems whose access status cannot be confirmed immediately.
This record gives managers and IT a clear closeout trail and helps reveal gaps in the offboarding process. A broader cybersecurity practices review can also help a business keep access controls and account ownership organized between departures.
Frequently asked questions
When should an employee’s access be revoked?
Coordinate the cutoff with the appropriate business contacts and carry it out at the agreed time. The timing and steps may depend on the circumstances and the organization’s established procedures.
Does disabling an account end active sessions?
Not necessarily. Check whether each service has a separate option to revoke sessions or tokens, and verify the result where possible.
What access should be removed when a contractor leaves?
Use the same access-path review: identity accounts, applications, remote connections, privileged roles, shared credentials, devices, and physical entry. Also confirm who owns any work or accounts the contractor managed.
Are there extra offboarding steps for healthcare organizations?
Review access to systems and information based on the person’s role, and follow the organization’s established security and compliance procedures. Include application owners in the verification and documentation process.
Make offboarding a repeatable process
A complete offboarding process covers named accounts, direct application logins, remote access, shared secrets, physical entry, and company devices. It also separates immediate access removal from the later work of preserving records and transferring ownership.
Turn the checklist into a repeatable process with a clear owner for each system and a confirmation step. If your business needs help reviewing access paths or documenting its IT processes, contact Zevonix to discuss your support needs.