How do I configure offboarding?
Settings → Policies → Offboarding sets when an offboarding starts, who confirms it, and how long a leaver has to send equipment back.
It does not decide what happens to each device. That is End of assignment on the entitlement category covering it, and where a returned device goes is the Return policy on Delivery & Returns.
In this guide
Before you begin
You need Admin access.
What is on the page
Two things: how a departure is reported, and the return deadline.
When someone leaves in your HRIS
On the Policy tab, three choices for what Velory does when your connected HR system reports a termination:
| Mode | What happens |
|---|---|
| Auto-start offboarding | Starts immediately, using the reported last day and a neutral departure type |
| Confirm each termination | (default) Creates a confirmation task — an admin picks the departure type and confirms before offboarding starts |
| Never auto-trigger | Terminations from the integration start nothing; you begin it from the employee record |
The default is deliberately the cautious one. A termination arriving from HR is not always the story it looks like — a contract ending and a person leaving are different events — and Confirm each termination puts a human between the sync and the revocations.
Who confirms a departure
Whoever you name is told when a departure is waiting, and whoever confirms first takes ownership of the leaver's remaining tasks: every company admin (the default), the leaver's manager, a named employee, or a group. Every empty result falls back to company admins, and confirming a departure requires company admin access.
Asset return deadline
Return within (days after last day) is how long a leaver has to get equipment back to you. Warn before deadline (days) is when the amber warning appears, and it has to fall on or before the deadline — the form refuses otherwise.
Where the rest lives
| Decision | Where it is set |
|---|---|
| What happens to a device — return or keep | End of assignment on the entitlement category |
| Where a returned device goes | Return policy on Delivery & Returns |
| Whether the employee may change either | A Lock switch beside each |
Good to know
How is this different from hardware policies?
Hardware policies describe the device — its contract term, depreciation curve, and buyout floor. Offboarding policies describe the departure — which option is offered for which asset type, and where returns are filed.
They work together — though with buy-out disabled, the depreciation side currently informs renewal and reporting rather than a live offer.
A category is missing from this page
Categories appear once hardware is assigned to them. Assign a device to the category and it shows up.
What happens to software and access on departure?
It is revoked automatically — there is nothing for you to set, which is what that tab says. Whether revocation reaches the vendor depends on the service's provisioning setup. See What is provisioning and deprovisioning?.
Why is there no buy-out option?
It is disabled product-wide, not missing from your setup. See the Hardware section above.
Why is editing disabled?
If the page could not load the current policies it disables editing rather than risk overwriting them — "Couldn't load the current policies, so editing is disabled to avoid overwriting them." Refresh and try again.
Was this article helpful?