Skip to content

Leave & absence

For the helpdesk team

The leave & absence screen at /agent/people/leave is where staff leave requests are decided. It lists every request across the trust — requested ones float to the top — with the person, leave type, dates, working days, the leave year, and (where an entitlement exists) the remaining balance.

The screen sits behind the people::agent permission, but seeing the list and being able to act on a row are two different things. The Approve / Decline controls only appear on a request when the resolver decides you have authority over it. That depends on the workspace’s leave_approver_mode:

  • Manager mode (default) — the requester’s active-engagement line manager (their linked account) can decide, or anyone holding people::leave::manage.
  • HR mode — only people::leave::manage holders can decide.

A platform admin passes the people::leave::manage check automatically. Whatever your role, you can never approve your own request — the resolver blocks self-approval.

On a request you can act on, type an optional note and click Approve or Decline. The note is recorded against the status change in the audit trail.

  • Only a request still in requested status can be decided. If someone else has already actioned it, you’ll get a message saying it’s already been decided.
  • Approving moves the request to approved; declining moves it to declined. Both are recorded with who decided, when, and the note.
  • A balance only shows when an entitlement row exists for that person, leave type, and leave year. No entitlement set up yet means no balance figure — it doesn’t block the decision.
  • The list isn’t a calendar. It’s a decision queue; once a request is approved or declined it stays in the list for reference but drops below the outstanding ones.
  • Staff raise and cancel their own requests from My leave — this screen is the approval side only.