AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Discipline & behaviour

Use discipline & behaviour in the school workspace. Record incidents, review student standing and manage sanctions through dedicated access.

Try guided demo →Download guide ↓
Discipline & behaviour — illustrated workflow banner
OVERVIEW

What you can do

01

Schedule

02

Served

03

Waive

04

List

05

Watchlist

06

List Sanctions

07

Get Policy

08

Set Policy

BEFORE YOU BEGIN

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
discipline:viewdiscipline:managediscipline:updatediscipline:create

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

STEP BY STEP

How the workflow works

  1. 01

    Locate the student within your permitted scope

    A school account with the permissions shown below.

  2. 02

    Record the incident and relevant context

    Served is part of the documented workflow.

  3. 03

    Review standing and any suggested threshold action

    Waive is part of the documented workflow.

  4. 04

    Schedule or close the appropriate sanction

    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.

  • Description
  • Tell the family about every incident, not only escalations
CURRENT BEHAVIOUR

Rules & current limits

  • Behaviour records have dedicated sensitive-data permissions; general student access does not imply access.

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

LEARN BY DOING

Try discipline & behaviour

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

Launch guided demo →
FOR IMPLEMENTERS

API & permissions reference

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

8 source-declared operations
GET/api/v1/discipline

List

discipline:view
GET/api/v1/discipline/watchlist

Watchlist

discipline:view
GET/api/v1/discipline/sanctions

List Sanctions

discipline:view
GET/api/v1/discipline/policy

Get Policy

discipline:view
PATCH/api/v1/discipline/policy

Set Policy

discipline:manage

Declared request fields: windowDays (optional), warnAt (optional), detentionAt (optional), parentMeetingAt (optional), suspensionReviewAt (optional), notifyFamilyOnIncident (optional).

POST/api/v1/discipline/sanctions/:id/schedule

Schedule

discipline:update

Declared request fields: scheduledFor (required), notes (optional).

POST/api/v1/discipline/sanctions/:id/close

Close Sanction

discipline:update

Declared request fields: served (required), reason (optional), notes (optional).

POST/api/v1/discipline

Create

discipline:create

Declared request fields: studentId (required), incidentDate (required), category (optional), description (required), severity (optional), actionTaken (optional), demeritPoints (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.

/en/school/disciplineOpen ↗

Keep exploring

Module guideDiscipline & behaviour →