AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Staff leave requests

Use staff leave requests in the school workspace. Keep staff leave requests and student absence reports in their respective review workflows.

Try guided demo →Download guide ↓
Staff leave requests — illustrated workflow banner

What you can do

01

Approve

02

Decline

03

Self-service: apply for leave (resolves the caller's own staff profile)

04

Self-service: my own leave history

05

Admin: pending leave requests awaiting a decision

06

Admin: approve or reject a leave request

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
hr:viewhr:update

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Choose staff leave or student absence reporting

    A school account with the permissions shown below.

  2. 02

    Enter the applicable dates and reason

    Decline is part of the documented workflow.

  3. 03

    Submit or review through the permitted role

    Self-service: apply for leave (resolves the caller's own staff profile) is part of the documented workflow.

  4. 04

    Check the final decision and attendance impact

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Book the suggested stand-ins, not just plan them

Rules & current limits

  • Staff and student approval rules differ. The family view resolves linked-child ownership.

Source inventory checked on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Try staff leave requests

Open a guided sample workspace, try the available actions, then reset whenever you like. No login required.

Launch guided demo →

API & permissions reference

These are the source-matched API operations connected to this guide. Reading this reference does not execute any request.

4 source-declared operations
POST/api/v1/leave/apply

Self-service: apply for leave (resolves the caller's own staff profile)

Authenticated scope and endpoint-specific rules

Declared request fields: leaveType (required), fromDate (required), toDate (required), reason (optional).

GET/api/v1/leave/mine

Self-service: my own leave history

Authenticated scope and endpoint-specific rules
GET/api/v1/leave/pending

Admin: pending leave requests awaiting a decision

hr:view
PATCH/api/v1/leave/:id/decision

Admin: approve or reject a leave request

hr:update

Declared request fields: status (required), autoAssignCover (optional), remark (optional).

Open the actual application

ERP links use your assigned account. Record-specific pages start from the list so you can choose a real record.

Keep exploring