Change employee status and read status history
Employee status is a current administrative value: DRAFT, ACTIVE, ON_LEAVE, SUSPENDED or TERMINATED. It is separate from login enabled state and dated employment evidence.
Rules
| Requested status | Server requirement |
|---|---|
| DRAFT | Creation starts here; an employee cannot return to DRAFT after leaving it |
| ACTIVE | An employment period covers the server's today |
| ON_LEAVE | A current employment period covers today |
| SUSPENDED | A current employment period covers today |
| TERMINATED | At least one employment exists and every period ends strictly before today |
Reactivation after a rehire needs a current employment. The service does not implement a full approval queue or configurable transition workflow. The browser excludes DRAFT/current status from its offered new-status choices; the server remains authoritative for each request.
Change status
- Open the accessible employee detail and reload current data.
- Review employment dates and the intended administrative decision.
- Choose Change status with
employee.manage. - Select the new state and enter the required reason, maximum 500 characters.
- Save and verify the displayed state.
- With employment-view authority, inspect Overview → Status history and its actor, previous/new state, reason and time.
History is paginated with Previous history/More history. Refresh status history if necessary. The current master value is not a historical/as-of status derived from a date picker.
Example: Employment ends 30 November. On server date 30 November it still covers today, so TERMINATED is refused. On 1 December, provided every period has ended before today, termination can be recorded. Closing the period does not itself change the master status at midnight.
Recovery
A current-employment error means dates do not cover server today, even if the browser date differs. A termination error can come from an open, future or today-ending period. Correct the actual employment facts or perform the action on the appropriate date; do not falsify dates to satisfy the button.
A stale version requires cancelling/reopening after recording the intended change. Employee status changes do not create, disable, unlock or remove a User. Review login separation and the departure checklist independently.