The job of this console
Open the case, chase asset return and access removal, deactivate when policy says so. Keep the Employee row for audit.
People · Lifecycle
Offboarding
Exit cases, asset return, and access wind-down on the same Employee row — not a deleted-people warehouse.
Scroll to Flowcharts. Scenario: Start offboarding for an employee.
Exit operations
Wind-down on the same person file
Offboarding tracks exit work on Employee. It does not invent a leavers database and it does not erase payroll or timesheet history.
People → Offboarding
Route
/people/offboarding
Org flag offboardingEnabled
HR Admin · Admin
Seat at the table
HR Admin and Admin. The employee may see tasks if self-service exists; they do not run the operator register.
The working rhythm
Select person, start case, work checklist, confirm assets and roles, then deactivate.
Moments that bring you here
Resignation. Last working day. A laptop still out. After payroll asked if they are still active.
ⓘ
Do not drop the source row
Employee remains canonical. Projects and timesheets keep history against that id.
Flowcharts
1 — Open an exit case
Select the Employee, start offboarding, track return and access.
flowchart TD
A[Open Offboarding] --> B[Select Employee]
B --> C[Start exit case]
C --> D[Assets / access / knowledge]
D --> E[Deactivate when policy allows]
E --> F[Employee remains historical source]
- 1OpenPeople → Offboarding.
- 2SelectExisting Employee.
- 3TrackAssets, access, knowledge transfer.
- 4DeactivatePer policy — do not drop the row from history.
Overview
Offboarding is a lifecycle workflow on Employee. Assets and access requests still use their registers. Payroll and timesheet lock rules still apply.
How to use
1. Do not delete to ‘clean’
History, pay, and audit need the person.
2. Assets on the asset register
Return is not a chat message.
3. Access
Roles, flags, and access requests — this case only tracks.