AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Student absence review

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

Try guided demo →Download guide ↓
Student absence review — illustrated workflow banner

What you can do

01

Approve

02

Decline

03

Withdraw

04

Report a planned or past absence for a student

05

List

06

Approve an absence, marking those days excused

07

Cancel

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
attendance: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

    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

    Withdraw 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
studentIdstringRequired by declaration
fromDatestringRequired by declaration
toDatestringOptional
reasonstringOptional
leaveTypestringOptional
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 student absence review

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/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

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