How changes save: unlike the Onboarding tab, the Offboarding tab saves with the Confirm button at the bottom of the page.
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.
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
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.
A step with no scheduling set runs on the D-day at 18:00.
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:
Deprovisioning can split into one task per app: Deprovision when Primo removes the account, or Remove account for on when you remove it yourself.
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.