How offboarding works
Termination detected
Layer receives a termination event from your connected HRIS (e.g. BambooHR, Gusto, Rippling) or identity provider. The event includes the departing employee’s identity, last working day, manager, and return shipping address (if available).
Task created
Layer creates an offboarding task for the employee. It queries the employee’s assigned assets and generates a per-app action plan automatically.
Actions executed
Layer executes each action through your connected integrations, with automatic retries for transient failures.
Action types
Layer determines the correct action for each asset based on the asset type and authentication method:| Action | When it applies |
|---|---|
| Revoke OAuth | Apps connected via OAuth tokens |
| Revoke SSO | Apps accessed through single sign-on |
| Remove license | Licensed seats that should be reclaimed |
| Transfer data | Assets that require data handoff before removal |
| Queue device return | Physical devices (laptops, monitors, phones) |
| Flag for review | Assets that don’t match other categories and need manual attention |
Deduplication
Layer prevents duplicate offboarding tasks for the same employee. If a task already exists in apending or in_progress state, new termination events for that employee are ignored. This is enforced both at the application level and by a database constraint.
Hardware returns
When a departing employee has assigned devices, Layer tracks the full return lifecycle:Return statuses
| Status | Meaning |
|---|---|
| Queued | Return initiated, awaiting shipping label |
| Label generated | Shipping label created and sent to employee |
| In transit | Carrier confirms the package is on its way |
| Received | Package delivered to your return facility |
| Inspection pending | Device arrived and awaiting physical inspection |
| Completed | Inspection passed, device processed |
| SLA breached | Return did not arrive within the expected timeframe |
Escalation schedule
If an employee hasn’t returned their device, Layer escalates automatically:| Day | Action |
|---|---|
| Day 7 | Reminder sent to the employee |
| Day 14 | Alert sent to the IT lead |
| Day 21 | Alert sent to the employee’s manager |
| Day 30 | Alert sent to the finance team |
Device inspection
When a device is received, it goes through an inspection checklist:- Screen cracks
- Dents or physical damage
- Missing keys
- Port damage
- Battery health issues
- Accessories present
Device disposition
After inspection, devices are assigned a disposition:| Disposition | Meaning |
|---|---|
| Awaiting wipe | Queued for data wipe |
| Wiped and restocked | Wiped and returned to inventory |
| Refurbishment queue | Needs repair before reuse |
| Retired | End of life, scheduled for disposal |