> ## 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.

# Understand offboarding settings

> Set how far back past leavers are offboarded and when each offboarding step runs relative to an employee's last day.

Offboarding settings decide when Primo acts after an employee's departure date arrives from your HR system. Go to **Employees > Settings** and open the **Offboarding** tab.

The tab opens with the **Create offboardings for past leavers** card, then has one card per step. Each step card sets a **Scheduling** relative to the employee's last day. To configure what each step does, see [Automate your offboardings](/employees/automated-offboardings).

<Info>
  **How changes save:** unlike the Onboarding tab, the Offboarding tab saves with the **Confirm** button at the bottom of the page.
</Info>

## Past leavers

By default, Primo only offboards employees whose departure date is today or later. A leaver whose departure date has already passed when your HR system syncs, for example a departure entered late in the HR system or an employee synced for the first time, gets no offboarding.

The **Create offboardings for past leavers** card sets how far back Primo still offboards them. When the departure date falls inside the selected window, counted back from the day of the sync, Primo creates the employee if needed and starts their offboarding.

| Option | Departures still offboarded |
| - | - |
| **Disabled** | None (default) |
| **Last 7 days** | Departure date in the last 7 days |
| **Last month** | Departure date in the last month |
| **Last 3 months** | Departure date in the last 3 months |
| **Last 6 months** | Departure date in the last 6 months |
| **Last year** | Departure date in the last year |

The setting applies to the whole company, whichever HR system the leaver comes from. It saves with the **Confirm** button, like the rest of the tab.

## Offboarding steps

| Step | Shown when | What it schedules |
| - | - | - |
| **Deprovisioning** | SaaS Management is enabled | When accounts are deprovisioned relative to the employee's last day |
| **Equipment** | Device management is enabled | When device offboarding actions run relative to the employee's last day |

## Scheduling

Each card has a **Scheduling** field made of two parts:

* **A day** relative to the last day: **One month before**, **Two weeks before**, **One week before**, **One day before**, **The D-day**, **One day after**, **One week after**, **Two weeks after**, or **One month after**.
* **A time**, in 30-minute steps.

<Note>
  A step with no scheduling set runs on **the D-day** at **18:00**.
</Note>

## Offboardings as tickets

Offboardings can be tracked as tickets, the same way as onboardings. Each offboarding then opens a ticket titled *First Last - Offboarding*, with one task per step:

| Task | Created when |
| - | - |
| **Offboarding details** | Always, first |
| **Deprovision apps** | The offboarding has SaaS accounts to remove |
| **Handle equipment** | The employee has devices to recover |
| **Handle shipping** | A return shipment is needed |

Deprovisioning can split into one task per SaaS: **Deprovision {app}** when Primo removes the account, or **Remove account for {employee} on {app}** when you remove it yourself.

<Info>
  Offboarding as tickets is rolling out to accounts. If your offboardings don't open a ticket, the new model isn't enabled for your organization yet — contact your Primo representative.
</Info>

## Related articles

* [Automate your offboardings](/employees/automated-offboardings)
* [Understand onboarding settings](/employees/onboarding-settings)
* [Set up HR sync](/employees/set-up-hr-sync)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.