Most organizations use more applications than they realize. Employees may have access to email, collaboration tools, cloud storage, customer relationship management systems, finance platforms, design software, code repositories, analytics tools, password managers, and specialist applications.
When someone leaves, disabling their primary account may not remove every route back into company data. Local accounts, API tokens, shared credentials, personal-device sessions, and third-party integrations can remain active.
A reliable SaaS offboarding process starts with an inventory and ends with verification. This guide pairs with our IT offboarding checklist, which covers devices and wider IT tasks.
Build an Accurate Application Inventory
Start with the organization's identity provider, software asset inventory, procurement records, IT service desk, expense records, and department-level application lists. Ask managers and system owners about tools that may not appear in central IT records.
For each application, identify the business owner, technical administrator, authentication method, data sensitivity, account type, and deprovisioning procedure. Record whether access is individual, shared, privileged, or service-based.
Do not assume that every employee uses only the applications assigned by IT. Shadow IT and project-specific tools can create gaps.
Identify Every Form of Access
Review more than the visible user account. Depending on the application, access may include:
- Primary user accounts and administrator roles.
- Active browser and mobile sessions.
- Single sign-on assignments and group memberships.
- Personal access tokens, API keys, and OAuth grants.
- SSH keys, certificates, and device registrations.
- Shared mailboxes, distribution lists, and collaboration spaces.
- External guest accounts and partner workspaces.
- Password-manager entries and shared credentials.
The system owner should determine which items must be disabled, revoked, rotated, transferred, or retained for continuity.
Coordinate Timing With HR and IT
The exact timing depends on the departure type, risk, contract, and local requirements. For a planned resignation, some access may remain necessary until the final working time. For a high-risk or involuntary departure, the authorized response may require coordinated changes at a specific moment.
Use a confidential, approved process to coordinate HR, the manager, IT, and security. Avoid sharing sensitive departure details with people who do not need them. Define a clear time zone and effective timestamp when teams operate across locations.
Disable Access and Revoke Sessions
Follow each application's documented deprovisioning process. Disabling the central identity may trigger automatic removal from connected applications, but verify that the integration covers the account and access type in question.
Where appropriate, revoke active sessions, refresh tokens, personal access tokens, API keys, and other credentials. Remove group memberships and privileged roles. Rotate shared credentials if the departing employee knew them, and update recovery methods that relied on the person's phone or email.
For systems that cannot be disabled immediately, document the reason, interim safeguards, approver, and deadline.
Transfer Ownership Without Sharing Passwords
Employees may own documents, calendars, dashboards, repositories, workflows, customer records, or billing accounts. Identify these before disabling access.
Use each service's approved ownership-transfer or administrator-recovery process. Do not ask employees to disclose personal passwords, and do not make a colleague impersonate the departing employee. Preserve business records according to the organization's retention and legal-hold policies.
Verify the Result
A completed ticket is not proof that every application is secure. Ask each system owner or authorized administrator to confirm the relevant action. Where available, review identity-provider events, application logs, and access reports.
Check for exceptions such as dormant accounts, local logins, service accounts, external invitations, or integrations that were missed. Keep evidence references in the offboarding record, not passwords, tokens, or unnecessary personal data.
SaaS Access Removal Checklist
- 1.Confirm the authorized departure and effective time.
- 2.Identify applications from central and department-level inventories.
- 3.Identify privileged, local, guest, and service-account access.
- 4.Review SSO groups and application assignments.
- 5.Disable accounts at the approved time.
- 6.Revoke sessions, tokens, keys, and OAuth grants where appropriate.
- 7.Remove group memberships and administrator privileges.
- 8.Transfer ownership of business-critical resources.
- 9.Rotate shared credentials and update recovery methods.
- 10.Verify actions with system owners.
- 11.Document exceptions and close them with an owner and due date.
Can SaaS Offboarding Be Automated?
Identity and access management tools can automate deprovisioning for connected applications. Workflow software can coordinate the people and approvals involved, assign system owners, track exceptions, and retain completion references.
Automation is only as complete as the integrations and inventory behind it. Test what happens when an application is not connected to single sign-on, when a user has multiple identities, or when a token exists outside the central identity platform.
FAQs
Is disabling email enough when an employee leaves?
No. Email is only one access point. Review every application, device, credential, session, and third-party workspace the employee could use.
Does single sign-on remove all SaaS access automatically?
Not always. It depends on the application integration, account type, provisioning configuration, and any local or non-federated access.
Should access be removed before the employee's last day?
Timing should follow the authorized departure plan and risk assessment. Coordinate changes with HR, IT, security, and the manager.
What happens to files owned by a departing employee?
Transfer business ownership through approved administrative procedures and apply the organization's retention, privacy, and legal-hold requirements.