Create staff vacation
Record an accepted all-day vacation for a Harbor Soho staff member from the vacations calendar. The manager form creates a staff vacation calendar event, refreshes the calendar, and keeps blackout and allowance checks in place.
In this article
Use this guide when a location manager needs to record staff leave for another employee at Harbor Soho.
Manager-created staff vacations are accepted immediately. The self-service vacation request flow is separate and should not be used for this action.
Before you start
- Harbor Demo Group and Harbor Soho are selected in the app context.
- The operator can manage vacations for the location. View-only vacation access cannot create staff vacations.
- The staff member already exists at Harbor Soho, for example Olivia Hart, Mason Reed, Noah Stone or Ava Price.
- The date range is valid, avoids an applicable vacation blackout such as Peak season blackout, and stays within the staff member's annual vacation allowance.
Instructions
- 1.
Open the vacations calendar
Open the Harbor Soho vacations calendar in month view, then start creating a Staff vacation. The same manager form can also be opened directly with kind=staff_vacation.
- 2.
Keep Staff vacation selected
Leave Close for vacation turned off so the event remains a staff vacation. Turning it on changes the action to a full location vacation closure.
- 3.
Choose the employee
Select the staff member whose vacation is being recorded. If the form was opened with returnStaffId, the employee is already filled in and cannot be changed.
- 4.
Set the dates
Choose the start and end dates. Staff vacations are saved as all-day calendar events in the location timezone, Europe/London for Harbor Soho.
- 5.
Add an optional reason
Use the vacation reason field when the manager needs to record context. The form stores this as the vacation reason and does not save a separate event description.
- 6.
Create the vacation
Press Create vacations. The manager flow submits the vacation as accepted through the calendar events API, then refreshes calendar data and returns to the configured route.
Validations and limits
- The app requires an active organisation and location before the form can be used.
- Staff vacation creation requires a staff member, valid start and end dates, and the start must be before the end.
- The backend rejects recurrence for staff vacation events.
- The backend checks the event kind, staff member, vacation payload, blackout conflicts and annual vacation limit before creating the calendar event.
- Users with only vacation request permission cannot create an accepted vacation for another employee.
Expected result
The new all-day Staff vacation appears on the vacations calendar after the app refreshes. If validation, permission, blackout or annual-limit checks fail, the form remains open and shows the resolved error message.