How to Automate Rippling Offboarding and App Deprovisioning
A Rippling offboarding workflow revokes app access, collects devices, and processes final payroll when a termination date fires. Build it under Workflow Studio → Offboarding, triggered by Termination Date rather than an employee status change.
Use the date trigger. Status changes fire when HR clicks the button, which is usually late on the last day and sometimes after the person has already left the building. A termination date lets you fire account revocation at hour zero of the last day, while payroll tasks run days later.
What should an offboarding workflow actually do?
The security-critical items first, in this order:
- Suspend app access across your connected app catalogue — email, Slack, GitHub, Figma, your SSO provider.
- Disable device access via MDM — this locks the laptop and can wipe it on next check-in.
- Revoke physical access if you have badge integration.
- Add to a distribution list or manager task for device return.
- Process final payroll and COBRA tasks at their own offsets.
The ordering is not cosmetic. If you revoke SSO before you have captured their device, the machine stays unlocked and locally logged in. Suspend app access but leave the device enabled until you have recorded the serial number and return address.
How do you build it in Workflow Studio?
- Go to Workflow Studio → Create Workflow → Offboarding.
- Set the trigger: Termination Date with offset
0 days. - Add a Deactivate App Access action. Rippling lists every app in your catalogue; select all except any explicitly excluded (more on that below).
- Add a Remote Lock / Device Action step with a 1-day offset so it does not race the access revocation.
- Add a Task action assigned to the manager: “Collect laptop and badge by [date]”.
- Add a Payroll action with an offset based on your final payroll cycle — often 5 to 10 days out.
- Publish, then test with a dummy employee profile.
The exclusion list that saves your bacon
Shared accounts are the trap. If the departing employee owns the company’s admin@ mailbox, the AWS root-adjacent account, or the shared billing login, deprovisioning them breaks the account for everyone. Build an explicit exception list before you run this live: any account where the employee is the only admin gets reassigned first, and the workflow excludes it.
Rippling’s offboarding documentation covers device and app actions but will not catch your organisational dependencies. That audit is on you.
What does the app catalogue actually reach?
Rippling connects to a catalogue of thousands of apps, but the depth varies. Some support full provisioning and deprovisioning via SCIM (Okta and Google Workspace integration channels, Slack, GitHub, most of the modern SaaS stack). Others are “configured in Rippling, actioned manually” — Rippling creates a task for IT rather than revoking anything.
Check each critical app’s integration depth under App Management → [App] → Integration. If it says manual, the automation is a reminder, not a control. For those, direct users through SSO so revocation at the identity layer covers the gap.
| Integration depth | What happens on termination |
|---|---|
| Full SCIM | Account suspended in the app automatically |
| SSO only | Access blocked at login; account still exists |
| Manual | Rippling creates an IT task, nothing automated |
How fast should access die?
Within minutes of the termination timestamp, ideally. In practice most companies accept under an hour. If your workflow fires on a date at midnight and your termination is “end of day,” you have a problem: the person works all day with no email.
Fix: set the offset so revocation happens at the start of the day after the last working day, not on it. Or have the manager set the termination date to the day after the last shift and communicate that clearly.
What breaks in practice?
- Locked-out admin. The departing person was the only Rippling admin. Designate two admins at all times.
- Contractors without termination dates. If nobody sets an end date, the workflow never fires. Set default end dates at contractor creation.
- Device never returned. Add an escalation task at T+14 days; the MDM wipe is your fallback.
- Payroll errors. Final pay after a lump-sum vacation payout needs review; do not trust the default calculation.
Who should not automate this fully?
The first five departures at a company should be handled partly manually. You will discover shared accounts, forgotten integrations, and weird permission chains that no workflow anticipates. Automate after you have run the process by hand and know where it snags.
If you are on Rippling for payroll only and your IT stack is not integrated, the offboarding workflow gives you tasks, not revocation. In that case the honest answer is that your SSO provider is the real control point.
Key Takeaways
- Trigger Rippling offboarding on the Termination Date, not a status change, so revocation fires on time.
- Revoke app access before locking devices, and record device serials before any wipe.
- Shared accounts owned solely by the departing employee must be reassigned before the workflow runs.
- Only SCIM-integrated apps are truly deprovisioned; SSO-only and manual apps need SSO enforcement or tasks.
- Always keep at least two Rippling admins so offboarding cannot lock out the company.
