How to review vacation requests
Use the Vacation requests screen to review staff holiday requests for one location, starting from the pending queue and narrowing the list by date range or employee. This is a review workflow only; approve, reject, create and delete are separate actions.
In this article
The Vacation requests screen gives managers a single place to review staff holiday requests before making rota decisions. It loads `staff_vacation` calendar events for the selected location and resolves staff names from the staff list.
The screen can start as a pending queue or widen to accepted and rejected requests. This guide stops at review and navigation to detail, even when management controls are visible.
Before you start
- Be signed in to Antylogic.
- Have Harbor Demo Group and Harbor Soho selected, or the equivalent organisation and location in production.
- Have location permission `vacation:view` or `vacation:manage`. `vacation:manage` also shows management controls.
- Have staff data available so employee names, avatars, initials and the employee filter can be resolved, for example Olivia Hart, Mason Reed, Noah Stone and Ava Price in the GB demo.
Instructions
- 1.
Open the request queue
Open `/:orgId/:locationId/calendars/vacations/requests?pending_only=true` from Home, a vacation request notification, the vacations calendar list button, or a direct deep link. Home and notification entry points prioritise pending requests.
- 2.
Confirm the review range
Check the date range before reviewing rows. If `from` and `to` are not present, the screen uses the current calendar year; for captures on 6 June 2026, use 1 January 2026 through 31 December 2026.
- 3.
Read the request rows
Review each row by Employee, Status, Dates and Notes. The list only includes `staff_vacation` events, expands occurrences and sorts rows by `occurrence_start`.
- 4.
Filter by employee or status scope
Use the employee selector to focus on one staff member, or keep All employees for the whole location. Clear the pending-only checkbox or open with `pending_only=false` to include accepted and rejected requests.
- 5.
Open a request for detail
Select a row to open `LocationCalendarEventEdit` with `kind=staff_vacation` and `returnRoute=LocationVacationsRequests`. Use the detail view for review context only in this action.
Validations and limits
- The screen requires authenticated organisation and location context.
- Without `vacation:view` or `vacation:manage`, the operator sees the no-permission calendar message and the list is not loaded.
- The backend requires both `from` and `to` for calendar event listing and rejects ranges where `to` is before `from`.
- The calendar request loads by `kinds=staff_vacation`; employee and pending filters are applied locally after events load.
- With `pending_only=true`, only `requested` or `pending` rows remain. `accepted` and `approved` are shown as accepted; `rejected` is shown as rejected.
- The employee filter is kept only when the selected staff id exists in the loaded staff options.
- Approve, reject, create and delete controls may be visible for `vacation:manage`, but those mutations belong to separate unit actions.
Expected result
The manager has a scoped, permission-checked view of staff holiday requests for Harbor Soho or the selected location, can inspect the relevant rows and can open details without changing request status in this review-only workflow.