AVKUL ERPDocs
MODULE GUIDE · 11 OCT 2026

Staff leave & student absences

Keep staff leave requests and student absence reports in their respective review workflows.

Try guided demo →Download guide ↓
Staff leave & student absences — illustrated workflow banner

What you can do

01

Self-service staff leave

02

Pending review

03

Approve or reject

04

Student absence report

05

Approval and cancellation

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
hr:viewhr:updateattendance:viewattendance:manage

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

    An assigned school account with the required permissions.

  2. 02

    Enter the applicable dates and reason

    Pending review is part of the documented workflow.

  3. 03

    Submit or review through the permitted role

    Approve or reject 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.

Request fields to understand

Source-declared fields used by related operations; each operation has its own validation and scope.

FieldDeclared typeInput
leaveTypestringOptional
fromDatestringRequired by declaration
toDatestringOptional
reasonstringOptional
status'APPROVED' | 'REJECTED'Required by declaration
autoAssignCoverbooleanOptional
remarkstringOptional
studentIdstringRequired by declaration
attachmentUrlstringOptional
approvebooleanRequired by declaration

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 & student absences

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

Launch guided demo →

API & permissions reference

This is the module’s source-declared endpoint catalogue. Reading this reference does not execute any request.

9 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).

POST/api/v1/student-leave

Report a planned or past absence for a student

Authenticated scope and endpoint-specific rules

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

GET/api/v1/student-leave/mine

Absences reported for my own children

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

List

attendance:view
PATCH/api/v1/student-leave/:id/decision

Approve an absence, marking those days excused

attendance:manage

Declared request fields: approve (required), reason (optional).

PATCH/api/v1/student-leave/:id/cancel

Cancel

Authenticated scope and endpoint-specific rules

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