When an employee or contractor leaves, removing one email account is not enough. This small business SaaS offboarding checklist shows what access to revoke, what information to preserve, how to document the change, and which checkpoints to repeat after every departure, role change, or contract renewal.
Overview
Small businesses often add cloud services faster than they build an inventory of them. A departing worker may have access to email, file storage, project systems, accounting tools, code repositories, customer databases, password managers, VPNs, mobile devices, and third-party integrations. Some access is direct; some is inherited through a group, shared login, API token, browser session, or connected application.
The goal of offboarding is not simply to delete a user. It is to end unnecessary access while preserving business records, transferring work, protecting customers, and keeping an audit trail. The order matters: collect required business information, secure accounts, revoke access, rotate shared secrets, and then remove or archive licenses according to the company’s retention needs.
Use a written process rather than relying on memory. The person conducting the offboarding should record the worker’s name, role, departure date, systems reviewed, actions taken, exceptions, and the person who verified completion. This creates a repeatable business account deprovisioning record for employees and contractors alike.
What to track
Begin with an access inventory. Ask the manager, IT administrator, finance lead, and project owners which systems the departing person used. Review the company’s password manager, identity provider, expense records, software bills, browser-managed accounts, and device inventory for additional clues. Do not assume that a user’s job title captures every permission they received over time.
| System or access type | Offboarding action | Verification to record |
|---|---|---|
| Email and calendar | Suspend or disable the account, revoke active sessions, remove forwarding rules, and set an approved handoff or autoresponder. | Account status, session revocation, mailbox owner, and any retention or export decision. |
| Password manager | Remove the user, reclaim shared vault access, review items they created or shared, and rotate credentials that cannot be individually reassigned. | Vaults reviewed, shared secrets rotated, and new owners assigned. |
| Cloud storage and collaboration | Transfer business files, remove direct and group permissions, inspect shared links, and check files owned by the departing user. | File transfer completed and external or public links reviewed. |
| Code repositories and developer tools | Remove organization membership, deploy permissions, personal access tokens, SSH keys, webhooks, and connected applications. | Repositories reviewed, tokens revoked, and production access tested. |
| Accounting, payroll, and payment systems | Disable access, remove approval rights, review scheduled payments, and transfer ownership of invoices, reports, and integrations. | Finance owner confirms access and approval paths are correct. |
| VPN, remote access, and identity systems | Disable the account, revoke sessions and certificates, remove group membership, and check remote desktop or administrative access. | Login attempt or access review confirms the account is inactive. |
| Devices and mobile management | Recover company equipment where applicable, lock or erase managed devices when authorized, remove management enrollment, and document personal-device boundaries. | Asset status, return condition, and management action recorded. |
| API keys and automation | Identify keys, service accounts, scheduled jobs, and integrations created or controlled by the worker. Replace or disable them without interrupting required operations. | Each key has an owner, purpose, replacement, or documented retirement decision. |
| Shared accounts | Change passwords, update recovery email addresses and phone numbers, remove saved sessions, and assign named owners. | Credential rotation and recovery settings verified. |
Pay particular attention to recovery channels. A former user may remain able to reset an account through a personal email address, phone number, authenticator, backup code, or remembered browser session. Review administrator roles as well as ordinary user access. If the departure involves a privileged administrator, have a second authorized person verify the changes.
Separate data handoff from access removal. Before disabling the account, identify active projects, customer conversations, support tickets, contracts, source code, financial records, and operational procedures that another person must receive. Preserve only what the business is authorized and required to retain, and document who approved the handoff.
Cadence and checkpoints
Use three layers of review: event-driven offboarding, periodic access checks, and an annual inventory of business software.
At the time of departure
- Confirm the effective date and time with the responsible manager.
- Record the person’s accounts, devices, roles, shared secrets, integrations, and business data.
- Complete the approved data handoff.
- Disable identity-provider and application access, revoke sessions, and remove group memberships.
- Rotate shared passwords, API keys, recovery methods, and other credentials the person could use.
- Recover or secure company devices and review remote access.
- Have another authorized person verify high-risk systems.
For an immediate or disputed departure, prioritize account suspension, session revocation, privileged access, remote access, payment systems, customer data, and secrets. Preserve relevant logs before making changes if an incident or suspected misuse may be involved. Follow the company’s legal and employment guidance for evidence preservation and communications.
Monthly or quarterly
Compare active users with current staff, contractors, vendors, and approved service accounts. Review administrator roles, external collaborators, dormant accounts, shared accounts, public links, unused licenses, and applications connected to the primary identity provider. Ask system owners to confirm that each account still has a business purpose and the minimum access needed.
A quarterly review is a practical baseline for many small businesses, while higher-risk systems may need more frequent checks. The right interval depends on staff turnover, the sensitivity of the data, the number of integrations, and how quickly permissions change.
At role changes and contractor renewals
Offboarding is also relevant when someone changes teams or when a contract is extended. Remove permissions that belonged only to the previous role, replace temporary credentials, and set a definite end date for contractor access. A renewal should be an explicit approval, not an automatic assumption that old access remains appropriate.
How to interpret changes
Not every change requires the same response. A new application, acquired business, remote-work arrangement, or identity-provider change may create access paths that are not visible in the old checklist. Treat these changes as prompts to update the inventory and assign an owner for the new system.
Several patterns deserve immediate attention:
- Unknown accounts: An account with no clear owner, purpose, or manager approval should be investigated and disabled when appropriate.
- Shared credentials: Repeated use of one login makes attribution and offboarding difficult. Move toward individual accounts and a password manager with controlled sharing.
- Persistent privileged access: Administrative rights that survive a role change indicate a least-privilege gap. Remove the rights or document a current business justification.
- Unowned integrations: An automation tied to a former worker’s token can fail unexpectedly or remain usable after departure. Give every integration a business owner and replacement plan.
- Unusual authentication activity: Unexpected sign-ins, password resets, mailbox forwarding, or new recovery methods should be treated as a possible account-security issue rather than a routine administrative detail.
When access removal affects operations, record the exception instead of skipping the step. For example, a payment integration may need a planned credential replacement, or a project archive may require a named owner before a mailbox is closed. An exception should include the risk, temporary control, responsible person, and deadline.
For related controls, review the password manager migration checklist and the guide to verifying urgent payment and vendor-change requests. These processes help reduce the risk that an offboarding change or account handoff is exploited through stolen credentials or impersonation.
When to revisit
Revisit this checklist for every employee departure, contractor departure, internal transfer, role change, and contractor renewal. Do not wait for the next scheduled review when a privileged administrator, finance user, developer with production access, or person handling sensitive customer information leaves.
Set a recurring monthly or quarterly checkpoint to compare the access inventory with the current organization. Once a year, review the complete SaaS list, including software paid for on company cards, free tools used by teams, browser extensions, automation platforms, and services connected through single sign-on. Refresh the checklist after a major platform change because administrator paths, session controls, audit logs, and integration settings can move.
A simple reusable record can contain these fields:
Person: name and role
Effective date: date and time
Manager and verifier: responsible approver and second reviewer
Systems reviewed: email, storage, code, finance, VPN, devices, APIs, shared accounts, and other tools
Data handoff: recipient and completion status
Credentials rotated: list of shared passwords, keys, tokens, and recovery methods
Exceptions: reason, temporary control, owner, and deadline
Completion: date, reviewer, and outstanding actions
Keep the record in a restricted location and avoid placing passwords or full secret values in it. The strongest small business offboarding process is one that can be followed under time pressure, verified by another person, and improved after each review.