Approve Holiday Request
Approve a pending staff holiday request for the active location. The existing request is resolved in place as accepted; no new holiday entry is created.
In this article
Managers resolve holiday requests from a dedicated queue for the selected location. The queue keeps employee, dates, notes and the decision action together so each request can be reviewed before it changes state.
Approval updates the existing `staff_vacation` calendar event to `accepted`, refreshes the list and notifies the affected employee when a requested holiday is accepted.
Before you start
- You are signed in with an organisation and location selected.
- The selected demo location is Harbor Soho in Harbor Demo Group.
- You have `vacation:manage` for the selected location. Users with only `vacation:view` can review the queue but cannot approve requests.
- A pending `staff_vacation` request exists inside the visible date range. The queue treats `requested` and legacy `pending` as pending states.
- For capture production, seed one temporary Harbor Soho pending request, preferably for Olivia Hart, if the GB demo runtime does not already contain one.
Instructions
- 1.
Open pending requests
Open `calendars/vacations/requests?pending_only=true` for Harbor Soho. This is the manager queue for holiday requests awaiting a decision.
- 2.
Review the request
Check the employee, pending status, dates and notes before acting. If a staff filter is active, requests for other staff members stay hidden.
- 3.
Choose Approve
Use the Approve row action on the pending request. The action is only available to users who can manage holidays for the selected location.
- 4.
Confirm the approval
In the confirmation modal, verify the employee and holiday dates, then confirm. Cancelling closes the modal and leaves the request unchanged.
- 5.
Check the result
After a successful approval, the app shows a success message and refreshes the queue. In pending-only view the request disappears; in the full list it appears as accepted.
- 6.
Use detail approval when needed
A manager can also open `calendars/edit/:eventId?kind=staff_vacation&returnRoute=LocationVacationsRequests`. If the loaded request is still requested, the detail form can submit the same acceptance decision.
Validations and limits
- The request must be pending before the queue offers Approve.
- Users without `vacation:manage` do not see approve, reject or delete actions.
- If no organisation or location is selected, or the user lacks view permission, the queue is not shown.
- The row action updates the existing holiday request; it does not create a new holiday entry or edit the employee, dates or notes.
- The queue action cannot bypass holiday blackout validation.
- Approval can fail because of permissions, payload validation, a holiday blackout, the annual holiday limit or another API error. In that case the request remains unresolved.
Expected result
The existing staff holiday request is accepted, the pending queue refreshes, and a decision notification is created for the employee when a requested holiday becomes accepted.