Creating Staff Leave
Record a staff leave or absence for a selected employee at Harbor Soho. The action creates an all-day staff_leave calendar event with a required employee and start date, an optional end date, and an optional reason.
In this article
Staff leave is managed inside the same calendar layer used for vacations and blackout periods, so managers can keep absence planning connected to day-to-day staffing coverage.
Use this flow when a staff member is unavailable because of leave or absence. Open-ended leave stores no end date, while closed leave is saved as an all-day range through the final selected day.
Before you start
- You are signed in with Harbor Demo Group and Harbor Soho selected.
- Your account has staff-leave:manage permission for Harbor Soho.
- Harbor Soho has staff available to select, such as Olivia Hart, Mason Reed, Noah Stone, or Ava Price.
- Start from the vacations calendar, an individual staff calendar, or the direct staff_leave create route. The mine calendar preset is not used for creating staff_leave.
Instructions
- 1.
Open the leave calendar
Open the Harbor Soho vacations and leave calendar at `/:orgId/:locationId/calendars/vacations?mode=month`. This is the management surface where staff leave, vacations, and blackout periods are handled together.
- 2.
Start a new staff leave
Choose the create action and select staff leave, or open `/:orgId/:locationId/calendars/create?kind=staff_leave&preset=vacations`. The app opens the dedicated Create leave form and applies the location timezone automatically.
- 3.
Select the employee
Choose the staff member who will be unavailable, for example Olivia Hart. If the action starts from an individual staff calendar, the employee can already be selected and shown read-only.
- 4.
Set the leave dates
Enter the required start date. Keep the leave open-ended when there is no confirmed return date, or switch to a leave with an end date and choose the final day. Closed leave is stored from 00:00 on the start day through 23:59 on the end day.
- 5.
Add the reason if needed
Use the Reason field only when the leave needs an internal note. The field is optional and is stored as `payload.reason` for the staff_leave calendar event.
- 6.
Create the leave
Submit the form with Create leave. The app creates the staff_leave calendar event, refreshes calendar-event lists, shows the success confirmation, and returns to the previous calendar surface.
Validations and limits
- Creating staff leave requires staff-leave:manage. staff-leave:view can view leave but cannot create it.
- A staff member and a valid start date are required before submission.
- For closed leave, the end date is required and must be after the start date.
- For open-ended leave, the payload sends `ends_at: null` and `clear_ends_at: true`.
- The staff_leave payload accepts only an optional text `reason`.
- staff_leave does not support recurrence or approval states.
- The backend rejects overlapping staff_leave entries for the same employee and location.
- Invalid JSON is rejected before the calendar event service creates anything.
Expected result
The absence is saved as a `calendar_events` record with `kind="staff_leave"`. Calendar views and staff availability queries can then treat the employee as unavailable for the leave range, including open-ended leave through the queried period.