Skip to main content
Prerequisites:
  • Your HR system must be connected so that Primo can detect departure dates. See Set up HR sync.
  • The Offboarding date field must be set to Sync continuously in Settings > HR System > Per-field sync settings. Otherwise, departure date changes aren’t picked up automatically.
Once configured, offboardings start automatically when a departure date arrives. This article covers what each step does. For the page layout and its scheduling options, see Understand offboarding settings. Go to Employees > Settings, open the Offboarding tab, set each step, and click Confirm.

​
The offboarding ticket

When offboardings are tracked as tickets, each offboarding opens a ticket titled First Last - Offboarding — when your HR system reports the departure, or when you save the offboarding information yourself. The steps below then appear as tasks on that ticket. See Offboardings as tickets.

​
Deprovisioning

This step appears only when SaaS Management is enabled. It requires Google Workspace or Microsoft Entra to be connected. See Connect your email provider.
Default timing: see Scheduling. On the scheduled date, Primo removes access to the connected SaaS using SCIM or API integrations. For Google Workspace and Microsoft Entra, this also suspends the employee’s account and can transfer data — Drive files, email ownership — to a designated recipient.

​
Equipment

This step appears only when device management is enabled.
Default timing: see Scheduling. Device offboarding actions include:
  • Sending a return shipment label to the employee
  • Triggering an MDM unenrollment command
  • Moving the device back to stock or archiving it
Wipe a device before reassigning it. See Wiping devices.