Offboarding Overview
Ploy automates employee offboarding to securely remove access when team members leave. The platform deprovisions accounts, revokes permissions, and removes users from groups across your stack.
What Happens During Offboarding
When an offboarding starts, Ploy creates tasks for account owners to:
Revoke SSO and OAuth access — SSO sessions terminated, OAuth tokens revoked
Remove from groups — User removed from teams, channels, and permission groups
Block login credentials — Email/password accounts disabled or deleted
Transfer admin rights — Admin or ownership roles reassigned before removal
Ploy tracks each action with timestamps and who completed it, creating a full audit trail.
How It Works
When an employee's end date is set in your HRIS, Ploy can automatically create an offboarding process. You configure which account types to include (SCIM, SSO, OAuth, email/password apps), and Ploy:
Gathers all matching accounts for the departing employee
Schedules offboarding to start on their end date
Assigns tasks to account owners to revoke access
Tracks completion as owners mark actions done
If no accounts match your filters, the offboarding auto-completes.
Offboarding Tab vs. Offboarding Flows
Offboarding Tab is your monitoring dashboard. View all current offboardings, track progress, manually create urgent offboarding with "New Offboarding," and export reports.
Offboarding Flows are automated workflows. Set triggers (like HRIS end dates), define which account types to include, and schedule when offboarding starts. Flows run automatically for routine departures.
Use flows for automation, the tab for visibility and control.
Next Steps
Set up an offboarding flow to automate future departures