Skip to main content
Offboarding settings decide how Primo handles every leaver: when the offboarding ticket opens, who owns it, and which steps run on it. Go to People > Settings and open the Offboarding tab. The tab has two sections: Ticket information, applied to every offboarding ticket, and Offboarding tasks, the steps that run on it, scheduled from the employee’s last day. To follow an offboarding once it runs, see Offboard an employee with the offboarding ticket.
The Offboarding tab of People > Settings: the Ticket information section, then the four offboarding tasks with their Automatic or Manual chips.
Availability: the offboarding ticket is rolling out to accounts. If you don’t see it yet, it isn’t enabled for your organization — contact your Primo representative.

Set the ticket information

Applied to every offboarding ticket Primo opens. Every change saves as soon as you make it, except Create offboarding ticket, which opens its own modal.

Choose when the ticket opens

Open Create offboarding ticket and pick its Autonomy:
  • Automatic — Primo opens the ticket on the scheduled date. Scheduling offers four choices:
    • The day before the last day
    • 7 days before the last day, marked Recommended
    • 30 days before the last day
    • As soon as the departure appears in your HRIS
  • Manual — Primo opens no ticket and sends no notification. You open each ticket yourself from the employee panel. See Start an offboarding.
The Create offboarding ticket modal: Automatic or Manual, then the Scheduling presets, with 7 days before the last day marked Recommended.
Until you change it, the ticket opens automatically 7 days before the last day. A departure your HR system reports later than that gets its ticket right away.
When your HR sync imports a departure whose last day has already passed (see Set up HR sync), or when a last day passes before its ticket opens, Primo opens no ticket. The employee panel shows Offboarding never started, with Create ticket to open it, or Ignore if the person isn’t leaving.

Configure the offboarding tasks

The four steps are listed in the order the ticket runs them:

Read the step chips

Each row shows how the next offboarding will handle the step:

Use the controls every step shares

Click a row to open its modal:
  • Include this step in offboarding — off means no task is created and the row reads Skip. Confirm offboarding information is always included.
  • Autonomy — Automatic (Primo runs the step) or Manual (a person does, Primo only opens the task).
  • Default assignee — the admin who owns the task and answers when Primo needs a decision on this step. When it’s empty, the ticket’s Default Assignee gets the task.
  • Scheduling — a day relative to the last day (from One month before to One month after, including The D-day) and a time, in 30-minute steps. In Automatic, it is when Primo runs the task. In Manual, it is the task’s due date.
Every step starts included and Manual, with no scheduling. An automatic step with no scheduling runs as soon as its task opens. A manual step with no scheduling has no due date.

Confirm offboarding information

Checks the leaver’s last day, personal email, and personal phone number. Primo schedules every other step from the last day, and reaches the leaver on the personal email and phone once they have left.
  • Automatic — Primo confirms the information on the scheduled date, using the last day and the contact details from your HR system as they are.
  • Manual — you check and confirm the information from the ticket.
Once this step is confirmed, the ticket opens the steps that follow.

Configure email & SaaS deprovisioning

This step appears only when SaaS Management is enabled on your account.
Removes the leaver’s accounts. The ticket gets this task only when the leaver holds at least one account.
  • Automatic — on the scheduled date, Primo removes the accounts as set below.
  • Manual — the task owner picks the accounts to remove, and how, from the ticket.
Manual deprovisioning due date sets how many days after the last day a manual account removal is due, from 1 to 60. It defaults to 7. The modal then lists your SaaS:
  • Email providers (Google Workspace, Microsoft Entra ID) — the first rows of Connected SaaS. Account sets what happens to the leaver’s account by default: Suspend, Delete, or Do nothing, among the actions the provider offers. Transfer files to and Forward new emails to set who receives the leaver’s files and incoming emails: Nobody, Employee’s manager, or A specific user, picked in User. A transfer the chosen action doesn’t support is greyed out. The row reads Needs setup until the account action is set and every A specific user transfer names someone, then Auto-deprovisioned.
  • Other connected SaaS, listed after the email providers — Primo removes these accounts itself. A SaaS reads Auto-deprovisioned when it has a published access policy, and No access policy when it has none: Primo then removes the account by default.
  • SaaS to deprovision manually — the SaaS Primo isn’t connected to, grouped in one block under the table with their owners. Each SaaS owner gets a task on the ticket.
The SaaS part of the Configure email & SaaS deprovisioning modal: connected SaaS with their access policy status, the SaaS to deprovision manually, and the Manual deprovisioning due date.

How access policies decide which accounts are removed

When the step’s task opens, Primo checks every account of the leaver. An account is selected for removal unless the published access policy of its SaaS says the employee keeps it after they leave. A SaaS with no published access policy has its account removed. The task owner can still check or uncheck any account before the step runs. Click Set up the [app] access policy next to a SaaS with No access policy to write it, View the [app] access policy to read the one it has, or View access policies to see them all. When at least one SaaS has no access policy, Fix missing access policies opens Primo AI with the list, so it can propose a policy for each one and publish them once you confirm. See Set up access policies.

Handle equipment

Decides what happens to the leaver’s devices and accessories. The ticket gets this task only when the leaver holds at least one device.
  • Automatic — on the scheduled date, Primo applies the defaults below.
  • Manual — you decide for each device and accessory from the ticket.
The defaults:
  • Devices — Put back in stock (the default) or Archive.
  • Device data — the MDM action applied by default, per operating system (macOS, Windows, Linux, iOS, iPadOS, Android, ChromeOS): Keep all data (the default), Lock device but keep data, or Wipe. Windows offers Standard wipe and Hard wipe instead of Wipe. Shown only when device management is enabled.
  • Accessories — Put back in stock (the default), Reassign, or Archive.
The Handle equipment modal: the default Device data per operating system, then the Accessories choices.
A wipe erases the device. Make sure the leaver’s data is saved elsewhere before you set Wipe as the default. See Wiping devices.

Configure return shipments

Decides whether the ticket gets a Set up the return shipment task once the devices are handled. Primo never runs this step by itself: a person sets up the shipping label. Return shipment offers three choices:
The Configure return shipments modal: Always, Choose per offboarding, or Never, then the Default assignee and the Due date.
Unless you pick Never, set the Default assignee who prepares the label, and a Due date relative to the last day.