> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate your offboardings

> Configure Primo to automatically handle the full offboarding journey — SaaS deprovisioning, email suspension, and equipment retrieval — triggered by departure dates from your HR system.

<Info>
  **Prerequisites:**

  * Your HR system must be connected so that Primo can detect departure dates. See [Set up HR Sync](/employees/set-up-hr-sync).
  * The **contract end date** field must be set to **Continuous synchronization** in your HR system settings — otherwise departure date changes won't be picked up automatically.
</Info>

<Info>
  **Coming soon:** Full offboarding automation — including one-click deprovisioning across all connected apps, automated equipment return, and MDM wipe — is on the roadmap. The steps below cover what's configurable today.
</Info>

Once configured, offboardings are triggered automatically when a departure date arrives. Each step below corresponds to a configuration step in **Settings > Offboardings**.

## Step 1 — Deprovisioning

Configure when and how employee SaaS access is revoked at offboarding.

<Info>
  This step requires Google Workspace or Microsoft Entra to be connected, and the **email provider** toggle to be turned on. See [Connect your email provider](/saas/get-started/connect-email-provider).
</Info>

### Scheduling

Choose when accounts should be deprovisioned relative to the employee's last day. Default: the day of departure (D-day) at 19:00.

When triggered, Primo deprovisions access to all connected SaaS applications 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.

### Processing options

* **Manually** — deprovisioning is triggered manually by an admin.
* **Automatically process** ✦ Recommended — Primo automatically deprovisions access based on the schedule above.
* **Automatically skip** — the deprovisioning step is skipped entirely for all offboardings.

## Step 2 — Equipment

Configure when device offboarding actions are scheduled relative to the employee's last day.

### Scheduling

Choose when device offboarding actions should run. Default: the day of departure (D-day) at 19:00.

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

<Info>
  It is recommended to wipe a device before reassigning it. See [Wiping devices](/mdm/guides/wiping-devices).
</Info>

### Processing options

* **Manually** — equipment offboarding actions are triggered manually by an admin.
* **Automatically process** ✦ Recommended — Primo automatically triggers equipment offboarding actions based on the schedule above.
* **Automatically skip** — the equipment step is skipped entirely for all offboardings.

## Related articles

* [Set up HR Sync](/employees/set-up-hr-sync)
* [Automate your onboardings](/employees/automate-onboardings)
* [Connect your email provider](/saas/get-started/connect-email-provider)
* [Wiping devices](/mdm/guides/wiping-devices)