Restore an archived employee

In this article

Before you start

• Harbor Demo Group and the Harbor Soho location are selected in the app context.
• The operator has staff:manage permission for Harbor Soho. staff:view can load the list, but cannot restore employees.
• The Employees tab is opened with inactive employees shown, either through location/staff?tab=staff&staff_show_deleted=true or the Show inactive employees checkbox.
• At least one Harbor Soho employee has been archived before the operation starts.
• The archived employee still has an assigned employee role.

Instructions

1. 1.

   Open the Employees tab

   Go to the Staff area for Harbor Soho and open Employees. For a direct documentation route, use location/staff?tab=staff&staff_show_deleted=true.

2. 2.

   Show inactive employees

   Enable Show inactive employees if it is not already selected. The list shows active and inactive employees together, so check the row status before taking action.

3. 3.

   Find the archived employee

   Locate the employee row with Inactive status. The Restore row action is available only to users with staff:manage and is enabled only for archived rows.

4. 4.

   Open the restore confirmation

   Select Restore on the inactive employee row. The confirmation modal explains that future schedules are not restored automatically.

5. 5.

   Confirm the restore

   Select Restore in the modal. The app sends POST /api/app/{orgId}/{locationId}/staff/{staffId}/restore with no form data and refreshes staff-related views after success.

6. 6.

   Review schedules separately

   If the employee should work upcoming services, assign those schedules manually after restore. Do not assume future staff schedules were recreated.

Validations and limits

• Users with only staff:view can see the Employees table but cannot use Restore.
• Archived staff are hidden from the default list unless staff_show_deleted=true is present or Show inactive employees is enabled.
• Restore applies only to a staff record in the active location context; staff from another location are treated as not found.
• The archived employee must still have staff_role_id, otherwise the backend returns error.staff.role_required.
• The restore request uses POST only, sends no payload, and returns 204 No Content on success.
• The restore action clears staff.deleted_at on the existing record and does not recreate deleted future staff_schedule records.

Expected result

The employee is active again in Harbor Soho, the staff list and related caches refresh, and any future schedules removed during archive still need manual reassignment.