Skip to main content

Offboarding User Journey

Summary​

Employees can raise and track a resignation. Privileged reviewers can approve or reject eligible requests, decide rollback requests created outside this verified UI, and manually process access revokes after the confirmed last-working date.

Audience​

Employees, managers, HR administrators, QA, product and support staff.

Reference Content​

The employee view locks the employee identity, fixes the resignation date to the current day, suggests a requested last-working date, requires a reason and prevents a second active request. History shows resigned date, effective last-working date, displayed status, rejection reason and rollback outcome.

The privileged view lists pending approvals. Submitted and manager-approved rows expose Approve and Reject. Approval requires a confirmed last-working date; rejection requires a reason. A rollback-requested row exposes Approve Rollback and Reject Rollback. The current UI does not expose the employee action that originates a rollback request.

Approved exits whose effective last-working date has passed can appear in Pending Access Revokes. An authorized operator opens a confirmation dialog and explicitly processes the queue. The UI states that login is disabled while history is retained; this action is not automatic from the page.

Exit interview, knowledge transfer, asset return/clearance and final settlement fields are not implemented as coordinated screens in this journey.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/ApprovalActionModal.tsx
  • Controllers/HrOperationsController.cs

See Also​

Keywords​

  • Resignation
  • Exit approval
  • Access revoke

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly