# AVKUL ERP complete feature handbook Snapshot: 11 October 2026 Coverage: 236 guides, 45 backend modules, 120 web routes, 52 mobile source screens, 839 declared API operations. Demo library: https://avkul.in/docs/demo/ Public demos use fictional browser-only samples; assigned accounts are required for actual ERP modules. # Academic setup Create the academic structure that attendance, admissions, examinations and timetables share. Category: Academics Guide: https://avkul.in/docs/guides/module-academic/ Guided sample demo: https://avkul.in/docs/demo/module-academic/ Snapshot: 11 October 2026 ## Features - Academic sessions - Classes and sections - Subject catalogue - Current session - Year-end close and reopen ## Access and 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. Permission keys: settings:view, settings:create, settings:update, settings:delete, student:view, settings:manage ## Workflow 1. Create an academic session with dates. 2. Add classes and their sections. 3. Create subjects and select the current session. 4. Close the books only after the year-end review. ## Fields and controls - name (string, declared required) - startDate (string, declared required) - endDate (string, declared required) - isCurrent (boolean, optional) - sessionId (string, declared required) - numericLevel (number, optional) - streamId (string, optional) - sortOrder (number, optional) - classId (string, declared required) - capacity (number, optional) - classTeacherId (string, optional) - roomNo (string, optional) - code (string, optional) - type (string, optional) - isElective (boolean, optional) - credits (number, optional) - locked (boolean, declared required) - reason (string, optional) ## Current limits - Session ownership and closed-year checks apply to connected workflows. ## Actual application access - https://avkul.in/en/school/academics ## API reference - GET /api/v1/academic/sessions — List Sessions; settings:view - POST /api/v1/academic/sessions — Create Session; settings:create - PATCH /api/v1/academic/sessions/:id — Update Session; settings:update - POST /api/v1/academic/sessions/:id/set-current — Set Current; settings:update - DELETE /api/v1/academic/sessions/:id — Remove Session; settings:delete - GET /api/v1/academic/classes — List Classes; student:view - POST /api/v1/academic/classes — Create Class; settings:create - PATCH /api/v1/academic/classes/:id — Update Class; settings:update - DELETE /api/v1/academic/classes/:id — Remove Class; settings:delete - GET /api/v1/academic/sections — List Sections; student:view - POST /api/v1/academic/sections — Create Section; settings:create - PATCH /api/v1/academic/sections/:id — Update Section; settings:update - DELETE /api/v1/academic/sections/:id — Remove Section; settings:delete - GET /api/v1/academic/subjects — List Subjects; student:view - POST /api/v1/academic/subjects — Create Subject; settings:create - PATCH /api/v1/academic/subjects/:id — Update Subject; settings:update - DELETE /api/v1/academic/subjects/:id — Remove Subject; settings:delete - GET /api/v1/academic/sessions/locks — Every academic year and whether its books are closed; settings:view - PATCH /api/v1/academic/sessions/:id/lock — Close or re-open an academic year's books; settings:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Roles & permissions Control which school users can view, create, edit, export and manage records. Category: Administration Guide: https://avkul.in/docs/guides/module-access-control/ Guided sample demo: https://avkul.in/docs/demo/module-access-control/ Snapshot: 11 October 2026 ## Features - Role catalogue - Permission catalogue - Role grants - User assignment ## Access and 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. Permission keys: role:view, role:create, role:update, role:delete, role:manage ## Workflow 1. Open a role and inspect its existing permissions. 2. Choose only the required permission keys. 3. Save the role and assign eligible users. 4. Sign in as the affected role to review access. ## Fields and controls - name (string, optional) - key (string, declared required) - description (string, optional) - permissionKeys (string[], declared required) - userId (string, declared required) ## Current limits - A role name alone does not grant platform administration. School scope and explicit guards still apply. ## Actual application access - https://avkul.in/en/school/settings/roles - https://avkul.in/en/school/settings/roles — select the actual record from this list. ## API reference - GET /api/v1/access-control/roles — List; role:view - GET /api/v1/access-control/permissions — Permission Catalog; role:view - GET /api/v1/access-control/roles/:id — Get; role:view - POST /api/v1/access-control/roles — Create; role:create - PATCH /api/v1/access-control/roles/:id — Update; role:update - DELETE /api/v1/access-control/roles/:id — Remove; role:delete - PUT /api/v1/access-control/roles/:id/permissions — Set Permissions; role:manage - GET /api/v1/access-control/roles/:id/assignable-users — Assignable Users; role:manage - POST /api/v1/access-control/roles/:id/users — Assign User; role:manage - DELETE /api/v1/access-control/roles/:id/users/:userId — Unassign User; role:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Admissions & applicant journey Connect family enquiries, counsellor follow-ups, reviewed applications and student admission. Category: School office Guide: https://avkul.in/docs/guides/module-admission/ Guided sample demo: https://avkul.in/docs/demo/module-admission/ Snapshot: 11 October 2026 ## Features - Enquiry pipeline - Contact attempts - Application stages - Guardian details - Campus visits - Document review - Applicant access links - Student placement - Parent invitation ## Access and 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. Permission keys: admission:manage, admission:view, admission:update, admission:create, student:create ## Workflow 1. Record or select an enquiry and log the next follow-up. 2. Open a linked application and review guardian details. 3. Receive and verify required documents and review readiness. 4. Select session, class and section before admitting the applicant. ## Fields and controls - purpose ('APPLICANT' | 'PARENT_INVITE', declared required) - version (string, declared required) - studentName (string, declared required) - classApplying (string, declared required) - guardianName (string, declared required) - phone (string, declared required) - email (string, optional) - relationship (string, declared required) - dateOfBirth (string, optional) - previousSchool (string, optional) - address (string, optional) - preferredAt (string, declared required) - notes (string, optional) - kind (string, declared required) - password (string, declared required) - summary (string, declared required) - channel (string, optional) - outcome (string, optional) - status (string, declared required) - followUpAt (string, optional) - byStaffId (string, optional) - counsellorId (string, declared required) - reason (string, optional) - parentName (string, declared required) ## Current limits - Application access links and parent invitations are separate from an existing family login. Admission is subject to readiness and school/session ownership. ## Actual application access - https://avkul.in/en/school/admissions ## API reference - GET /api/v1/admissions/applications/:id/access-links — List; admission:manage - POST /api/v1/admissions/applications/:id/access-links — Issue; admission:manage - DELETE /api/v1/admissions/applications/:id/access-links — Revoke; admission:manage - GET /api/v1/admissions/work-queue — Queue; admission:view - GET /api/v1/admissions/documents/:id/file — File; admission:view - GET /api/v1/admissions/portal — Get; Public/capability access - PATCH /api/v1/admissions/portal/draft — Save; Public/capability access - POST /api/v1/admissions/portal/submit — Submit; Public/capability access - POST /api/v1/admissions/portal/visit-request — Visit; Public/capability access - POST /api/v1/admissions/portal/documents — Upload; Public/capability access - GET /api/v1/admissions/portal/documents/:id/file — File; Public/capability access - GET /api/v1/admissions/parent-invitation — Get; Public/capability access - POST /api/v1/admissions/parent-invitation/accept — Accept; Public/capability access - GET /api/v1/admissions/enquiries/due — Leads due a follow-up, oldest overdue first; admission:view - GET /api/v1/admissions/enquiries/funnel — Pipeline by stage and by source, with conversion; admission:view - GET /api/v1/admissions/enquiries — List; admission:view - GET /api/v1/admissions/enquiries/:id/follow-ups — History; admission:view - POST /api/v1/admissions/enquiries/:id/follow-ups — Record a contact attempt and move the lead on; admission:update - POST /api/v1/admissions/enquiries/:id/reassign — Reassign; admission:manage - POST /api/v1/admissions/enquiries/:id/reopen — Put a converted/lost enquiry back in play; admission:update - POST /api/v1/admissions/enquiries — Create; admission:create - PATCH /api/v1/admissions/enquiries/:id — Update; admission:update - POST /api/v1/admissions/enquiries/:id/convert — Convert; admission:update, student:create - DELETE /api/v1/admissions/enquiries/:id — Remove; admission:update - GET /api/v1/admissions/applications — List; admission:view - GET /api/v1/admissions/applications/funnel — Where applicants are, and how many converted; admission:view - POST /api/v1/admissions/applications — Open an application, optionally from an enquiry; admission:create - PATCH /api/v1/admissions/applications/:id — Update; admission:update - POST /api/v1/admissions/applications/:id/advance — Move the application one legal step; admission:manage - POST /api/v1/admissions/applications/:id/admit — Turn a selected applicant into a student; admission:manage - GET /api/v1/admissions/applications/:id/journey — Get; admission:view - PATCH /api/v1/admissions/applications/:id/journey/guardian — Guardian; admission:update - PATCH /api/v1/admissions/applications/:id/journey/visit — Visit; admission:update - PATCH /api/v1/admissions/applications/:id/journey/documents — Document; admission:update - POST /api/v1/admissions/applications/:id/journey/documents/review — Review; admission:manage - POST /api/v1/admissions/applications/:id/journey/parent-access — Parent Access; admission:manage - POST /api/v1/admissions/public/:schoolCode/enquiries — Create; Public/capability access ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # AI tools & decision support Use assisted writing, learning support and forecasts while reviewing the provider state and human decisions. Category: Intelligence Guide: https://avkul.in/docs/guides/module-ai-features/ Guided sample demo: https://avkul.in/docs/demo/module-ai-features/ Snapshot: 11 October 2026 ## Features - Provider status - Academic assistance - Learning gaps - Lesson planning - Forecast scenarios - Staff workload - Transport ETA - Governance and review ## Access and 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. Permission keys: dashboard:view, exam:update, attendance:view, fee:view, exam:create, student:view, lms:view, timetable:view, inventory:view, communication:create, attendance:create, hostel:view, exam:view, student:manage, fee:manage, attendance:update, transport:view, health:manage, settings:update ## Workflow 1. Review the provider-status banner before requesting assistance. 2. Choose the school context, topic or forecast period. 3. Run the relevant tool and inspect its output and evidence. 4. Review or edit the result before using it with learners. ## Fields and controls - studentId (string, declared required) - examId (string, optional) - subject (string, declared required) - topic (string, optional) - difficulty (string, optional) - count (number, optional) - questionType (string, optional) - question (string, declared required) - lessonId (string, declared required) - bulletPoints (string, declared required) - language (string, optional) - interestArea (string, optional) - sectionId (string, declared required) - transcript (string, declared required) - date (string, optional) - imageUrl (string, declared required) - claimedName (string, optional) - visitorLogId (string, optional) - referenceImageUrl (string, optional) - sourceImageUrl (string, declared required) - targetImageUrl (string, declared required) - days (number, optional) - regenerate (boolean, optional) - status ('DRAFT' | 'PUBLISHED' | 'PRIVATE' | 'ARCHIVED', declared required) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/ai-governance - https://avkul.in/en/school/ai-tools - https://avkul.in/en/school/cashflow - https://avkul.in/en/school/enrolment-forecast - https://avkul.in/en/school/executive-copilot - https://avkul.in/en/school/forecasts - https://avkul.in/en/school/inventory-forecast - https://avkul.in/en/school/learning-gaps - https://avkul.in/en/school/lesson-planner - https://avkul.in/en/school/multilingual-explain - https://avkul.in/en/school/staff-workload - https://avkul.in/en/school/transport-eta ## API reference - GET /api/v1/ai-features/provider-status — AI configuration status; does not contact the provider or expose secrets; dashboard:view - POST /api/v1/ai-features/remarks — Generate Remark; exam:update - GET /api/v1/ai-features/attendance-anomalies — Attendance Anomalies; attendance:view - GET /api/v1/ai-features/fee-risk — Fee Risk; fee:view - POST /api/v1/ai-features/question-paper — Generate Question Paper; exam:create - GET /api/v1/ai-features/discipline-risk — Discipline Risk; student:view - POST /api/v1/ai-features/parent-chat — Parent Chat; dashboard:view - POST /api/v1/ai-features/staff-copilot — Generic AI Assistant for staff — grounded in real, live school numbers; dashboard:view - POST /api/v1/ai-features/study-buddy — Study Buddy; lms:view - GET /api/v1/ai-features/career-counsel/:studentId — Career Counsel; student:view - GET /api/v1/ai-features/timetable-suggest — Suggest Timetable; timetable:view - GET /api/v1/ai-features/inventory-reorder — Inventory Reorder; inventory:view - POST /api/v1/ai-features/notice-draft — Draft Notice; communication:create - POST /api/v1/ai-features/alumni-match — Match Alumni; student:view - POST /api/v1/ai-features/voice-attendance — Voice Attendance; attendance:create - POST /api/v1/ai-features/visitor-verify — Verify Visitor Photo; hostel:view - GET /api/v1/ai-features/dropout-risk — Dropout Risk; student:view - GET /api/v1/ai-features/repeat-visitors — Repeat Visitors; hostel:view - POST /api/v1/ai-features/face-match — Compare Faces; hostel:view - POST /api/v1/ai-features/learning-path — Learning Path; lms:view - GET /api/v1/ai-features/learning-path/:studentId — Get Learning Path; lms:view - GET /api/v1/ai-features/learning-path/:studentId/history — Learning Path History; lms:view - PATCH /api/v1/ai-features/learning-path-items/:itemId — Update Learning Path Item; lms:view - GET /api/v1/ai-features/learning-gaps — List Learning Gaps; student:view - GET /api/v1/ai-features/learning-gaps/latest — Latest Learning Gap Scan; student:view - POST /api/v1/ai-features/learning-gaps/scan — Run Learning Gap Scan; student:view - PATCH /api/v1/ai-features/learning-gaps/alerts/:alertId — Update Learning Gap Alert; student:view - POST /api/v1/ai-features/learning-gaps/alerts/:alertId/learning-path — Learning Path From Gap; lms:view - POST /api/v1/ai-features/adaptive-exam — Adaptive Exam; exam:view - GET /api/v1/ai-features/lesson-planner — List Lesson Plans; timetable:view - POST /api/v1/ai-features/lesson-planner — Generate Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/days/:dayId — Update Lesson Plan Day; timetable:view - GET /api/v1/ai-features/lesson-planner/:planId — Get Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId — Update Lesson Plan Meta; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId/status — Set Lesson Plan Status; timetable:view - GET /api/v1/ai-features/multilingual-explain — List Multilingual Explain; lms:view - POST /api/v1/ai-features/multilingual-explain — Generate Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/langs/:langId — Update Multilingual Explain Lang; lms:view - GET /api/v1/ai-features/multilingual-explain/:id — Get Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id — Update Multilingual Explain Meta; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id/status — Set Multilingual Explain Status; lms:view - GET /api/v1/ai-features/enrolment-forecast — List Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/latest — Latest Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/compare — Compare Enrolment Forecast; student:manage - POST /api/v1/ai-features/enrolment-forecast — Run Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/:id — Get Enrolment Forecast; student:manage - GET /api/v1/ai-features/cashflow-prediction — List Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/latest — Latest Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/compare — Compare Cashflow; fee:manage - POST /api/v1/ai-features/cashflow-prediction — Run Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/:id — Get Cashflow; fee:manage - GET /api/v1/ai-features/staff-workload — List Staff Workload; timetable:view, attendance:update - GET /api/v1/ai-features/staff-workload/latest — Latest Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload — Run Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload/substitutions — Suggest Substitutions; timetable:view, attendance:update - GET /api/v1/ai-features/staff-workload/:id — Get Staff Workload; timetable:view, attendance:update - GET /api/v1/ai-features/transport-eta — List Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/latest — Latest Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/live/:vehicleId — Live Transport Eta; transport:view - POST /api/v1/ai-features/transport-eta — Run Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/:id — Get Transport Eta; transport:view - GET /api/v1/ai-features/hostel-inventory-forecast — List Inventory Forecast; inventory:view - GET /api/v1/ai-features/hostel-inventory-forecast/latest — Latest Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast — Run Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast/:id/draft-po — Draft Po From Forecast; inventory:view - GET /api/v1/ai-features/hostel-inventory-forecast/:id — Get Inventory Forecast; inventory:view - POST /api/v1/ai-features/parent-copilot — Parent Copilot; dashboard:view - POST /api/v1/ai-features/voice-assistant — Voice Assistant; dashboard:view - POST /api/v1/ai-features/progress-story — Progress Story; student:view - POST /api/v1/ai-features/career-twin — Career Twin; student:view - POST /api/v1/ai-features/alumni-opportunity — Alumni Opportunity; student:view - POST /api/v1/ai-features/campus-safety — Campus Safety; hostel:view - GET /api/v1/ai-features/wellbeing-radar — Wellbeing Radar; health:manage - GET /api/v1/ai-features/ai-audit — Ai Audit; dashboard:view - POST /api/v1/ai-features/ai-audit/feedback — Ai Audit Feedback; dashboard:view - GET /api/v1/ai-features/fairness-monitor — Fairness Monitor; student:manage - GET /api/v1/ai-features/data-minimization — Get Data Minimization; dashboard:view - PATCH /api/v1/ai-features/data-minimization — Update Data Minimization; settings:update - POST /api/v1/ai-features/auto-grade — Auto Grade; exam:update - POST /api/v1/ai-features/classroom-insights — Classroom Insights; attendance:view - POST /api/v1/ai-features/substitution-brain — Substitution Brain; timetable:view - POST /api/v1/ai-features/question-bank-intel — Question Bank Intel; exam:view - POST /api/v1/ai-features/meeting-notes — Meeting Notes; communication:create - GET /api/v1/ai-features/school-twin-benchmark — School Twin Benchmark; dashboard:view - POST /api/v1/ai-features/policy-copilot — Policy Copilot; dashboard:view - POST /api/v1/ai-features/accreditation-pack — Accreditation Pack; dashboard:view - GET /api/v1/ai-features/branch-performance — Branch Performance; dashboard:view - GET /api/v1/webhooks/whatsapp — Verify; Public/capability access - POST /api/v1/webhooks/whatsapp — Inbound; Public/capability access - POST /api/v1/ai-features/whatsapp-parent-copilot/simulate — Simulate; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Alumni records Maintain alumni information and keep former learners connected to the school community. Category: Community Guide: https://avkul.in/docs/guides/module-alumni/ Guided sample demo: https://avkul.in/docs/demo/module-alumni/ Snapshot: 11 October 2026 ## Features - Alumni directory - Record creation - Profile updates - Record removal ## Access and 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. Permission keys: student:view, student:create, student:update, student:delete ## Workflow 1. Open the alumni directory. 2. Add the alumnus and relevant year/contact details. 3. Update the record as information changes. 4. Review scope before removing an entry. ## Fields and controls - firstName (string, declared required) - lastName (string, optional) - graduationYear (number, declared required) - studentId (string, optional) - currentOccupation (string, optional) - company (string, optional) - email (string, optional) - phone (string, optional) - linkedinUrl (string, optional) - addressJson (Record, optional) - notes (string, optional) ## Current limits - A directory record does not automatically provision an alumni login or send invitations. ## Actual application access - https://avkul.in/en/school/alumni ## API reference - GET /api/v1/alumni — List; student:view - POST /api/v1/alumni — Create; student:create - PATCH /api/v1/alumni/:id — Update; student:update - DELETE /api/v1/alumni/:id — Remove; student:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Homework & assignments Create and distribute class work, collect student submissions and record grading feedback. Category: Academics Guide: https://avkul.in/docs/guides/module-assignment/ Guided sample demo: https://avkul.in/docs/demo/module-assignment/ Snapshot: 11 October 2026 ## Features - Class and section scope - Assignment attachments - Submission queue - Grading - History - In-app reminders ## Access and 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. Permission keys: assignment:view, assignment:update, assignment:create, assignment:delete ## Workflow 1. Select the teaching section and create an assignment. 2. Add the instructions, due date and supported files. 3. Review submitted or pending work. 4. Grade the submission and review the activity history. ## Fields and controls - assignmentId (string, optional) - dueInDays (number, optional) - title (string, declared required) - classId (string, optional) - sectionId (string, optional) - subjectId (string, optional) - instructions (string, optional) - maxMarks (number, optional) - dueDate (string, optional) - status ('DRAFT' | 'PUBLISHED' | 'CLOSED', optional) - version (string, optional) - correctionReason (string, optional) - outcome ('GRADED' | 'RETURNED', optional) - marksObtained (number, optional) - remarks (string, optional) ## Current limits - Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel. ## Actual application access - https://avkul.in/en/school/assignments - https://avkul.in/en/school/assignments — select the actual record from this list. ## API reference - GET /api/v1/assignment-files/:id — Download; assignment:view - POST /api/v1/assignments/:id/files — Upload; assignment:update - GET /api/v1/assignments — List; assignment:view - GET /api/v1/assignments/dashboard — Dashboard; assignment:view - GET /api/v1/assignments/pending — Pending; assignment:view - POST /api/v1/assignments/remind — Remind; assignment:update - GET /api/v1/assignments/:id/reminders — Reminder History; assignment:view - GET /api/v1/assignments/:id/history — History; assignment:view - GET /api/v1/assignments/:id — Get; assignment:view - POST /api/v1/assignments — Create; assignment:create - PATCH /api/v1/assignments/:id — Update; assignment:update - DELETE /api/v1/assignments/:id — Remove; assignment:delete - PATCH /api/v1/assignments/submissions/:submissionId/grade — Grade Submission; assignment:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student attendance Complete a daily class register and review attendance history, shortages and family alerts. Category: Academics Guide: https://avkul.in/docs/guides/module-attendance/ Guided sample demo: https://avkul.in/docs/demo/module-attendance/ Snapshot: 11 October 2026 ## Features - Section roster - Daily marking - Section completion - Corrections - Monthly register - Shortage review - Holiday stamping ## Access and 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. Permission keys: attendance:view, attendance:create, attendance:manage ## Workflow 1. Choose a permitted section and date. 2. Mark the roster and review the section completion summary. 3. Save the register and inspect corrections/history. 4. Review shortages and recorded alerts before reminding families. ## Fields and controls - sectionId (string, optional) - date (string, declared required) - session (string, optional) - records (AttendanceRecordInput[], declared required) - version (string, optional) - correctionReason (string, optional) - force (boolean, optional) - notifyGuardians (boolean, optional) - from (string, declared required) - to (string, declared required) - message (string, optional) - studentIds (string[], optional) ## Current limits - Holiday and attendance policy affect denominators. Only permitted sections are visible; recording an absence is distinct from approving leave. ## Actual application access - https://avkul.in/en/school/attendance ## API reference - GET /api/v1/attendance/dashboard — Dashboard; attendance:view - GET /api/v1/attendance/changes — Changes; attendance:view - GET /api/v1/attendance/roster — Students of a section + their status for a date; attendance:view - POST /api/v1/attendance/mark — Mark/replace attendance for a section + date; attendance:create - POST /api/v1/attendance/mark-holidays — Stamp HOLIDAY rows for closed days from the calendar; attendance:manage - GET /api/v1/attendance/register — Monthly attendance register for a section; attendance:view - POST /api/v1/attendance/alerts/absence — Tell absent students' guardians, once per student per day; attendance:manage - GET /api/v1/attendance/shortages — Students below the required attendance percentage; attendance:view - POST /api/v1/attendance/alerts/shortage — Warn guardians of students below the required percentage; attendance:manage - GET /api/v1/attendance/alerts — What has already been sent to families; attendance:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Audit trail Review the recorded actions taken on school records and trace related entities. Category: Administration Guide: https://avkul.in/docs/guides/module-audit/ Guided sample demo: https://avkul.in/docs/demo/module-audit/ Snapshot: 11 October 2026 ## Features - Activity filters - Actor and action - Entity references - Record detail ## Access and 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. Permission keys: settings:view ## Workflow 1. Select an entity or activity filter. 2. Locate the relevant actor and time. 3. Open the recorded change and its entity reference. 4. Compare the trail with the current record. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The audit view records permitted activity; it is not an editor for rewriting historical actions. ## Actual application access - https://avkul.in/en/school/audit-log ## API reference - GET /api/v1/audit-logs — List; settings:view - GET /api/v1/audit-logs/entities — List Entities; settings:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Sign-in & account sessions Sign in with assigned account details and keep platform support access separate from school accounts. Category: Administration Guide: https://avkul.in/docs/guides/module-auth/ Guided sample demo: https://avkul.in/docs/demo/module-auth/ Snapshot: 11 October 2026 ## Features - Account login - Current profile - Token refresh - Logout - Platform impersonation ## Access and setup Intended access: Platform administrator - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. ## Workflow 1. Open the ERP sign-in page. 2. Enter the assigned identifier and school code when required. 3. Use the workspace available to the signed-in role. 4. Log out when the session is finished. ## Fields and controls - identifier (string, declared required) - password (string, declared required) - schoolCode (string, optional) - tenantSlug (string, optional) - deviceName (string, optional) - refreshToken (string, optional) - userId (string, declared required) - reason (string, declared required) - minutes (number, optional) - sessionId (string, optional) ## Current limits - Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited. ## Actual application access - https://avkul.in/en/saas/impersonation - https://avkul.in/en/login - https://avkul.in/en ## API reference - POST /api/v1/auth/login — Login by email / phone / employee code / admission no; Public/capability access - POST /api/v1/auth/refresh — Rotate a refresh token for a new token pair; Public/capability access - POST /api/v1/auth/logout — Revoke the current session (or all sessions); Authenticated scope - GET /api/v1/auth/me — Current user profile, roles and permissions; Authenticated scope - POST /api/v1/auth/impersonate — Start acting as another user (platform admins only); Authenticated scope - POST /api/v1/auth/impersonate/stop — End an impersonation session; Authenticated scope - GET /api/v1/auth/impersonate/active — Open impersonation sessions (platform admins only); Authenticated scope - POST /api/v1/auth/impersonate/close-lapsed — Close expired impersonation sessions (platform admins only); Authenticated scope - GET /api/v1/auth/impersonate/history — Impersonation audit history (platform admins only); Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student & staff import/export Prepare spreadsheet records using the provided templates and use the bulk student/staff operations. Category: School office Guide: https://avkul.in/docs/guides/module-bulk/ Guided sample demo: https://avkul.in/docs/demo/module-bulk/ Snapshot: 11 October 2026 ## Features - Student template - Student import and export - Staff template - Staff import and export ## Access and 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. Permission keys: student:create, student:view, hr:create, hr:view ## Workflow 1. Download the template for the chosen record type. 2. Fill the required columns with school-owned references. 3. Submit through the permitted bulk workflow and inspect its result. 4. Export and reconcile the accepted records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Imports can modify many records. A template or export endpoint does not imply a separate bulk-import page exists. ## Actual application access - https://avkul.in/en/school/students - https://avkul.in/en/school/staff ## API reference - GET /api/v1/bulk/students/template — Template; student:create - GET /api/v1/bulk/students/export — Export; student:view - POST /api/v1/bulk/students/import — Import; student:create - GET /api/v1/bulk/staff/template — Template; hr:create - GET /api/v1/bulk/staff/export — Export; hr:view - POST /api/v1/bulk/staff/import — Import; hr:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School calendar & holidays Publish the dates, events and holiday settings that support school planning and attendance. Category: School office Guide: https://avkul.in/docs/guides/module-calendar/ Guided sample demo: https://avkul.in/docs/demo/module-calendar/ Snapshot: 11 October 2026 ## Features - Calendar view - Working days - Holiday settings - Attendance policy - Event RSVP ## Access and 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. Permission keys: calendar:view, settings:update, calendar:create, calendar:update, calendar:delete, communication:manage ## Workflow 1. Review the selected calendar period. 2. Add or update a permitted holiday or event. 3. Check applicability to students and staff. 4. Review working days and RSVP summaries. ## Fields and controls - weekOffDays (number[], optional) - minAttendancePercent (number, optional) - dayStartsAt (string, optional) - name (string, optional) - description (string, optional) - startDate (string, optional) - endDate (string, optional) - type (string, optional) - appliesToStudents (boolean, optional) - appliesToStaff (boolean, optional) - sessionId (string, optional) - status (string, declared required) - guests (number, optional) - remark (string, optional) ## Current limits - Declaring a holiday requires its own permission. The attendance and timetable workflows use their documented calendar rules. ## Actual application access - https://avkul.in/en/school/calendar ## API reference - GET /api/v1/calendar — Feed; calendar:view - GET /api/v1/calendar/working-days — Working Days; calendar:view - GET /api/v1/calendar/is-holiday — Is Holiday; calendar:view - GET /api/v1/calendar/attendance-policy — Get Policy; calendar:view - PATCH /api/v1/calendar/attendance-policy — Set Policy; settings:update - GET /api/v1/calendar/holidays — List Holidays; calendar:view - POST /api/v1/calendar/holidays — Create Holiday; calendar:create - PATCH /api/v1/calendar/holidays/:id — Update Holiday; calendar:update - DELETE /api/v1/calendar/holidays/:id — Remove Holiday; calendar:delete - POST /api/v1/calendar/events/:id/rsvp — Rsvp; Authenticated scope - GET /api/v1/calendar/events/:id/rsvp/mine — My Rsvp; Authenticated scope - GET /api/v1/calendar/events/:id/rsvp/summary — Rsvp Summary; communication:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Certificates & verification Manage certificate templates, issue documents and provide token-based verification. Category: School office Guide: https://avkul.in/docs/guides/module-certificate/ Guided sample demo: https://avkul.in/docs/demo/module-certificate/ Snapshot: 11 October 2026 ## Features - Templates - Individual and bulk issue - Generated records - Revocation - Public verification ## Access and 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. Permission keys: certificate:view, certificate:create, certificate:update, certificate:delete ## Workflow 1. Choose or create a certificate template. 2. Select the eligible recipient and issue the document. 3. Review the generated certificate record. 4. Use the document verification token to check validity. ## Fields and controls - name (string, declared required) - type (string, declared required) - bodyHtml (string, optional) - paperSize (string, optional) - isActive (boolean, optional) - templateId (string, declared required) - studentId (string, optional) - staffId (string, optional) - dataJson (Record, optional) - items (BulkGenerateItemDto[], declared required) ## Current limits - Verification requires an actual generated token. Sample demo certificates are not school-issued documents. ## Actual application access - https://avkul.in/en/school/certificates - https://avkul.in/en/verify — select the actual record from this list. ## API reference - GET /api/v1/certificate/templates — List Templates; certificate:view - POST /api/v1/certificate/templates — Create Template; certificate:create - PATCH /api/v1/certificate/templates/:id — Update Template; certificate:update - DELETE /api/v1/certificate/templates/:id — Remove Template; certificate:delete - GET /api/v1/certificate/generated — List Generated; certificate:view - POST /api/v1/certificate/generated — Generate; certificate:create - POST /api/v1/certificate/generated/bulk — Bulk Generate; certificate:create - POST /api/v1/certificate/generated/:id/revoke — Revoke; certificate:update - GET /api/v1/certificate/verify/:qrToken — Verify; Public/capability access ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # College administration Manage department and semester structures, electives, internal marks, placements and research records. Category: Institutions Guide: https://avkul.in/docs/guides/module-college/ Guided sample demo: https://avkul.in/docs/demo/module-college/ Snapshot: 11 October 2026 ## Features - Departments - Semesters - Electives and enrollment - Internal marks - Placements - Research projects ## Access and 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. Permission keys: student:view, student:create, student:update, student:delete ## Workflow 1. Create the department and semester structure. 2. Offer electives with the required limits. 3. Record eligible enrollments and internal marks. 4. Maintain placement and research records. ## Fields and controls - name (string, optional) - code (string, declared required) - hodStaffId (string, optional) - description (string, optional) - totalSeats (number, optional) - departmentId (string, declared required) - semesterNo (number, declared required) - type (SemesterType, declared required) - startDate (string, optional) - endDate (string, optional) - totalCredits (number, optional) - isActive (boolean, optional) - subjectId (string, declared required) - semesterId (string, declared required) - maxStudents (number, optional) - credits (number, optional) - teacherStaffId (string, optional) - status (string, optional) - electiveId (string, declared required) - studentId (string, declared required) - assignment1 (number, optional) - assignment2 (number, optional) - midSem (number, optional) - attendance (number, optional) ## Current limits - College workflows share the school account and permission context; college-specific setup must exist. ## Actual application access - https://avkul.in/en/school/college ## API reference - GET /api/v1/college/stats — College overview stats; student:view - GET /api/v1/college/departments — List all departments; student:view - POST /api/v1/college/departments — Create a department; student:create - PATCH /api/v1/college/departments/:id — Update a department; student:update - DELETE /api/v1/college/departments/:id — Delete a department; student:delete - GET /api/v1/college/semesters — List semesters (filter by departmentId); student:view - POST /api/v1/college/semesters — Create a semester; student:create - PATCH /api/v1/college/semesters/:id — Update a semester; student:update - GET /api/v1/college/electives — List elective subjects (filter by semesterId); student:view - POST /api/v1/college/electives — Create an elective subject offering; student:create - PATCH /api/v1/college/electives/:id — Update elective (status, max students); student:update - POST /api/v1/college/electives/enroll — Enroll a student in an elective; student:create - GET /api/v1/college/internal-marks — List internal marks (filter by semesterId, studentId); student:view - POST /api/v1/college/internal-marks — Create internal marks entry; student:create - PATCH /api/v1/college/internal-marks/:id — Update internal marks; student:update - GET /api/v1/college/placements — List placement records (filter by status); student:view - POST /api/v1/college/placements — Create a placement record; student:create - PATCH /api/v1/college/placements/:id — Update placement status; student:update - GET /api/v1/college/research — List research projects (filter by departmentId); student:view - POST /api/v1/college/research — Create a research project; student:create - PATCH /api/v1/college/research/:id — Update a research project; student:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notices, announcements & messages Coordinate school notices, events, complaints, audience-based announcements and direct conversations. Category: Community Guide: https://avkul.in/docs/guides/module-communication/ Guided sample demo: https://avkul.in/docs/demo/module-communication/ Snapshot: 11 October 2026 ## Features - Notices and events - Announcement templates - Audience preview - Delivery report - Scoped messages - Complaints ## Access and 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. Permission keys: communication:view, communication:create, communication:update, communication:delete, communication:manage ## Workflow 1. Choose the notice, announcement or conversation workflow. 2. Select the permitted audience and prepare the content. 3. Preview reachability before sending where available. 4. Review delivery reports, replies or complaint status. ## Fields and controls - name (string, optional) - category (string, optional) - subject (string, optional) - body (string, declared required) - channels (string[], optional) - isActive (boolean, optional) - audience (string, optional) - targeting (AudienceTargetingDto, optional) - title (string, declared required) - message (string, optional) - templateId (string, optional) - scheduledAt (string, optional) - isPinned (boolean, optional) - classId (string, optional) - sectionId (string, optional) - expiresAt (string, optional) - description (string, optional) - startAt (string, declared required) - endAt (string, optional) - venue (string, optional) - rsvpEnabled (boolean, optional) - isAllDay (boolean, optional) - priority (string, optional) - studentId (string, optional) ## Current limits - External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it. ## Actual application access - https://avkul.in/en/school/announcements - https://avkul.in/en/school/communication - https://avkul.in/en/school/messages ## API reference - GET /api/v1/announcements/templates — List Templates; communication:view - POST /api/v1/announcements/templates — Create Template; communication:create - PATCH /api/v1/announcements/templates/:id — Update Template; communication:update - DELETE /api/v1/announcements/templates/:id — Remove Template; communication:delete - POST /api/v1/announcements/preview-audience — Count and channel-reachability for an audience; communication:view - GET /api/v1/announcements — List; communication:view - GET /api/v1/announcements/:id — Get; communication:view - GET /api/v1/announcements/:id/deliveries — Per-recipient delivery report; communication:view - POST /api/v1/announcements — Create; communication:create - POST /api/v1/announcements/:id/send — Deliver the announcement across its channels; communication:manage - GET /api/v1/communication/notices — Notices; communication:view - POST /api/v1/communication/notices — Create Notice; communication:create - PATCH /api/v1/communication/notices/:id — Update Notice; communication:update - DELETE /api/v1/communication/notices/:id — Remove Notice; communication:delete - GET /api/v1/communication/events — Events; communication:view - POST /api/v1/communication/events — Create Event; communication:create - DELETE /api/v1/communication/events/:id — Remove Event; communication:delete - GET /api/v1/communication/complaints — Complaints; communication:view - POST /api/v1/communication/complaints — Create Complaint; communication:create - PATCH /api/v1/communication/complaints/:id — Update Complaint; communication:update - GET /api/v1/messages/contacts — Addressable contacts for the signed-in user; Authenticated scope - GET /api/v1/messages — My conversations, most recent first; Authenticated scope - GET /api/v1/messages/:id — Get Thread; Authenticated scope - POST /api/v1/messages — Start a conversation (or add to the existing one); Authenticated scope - POST /api/v1/messages/:id/messages — Send; Authenticated scope - POST /api/v1/messages/:id/read — Mark Read; Authenticated scope - POST /api/v1/messages/:id/mute — Mute; Authenticated scope - DELETE /api/v1/messages/messages/:messageId — Withdraw your own message; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Discipline & behaviour Record incidents, review student standing and manage sanctions through dedicated access. Category: Student care Guide: https://avkul.in/docs/guides/module-discipline/ Guided sample demo: https://avkul.in/docs/demo/module-discipline/ Snapshot: 11 October 2026 ## Features - Incident register - Watchlist - Policy thresholds - Sanctions - Student summary ## Access and 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. Permission keys: discipline:view, discipline:manage, discipline:update, discipline:create, discipline:delete ## Workflow 1. Locate the student within your permitted scope. 2. Record the incident and relevant context. 3. Review standing and any suggested threshold action. 4. Schedule or close the appropriate sanction. ## Fields and controls - windowDays (number, optional) - warnAt (number, optional) - detentionAt (number, optional) - parentMeetingAt (number, optional) - suspensionReviewAt (number, optional) - notifyFamilyOnIncident (boolean, optional) - scheduledFor (string, declared required) - notes (string, optional) - served (boolean, declared required) - reason (string, optional) - studentId (string, declared required) - incidentDate (string, declared required) - category (string, optional) - description (string, declared required) - severity (string, optional) - actionTaken (string, optional) - demeritPoints (number, optional) - status (string, optional) ## Current limits - Behaviour records have dedicated sensitive-data permissions; general student access does not imply access. ## Actual application access - https://avkul.in/en/school/discipline ## API reference - 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 - GET /api/v1/discipline/students/:studentId/standing — Standing; discipline:view - POST /api/v1/discipline/sanctions/:id/schedule — Schedule; discipline:update - POST /api/v1/discipline/sanctions/:id/close — Close Sanction; discipline:update - GET /api/v1/discipline/students/:studentId/summary — Student Summary; discipline:view - POST /api/v1/discipline — Create; discipline:create - PATCH /api/v1/discipline/:id — Update; discipline:update - DELETE /api/v1/discipline/:id — Remove; discipline:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Examinations & results Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/module-exam/ Guided sample demo: https://avkul.in/docs/demo/module-exam/ Snapshot: 11 October 2026 ## Features - Exam schedules - Marks entry and history - Completion status - Grade scales - Report cards - Publish and unpublish - Seating and invigilation - Adaptive exams - Mark rechecks ## Access and 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. Permission keys: exam:view, exam:create, exam:update, exam:delete, exam:manage ## Workflow 1. Create the exam and its subject schedules. 2. Review the candidates, seating and completion status. 3. Record and verify marks, then generate report cards. 4. Publish approved results; use the correction workflow when required. ## Fields and controls - title (string, declared required) - subjectId (string, declared required) - classId (string, declared required) - sectionId (string, optional) - targetCount (number, optional) - durationMin (number, optional) - maxAttempts (number, optional) - questionIds (string[], optional) - publishResults (boolean, optional) - text (string, declared required) - options (string[], declared required) - correctAnswer (string, declared required) - difficulty (string, optional) - chapter (string, optional) - marks (number, optional) - status (string, optional) - name (string, declared required) - rows (number, optional) - seatsPerRow (number, optional) - blockedSeats (number, optional) - building (string, optional) - floor (string, optional) - isActive (boolean, optional) - scheduleId (string, declared required) ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/adaptive-exams/attempts — select the actual record from this list. - https://avkul.in/en/school/adaptive-exams - https://avkul.in/en/school/exam-seating - https://avkul.in/en/school/exams - https://avkul.in/en/school/exams — select the actual record from this list. - https://avkul.in/en/school/mark-rechecks ## API reference - GET /api/v1/adaptive-exams — List; exam:view - POST /api/v1/adaptive-exams — Create; exam:create - GET /api/v1/adaptive-exams/questions — List Questions; exam:view - POST /api/v1/adaptive-exams/questions — Create Question; exam:create - GET /api/v1/adaptive-exams/attempts/:attemptId — Attempt Detail; exam:view - GET /api/v1/adaptive-exams/:examId — Get Exam; exam:view - PATCH /api/v1/adaptive-exams/:examId/status — Update Status; exam:update - GET /api/v1/exam-seating/rooms — List Rooms; exam:view - POST /api/v1/exam-seating/rooms — Create Room; exam:create - PATCH /api/v1/exam-seating/rooms/:id — Update Room; exam:update - DELETE /api/v1/exam-seating/rooms/:id — Remove Room; exam:delete - POST /api/v1/exam-seating/allocate — Seat every candidate for one paper; exam:manage - DELETE /api/v1/exam-seating/schedules/:scheduleId/seats — Clear; exam:manage - GET /api/v1/exam-seating/schedules/:scheduleId/plan — Room-by-room seating chart for a paper; exam:view - POST /api/v1/exam-seating/invigilators — Assign Invigilator; exam:update - DELETE /api/v1/exam-seating/invigilators/:id — Remove Invigilator; exam:update - GET /api/v1/exam-seating/invigilators/staff/:staffId — One staff member's invigilation duty chart; exam:view - GET /api/v1/exam-seating/admit-card/:examId/:studentId — A candidate's papers with room and seat; exam:view - GET /api/v1/exams — List; exam:view - POST /api/v1/exams — Create; exam:create - PATCH /api/v1/exams/:id — Update; exam:update - DELETE /api/v1/exams/:id — Remove; exam:delete - GET /api/v1/exams/:examId/schedules — List Schedules; exam:view - GET /api/v1/exams/:examId/completion — Completion; exam:view - POST /api/v1/exams/:examId/schedules — Create Schedule; exam:update - POST /api/v1/exams/:examId/report-cards/generate — Compute report cards for a section in this exam; exam:update - GET /api/v1/exams/:examId/report-cards — Report Cards; exam:view - POST /api/v1/exams/:examId/report-cards/publish — Publish report cards to the parent/student portal; exam:manage - POST /api/v1/exams/:examId/report-cards/unpublish — Withdraw published results to issue a correction; exam:manage - PATCH /api/v1/exam-schedules/:id — Update; exam:update - DELETE /api/v1/exam-schedules/:id — Remove; exam:delete - GET /api/v1/exam-schedules/:id/marks — Marks-entry roster for a schedule; exam:view - GET /api/v1/exam-schedules/:id/marks/history — History; exam:view - POST /api/v1/exam-schedules/:id/marks — Save Marks; exam:update - GET /api/v1/grade-scales — List; exam:view - POST /api/v1/grade-scales — Create; exam:update - DELETE /api/v1/grade-scales/:id — Remove; exam:delete - GET /api/v1/report-cards/:id — Get; exam:view - GET /api/v1/mark-rechecks — List; exam:view - POST /api/v1/mark-rechecks — Query a published mark; Authenticated scope - POST /api/v1/mark-rechecks/:id/review — Acknowledge that the paper is being re-read; exam:manage - POST /api/v1/mark-rechecks/:id/decision — Uphold, revise or reject a recheck; exam:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Fee structures & collections Configure charges, preview billing, issue invoices and record collections and adjustments. Category: Finance Guide: https://avkul.in/docs/guides/module-fee/ Guided sample demo: https://avkul.in/docs/demo/module-fee/ Snapshot: 11 October 2026 ## Features - Fee types and structures - Billing preview - Invoice generation - Collections and receipts - Dues ageing - Concessions - Refunds and reversals ## Access and 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. Permission keys: fee:view, fee:manage, fee:create, fee:update, fee:delete ## Workflow 1. Create the required fee structure and installments. 2. Preview eligible students and existing invoices. 3. Generate invoices and record a valid collection. 4. Review the receipt, remaining balance and adjustment history. ## Fields and controls - reference (string, optional) - note (string, optional) - amount (number, optional) - reason (string, declared required) - name (string, optional) - code (string, optional) - isRecurring (boolean, optional) - isOptional (boolean, optional) - classId (string, optional) - studentId (string, declared required) - sessionId (string, optional) - items (InvoiceItemInput[], declared required) - structureId (string, declared required) - installmentNo (number, optional) - sectionId (string, optional) - dueDate (string, optional) - notes (string, optional) - type (string, declared required) - value (number, declared required) - feeTypeId (string, optional) - isActive (boolean, optional) - discountId (string, optional) - status (string, declared required) - studentIds (string[], optional) ## Current limits - A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation. ## Actual application access - https://avkul.in/en/school/fee-structures - https://avkul.in/en/school/fees ## API reference - GET /api/v1/fees/collections — Collections List; fee:view - GET /api/v1/fees/collections/summary — Collections Summary; fee:view - GET /api/v1/fees/payments/:id/receipt — Receipt; fee:view - POST /api/v1/fees/payments/:id/reconcile — Reconcile Collection; fee:manage - POST /api/v1/fees/invoices/:id/fine — Fine; fee:manage - GET /api/v1/fees/types — List Types; fee:view - POST /api/v1/fees/types — Create Type; fee:create - GET /api/v1/fees/structures — List Structures; fee:view - GET /api/v1/fees/structures/:id — Get Structure; fee:view - POST /api/v1/fees/structures — Create Structure; fee:create - PATCH /api/v1/fees/structures/:id — Update Structure; fee:update - DELETE /api/v1/fees/structures/:id — Remove Structure; fee:delete - POST /api/v1/fees/generate/preview — Who would be billed, for how much, and who is already invoiced; fee:view - POST /api/v1/fees/generate — Generate invoices for every eligible student; fee:manage - GET /api/v1/fees/concessions/schemes — Concession schemes the school offers; fee:view - POST /api/v1/fees/concessions/schemes — Create Scheme; fee:manage - PATCH /api/v1/fees/concessions/schemes/:id — Update Scheme; fee:manage - DELETE /api/v1/fees/concessions/schemes/:id — Remove Scheme; fee:manage - GET /api/v1/fees/concessions/report — What the school has awarded, and what it has cost; fee:view - GET /api/v1/fees/concessions — List Awards; fee:view - POST /api/v1/fees/concessions — Award a concession to a student (starts as REQUESTED); fee:update - POST /api/v1/fees/concessions/:id/decision — Approve or refuse a requested concession; fee:manage - DELETE /api/v1/fees/concessions/:id — Withdraw an award; issued invoices keep their discount; fee:manage - GET /api/v1/fees/invoices — List Invoices; fee:view - GET /api/v1/fees/defaulters — Invoices with an outstanding balance; fee:view - GET /api/v1/fees/dues/ageing — Outstanding fees aged per student; fee:view - POST /api/v1/fees/dues/reminders — Send a payment reminder to fee-paying guardians; fee:manage - GET /api/v1/fees/invoices/:id — Get Invoice; fee:view - POST /api/v1/fees/invoices — Create Invoice; fee:create - POST /api/v1/fees/invoices/:id/payments — Collect a payment against an invoice; fee:update - POST /api/v1/fees/payments/:paymentId/refund — Refund a collected payment (full or partial); fee:manage - POST /api/v1/fees/invoices/:id/write-off — Forgive outstanding balance; fee:manage - POST /api/v1/fees/invoices/:id/discount — Apply a concession/scholarship discount; fee:manage - POST /api/v1/fees/invoices/:id/cancel — Void an invoice raised in error; fee:manage - POST /api/v1/fees/adjustments/:id/reverse — Undo a discount / write-off / cancellation; fee:manage - GET /api/v1/fees/invoices/:id/adjustments — Invoice Adjustments; fee:view - GET /api/v1/fees/adjustments/summary — Totals discounted, written off and refunded over a period; fee:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Health records & infirmary Maintain school health information and record infirmary visits, medication entries and closures. Category: Student care Guide: https://avkul.in/docs/guides/module-health/ Guided sample demo: https://avkul.in/docs/demo/module-health/ Snapshot: 11 October 2026 ## Features - Health profiles - Emergency contact - Infirmary visits - Medication records - Frequent-visit review ## Access and 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. Permission keys: health:view, health:update ## Workflow 1. Find the permitted student health profile. 2. Review emergency and health information. 3. Record the infirmary visit and permitted medication details. 4. Close the visit and review repeated visits where relevant. ## Fields and controls - bloodGroup (string, optional) - allergies (string, optional) - chronicConditions (string, optional) - medications (string, optional) - emergencyContactName (string, optional) - emergencyContactPhone (string, optional) - heightCm (number, optional) - weightKg (number, optional) - lastCheckupDate (string, optional) - vaccinationJson (Record, optional) - notes (string, optional) - studentId (string, declared required) - complaint (string, declared required) - observations (string, optional) - temperatureC (number, optional) - outcome ('OPEN' | 'RETURNED_TO_CLASS' | 'RESTING' | 'SENT_HOME' | 'REFERRED_HOSPITAL', declared required) - treatment (string, optional) - medicine (string, declared required) - visitId (string, optional) - dose (string, optional) - route (string, optional) - consentSource (string, optional) ## Current limits - Access is restricted by dedicated health permissions. Sample walkthrough information is fictional and is not medical advice. ## Actual application access - https://avkul.in/en/school/health-records ## API reference - GET /api/v1/health-records — List; health:view - GET /api/v1/health-records/students/:studentId — Get By Student; health:view - PUT /api/v1/health-records/students/:studentId — Upsert; health:update - GET /api/v1/infirmary/visits — List Visits; health:view - GET /api/v1/infirmary/frequent-visitors — Students in the sick room unusually often; health:view - GET /api/v1/infirmary/students/:studentId/alerts — Alerts; health:view - POST /api/v1/infirmary/visits — Book a child into the sick room; health:update - POST /api/v1/infirmary/visits/:id/close — Close Visit; health:update - POST /api/v1/infirmary/medications — Record a dose given on school premises; health:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Hostel, rooms & roll call Manage residence capacity, room/bed allocations, visitor logs and nightly attendance. Category: Campus Guide: https://avkul.in/docs/guides/module-hostel/ Guided sample demo: https://avkul.in/docs/demo/module-hostel/ Snapshot: 11 October 2026 ## Features - Hostels and rooms - Beds - Resident allocations - Visitor check-in/out - Night roll call - Missing residents ## Access and 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. Permission keys: hostel:view, hostel:create, hostel:update, hostel:delete ## Workflow 1. Set up the hostel, rooms and beds. 2. Allocate eligible residents to available accommodation. 3. Record and check out permitted visitors. 4. Open the roll call, mark residents and close the register. ## Fields and controls - name (string, declared required) - type (string, optional) - wardenStaffId (string, optional) - address (string, optional) - hostelId (string, declared required) - roomNo (string, declared required) - floor (string, optional) - capacity (number, optional) - fare (number, optional) - roomId (string, declared required) - bedNo (string, declared required) - studentId (string, optional) - bedId (string, declared required) - fromDate (string, declared required) - toDate (string, optional) - visitorName (string, declared required) - purpose (string, optional) - idProof (string, optional) - outTime (string, optional) - date (string, optional) - marks (ResidentMarkDto[], declared required) - force (boolean, optional) - notes (string, optional) ## Current limits - Capacity and allocation state must be reviewed before assignment. Family notification delivery depends on the available channel. ## Actual application access - https://avkul.in/en/school/hostel ## API reference - GET /api/v1/hostel/stats — Get Stats; hostel:view - GET /api/v1/hostel/my-allocation — My Allocation; Authenticated scope - GET /api/v1/hostel/hostels — List Hostels; hostel:view - POST /api/v1/hostel/hostels — Create Hostel; hostel:create - PATCH /api/v1/hostel/hostels/:id — Update Hostel; hostel:update - DELETE /api/v1/hostel/hostels/:id — Remove Hostel; hostel:delete - GET /api/v1/hostel/rooms — List Rooms; hostel:view - POST /api/v1/hostel/rooms — Create Room; hostel:create - PATCH /api/v1/hostel/rooms/:id — Update Room; hostel:update - DELETE /api/v1/hostel/rooms/:id — Remove Room; hostel:delete - GET /api/v1/hostel/beds — List Beds; hostel:view - POST /api/v1/hostel/beds — Create Bed; hostel:create - PATCH /api/v1/hostel/beds/:id — Update Bed; hostel:update - DELETE /api/v1/hostel/beds/:id — Remove Bed; hostel:delete - GET /api/v1/hostel/allocations — List Allocations; hostel:view - POST /api/v1/hostel/allocations — Create Allocation; hostel:create - PATCH /api/v1/hostel/allocations/:id — Update Allocation; hostel:update - POST /api/v1/hostel/allocations/:id/vacate — Vacate Allocation; hostel:update - GET /api/v1/hostel/visitor-logs — List Visitor Logs; hostel:view - POST /api/v1/hostel/visitor-logs — Create Visitor Log; hostel:create - PATCH /api/v1/hostel/visitor-logs/:id — Update Visitor Log; hostel:update - POST /api/v1/hostel/visitor-logs/:id/checkout — Checkout Visitor; hostel:update - DELETE /api/v1/hostel/visitor-logs/:id — Remove Visitor Log; hostel:delete - GET /api/v1/hostel/roll-call/missing — Residents not accounted for, and hostels with no roll call at all; hostel:view - GET /api/v1/hostel/roll-call/:id — Register; hostel:view - POST /api/v1/hostel/roll-call/open — Open tonight's register for a hostel; hostel:update - POST /api/v1/hostel/roll-call/:id/mark — Mark; hostel:update - POST /api/v1/hostel/roll-call/:id/close — Close the night; families of absent residents are told; hostel:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Payroll & salary structures Prepare salary structures, process payroll, review approvals and maintain salary slips. Category: People Guide: https://avkul.in/docs/guides/module-hr/ Guided sample demo: https://avkul.in/docs/demo/module-hr/ Snapshot: 11 October 2026 ## Features - Salary structures - Payroll processing - Approval - Mark paid - Salary slips - PDF generation ## Access and 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. Permission keys: payroll:view, payroll:create, payroll:update, payroll:delete, payroll:manage ## Workflow 1. Create the applicable salary structure. 2. Process payroll for the selected period. 3. Review calculations and approve the run. 4. Record payment status and review salary slips. ## Fields and controls - name (string, declared required) - staffId (string, optional) - basic (number, declared required) - componentsJson (SalaryComponentDto[], optional) - ctc (number, optional) - effectiveFrom (string, optional) - isActive (boolean, optional) - month (number, declared required) - year (number, declared required) - applyLossOfPay (boolean, optional) - paidDays (number, optional) - loanRecovery (number, optional) - tax (number, optional) ## Current limits - Marking payroll paid records an administrative state; this feature does not by itself transfer money to a bank. ## Actual application access - https://avkul.in/en/school/payroll ## API reference - GET /api/v1/hr/salary-structures — List Structures; payroll:view - POST /api/v1/hr/salary-structures — Create Structure; payroll:create - PATCH /api/v1/hr/salary-structures/:id — Update Structure; payroll:update - DELETE /api/v1/hr/salary-structures/:id — Remove Structure; payroll:delete - GET /api/v1/hr/payrolls — List Payrolls; payroll:view - GET /api/v1/hr/payrolls/:id — Get Payroll; payroll:view - POST /api/v1/hr/payrolls/process — Process Payroll; payroll:manage - POST /api/v1/hr/payrolls/:id/approve — Approve Payroll; payroll:manage - POST /api/v1/hr/payrolls/:id/mark-paid — Mark Paid; payroll:manage - GET /api/v1/hr/salary-slips — List Slips; payroll:view - PATCH /api/v1/hr/salary-slips/:id — Update Slip; payroll:update - POST /api/v1/hr/salary-slips/:id/generate-pdf — Generate Slip Pdf; payroll:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Inventory & purchases Manage supplies, procurement, stock movements and issued school property. Category: Campus Guide: https://avkul.in/docs/guides/module-inventory/ Guided sample demo: https://avkul.in/docs/demo/module-inventory/ Snapshot: 11 October 2026 ## Features - Items and vendors - Purchase orders - Approval and partial receipt - Stock transactions - Low stock - Asset issue/return - History and export ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Accountant, Store Keeper, Inventory Manager - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. Permission keys: inventory:view, inventory:create, inventory:update, inventory:manage ## Workflow 1. Create an item and supplier with the relevant stock unit. 2. Prepare and submit a purchase order for review. 3. Receive accepted quantities and inspect stock movements. 4. Issue or return property and review outstanding balances. ## Fields and controls - name (string, declared required) - category (string, optional) - sku (string, optional) - unit (string, optional) - quantity (number, declared required) - reorderLevel (number, optional) - unitPrice (number, optional) - contact (string, optional) - phone (string, optional) - email (string, optional) - gstin (string, optional) - address (string, optional) - poNumber (string, declared required) - vendorId (string, declared required) - expectedAt (string, optional) - notes (string, optional) - items (InvPoLineDto[], declared required) - id (string, optional) - version (string, optional) - reason (string, optional) - action (string, declared required) - reference (string, declared required) - lines (InvReceiveLineDto[], declared required) - itemId (string, declared required) ## Current limits - Purchase totals exclude tax/freight and supplier accounting. Valuation uses reference prices, not FIFO or weighted-average accounting. ## Actual application access - https://avkul.in/en/school/inventory ## API reference - GET /api/v1/inventory/workspace — Workspace; inventory:view - GET /api/v1/inventory/items — Items; inventory:view - POST /api/v1/inventory/items — Item; inventory:create - PATCH /api/v1/inventory/items/:id — Edit Item; inventory:update - GET /api/v1/inventory/vendors — Vendors; inventory:view - POST /api/v1/inventory/vendors — Vendor; inventory:create - PATCH /api/v1/inventory/vendors/:id — Edit Vendor; inventory:update - GET /api/v1/inventory/purchase-orders — Orders; inventory:view - POST /api/v1/inventory/purchase-orders — Po; inventory:create - PATCH /api/v1/inventory/purchase-orders/:id — Edit Po; inventory:update - POST /api/v1/inventory/purchase-orders/:id/submit — Submit; inventory:update - POST /api/v1/inventory/purchase-orders/:id/cancel — Cancel; inventory:update - POST /api/v1/inventory/purchase-orders/:id/decision — Decide; inventory:manage - POST /api/v1/inventory/purchase-orders/:id/receive — Receive; inventory:update - GET /api/v1/inventory/stock-txns — Stock; inventory:view - POST /api/v1/inventory/stock-txns — Move; inventory:create - GET /api/v1/inventory/low-stock — Low; inventory:view - GET /api/v1/inventory/issues/outstanding — Outstanding; inventory:view - POST /api/v1/inventory/issues — Issue; inventory:create - POST /api/v1/inventory/issues/:id/return — Return Asset; inventory:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff leave & student absences Keep staff leave requests and student absence reports in their respective review workflows. Category: People Guide: https://avkul.in/docs/guides/module-leave/ Guided sample demo: https://avkul.in/docs/demo/module-leave/ Snapshot: 11 October 2026 ## Features - Self-service staff leave - Pending review - Approve or reject - Student absence report - Approval and cancellation ## Access and 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. Permission keys: hr:view, hr:update, attendance:view, attendance:manage ## Workflow 1. Choose staff leave or student absence reporting. 2. Enter the applicable dates and reason. 3. Submit or review through the permitted role. 4. Check the final decision and attendance impact. ## Fields and controls - leaveType (string, optional) - fromDate (string, declared required) - toDate (string, optional) - reason (string, optional) - status ('APPROVED' | 'REJECTED', declared required) - autoAssignCover (boolean, optional) - remark (string, optional) - studentId (string, declared required) - attachmentUrl (string, optional) - approve (boolean, declared required) ## Current limits - Staff and student approval rules differ. The family view resolves linked-child ownership. ## Actual application access - https://avkul.in/en/school/staff-leave - https://avkul.in/en/school/student-leave ## API reference - POST /api/v1/leave/apply — Self-service: apply for leave (resolves the caller's own staff profile); Authenticated scope - GET /api/v1/leave/mine — Self-service: my own leave history; Authenticated scope - 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 - POST /api/v1/student-leave — Report a planned or past absence for a student; Authenticated scope - GET /api/v1/student-leave/mine — Absences reported for my own children; Authenticated scope - GET /api/v1/student-leave — List; attendance:view - PATCH /api/v1/student-leave/:id/decision — Approve an absence, marking those days excused; attendance:manage - PATCH /api/v1/student-leave/:id/cancel — Cancel; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # General ledger Maintain account records and post balanced double-entry journals with auditable reversals. Category: Finance Guide: https://avkul.in/docs/guides/module-ledger/ Guided sample demo: https://avkul.in/docs/demo/module-ledger/ Snapshot: 11 October 2026 ## Features - Chart of accounts - Balanced journals - Journal reversal - Trial balance - Income statement ## Access and 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. Permission keys: fee:view, fee:manage ## Workflow 1. Review or seed the chart of accounts. 2. Prepare matching debit and credit lines. 3. Post the balanced journal and inspect its record. 4. Use a reversal to correct an entry without erasing the original. ## Fields and controls - name (string, declared required) - code (string, optional) - type (string, declared required) - parentId (string, optional) - isPostable (boolean, optional) - isActive (boolean, optional) - lines (JournalLineDto[], declared required) - entryDate (string, optional) - narration (string, optional) - source (string, optional) - sourceRef (string, optional) ## Current limits - Debits and credits must balance. Ledger recording is not a bank settlement or a statutory filing. ## Actual application access - https://avkul.in/en/school/ledger ## API reference - GET /api/v1/ledger/accounts — List Accounts; fee:view - POST /api/v1/ledger/accounts — Create Account; fee:manage - POST /api/v1/ledger/accounts/seed-defaults — Create a standard chart of accounts, skipping what exists; fee:manage - PATCH /api/v1/ledger/accounts/:id — Update Account; fee:manage - DELETE /api/v1/ledger/accounts/:id — Remove Account; fee:manage - GET /api/v1/ledger/journals — List Journals; fee:view - POST /api/v1/ledger/journals — Post a balanced double-entry transaction; fee:manage - POST /api/v1/ledger/journals/:id/reverse — Post the mirror image; the original stays on the record; fee:manage - GET /api/v1/ledger/trial-balance — Every account with its debit/credit totals; fee:view - GET /api/v1/ledger/income-statement — Income, expenditure and surplus for a period; fee:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Library & circulation Maintain titles and copies, lend books, manage reservations and handle fines. Category: Campus Guide: https://avkul.in/docs/guides/module-library/ Guided sample demo: https://avkul.in/docs/demo/module-library/ Snapshot: 11 October 2026 ## Features - Book catalogue - Copy availability - Issue and return - Renewal - Reservations - Library policy - Fine collection and waiver ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Librarian - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. Permission keys: library:view, library:create, library:update, library:delete, library:manage ## Workflow 1. Create a title and its physical copies. 2. Check borrower eligibility and issue an available copy. 3. Return or renew the loan and review reservations. 4. Review overdue items and any permitted fine action. ## Fields and controls - title (string, declared required) - author (string, optional) - publisher (string, optional) - isbn (string, optional) - category (string, optional) - edition (string, optional) - rackNo (string, optional) - price (number, optional) - id (string, optional) - version (string, optional) - reason (string, optional) - bookId (string, declared required) - barcode (string, declared required) - status (string, optional) - copyId (string, declared required) - dueDate (string, optional) - condition (string, declared required) - additionalCharge (number, optional) - loanDays (number, optional) - finePerDay (number, optional) - graceDays (number, optional) - maxBooksPerBorrower (number, optional) - maxFinePerIssue (number, optional) - blockIssueOverDues (number, optional) ## Current limits - Availability, borrower policy and reservation rules affect issue/renewal. A fine record is distinct from a fee gateway payment. ## Actual application access - https://avkul.in/en/school/library ## API reference - GET /api/v1/library/workspace — Workspace; library:view - GET /api/v1/library/books — Books; library:view - GET /api/v1/library/copies — Copies; library:view - GET /api/v1/library/issues — Issues; library:view - GET /api/v1/library/overdue — Overdue; library:view - POST /api/v1/library/books — Book; library:create - PATCH /api/v1/library/books/:id — Edit Book; library:update - DELETE /api/v1/library/books/:id — Delete Book; library:delete - POST /api/v1/library/copies — Copy; library:create - PATCH /api/v1/library/copies/:id — Edit Copy; library:update - DELETE /api/v1/library/copies/:id — Delete Copy; library:delete - POST /api/v1/library/issues — Issue; library:create - POST /api/v1/library/issues/:id/return — Return Book; library:update - POST /api/v1/library/issues/:id/renew — Renew; library:update - POST /api/v1/library/issues/:id/remind — Remind; library:update - POST /api/v1/library/reservations — Reserve; library:create - POST /api/v1/library/reservations/:id/cancel — Cancel; library:update - GET /api/v1/library/policy — Policy; library:view - PATCH /api/v1/library/policy — Set Policy; library:manage - GET /api/v1/library/fines/outstanding — Outstanding; library:view - GET /api/v1/library/issues/:id/fine — Summary; library:view - POST /api/v1/library/issues/:id/fine/collect — Collect; library:update - POST /api/v1/library/issues/:id/fine/waive — Waive; library:manage - POST /api/v1/library/fines/:id/void — Void; library:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Live classes & recordings Schedule live lessons, manage their lifecycle and maintain recordings where configured. Category: Academics Guide: https://avkul.in/docs/guides/module-live-classes/ Guided sample demo: https://avkul.in/docs/demo/module-live-classes/ Snapshot: 11 October 2026 ## Features - Class schedule - Start and end - Learner join view - Recording upload - Chunk finalize and recovery ## Access and 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. Permission keys: live-class:view, live-class:create, live-class:update, live-class:delete ## Workflow 1. Create the class for the intended learners. 2. Review the scheduled time and class details. 3. Start the class and use the available joining experience. 4. End the session and review an available recording. ## Fields and controls - title (string, optional) - classId (string, declared required) - sectionId (string, optional) - subjectId (string, optional) - scheduledAt (string, optional) - durationMin (number, optional) ## Current limits - Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity. ## Actual application access - https://avkul.in/en/school/live-classes - https://avkul.in/en/school/live-classes — select the actual record from this list. ## API reference - GET /api/v1/live-classes — List; live-class:view - GET /api/v1/live-classes/:id — Get; live-class:view - POST /api/v1/live-classes — Create; live-class:create - PATCH /api/v1/live-classes/:id — Update; live-class:update - POST /api/v1/live-classes/:id/cancel — Cancel; live-class:update - DELETE /api/v1/live-classes/:id — Remove; live-class:delete - POST /api/v1/live-classes/:id/start — Start; live-class:update - POST /api/v1/live-classes/:id/end — End; live-class:update - POST /api/v1/live-classes/:id/recording — Save Recording; live-class:update - POST /api/v1/live-classes/:id/recording/chunk — Append Recording Chunk; live-class:update - POST /api/v1/live-classes/:id/recording/finalize — Finalize Recording; live-class:update - POST /api/v1/live-classes/:id/recording/recover — Recover Recording; live-class:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Courses & lessons Build a course structure and let learners open lessons and record progress. Category: Academics Guide: https://avkul.in/docs/guides/module-lms/ Guided sample demo: https://avkul.in/docs/demo/module-lms/ Snapshot: 11 October 2026 ## Features - Course catalogue - Modules - Lessons - Video assets - Publishing - Learner progress ## Access and 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. Permission keys: lms:view, lms:create, lms:update, lms:delete ## Workflow 1. Create a course and its details. 2. Add modules and lessons in the intended order. 3. Attach supported learning media and review visibility. 4. Open the learner course view and track lesson progress. ## Fields and controls - title (string, declared required) - description (string, optional) - subjectId (string, optional) - classId (string, optional) - isPublished (boolean, optional) - sortOrder (number, optional) - contentType (string, declared required) - videoUrl (string, optional) - body (string, optional) - durationMin (number, optional) ## Current limits - A course must be available to the learner before it appears in self-service. Video delivery depends on the stored asset and browser support. ## Actual application access - https://avkul.in/en/school/lms - https://avkul.in/en/school/lms — select the actual record from this list. ## API reference - GET /api/v1/lms/courses — List Courses; lms:view - GET /api/v1/lms/courses/:id — Get Course; lms:view - POST /api/v1/lms/courses — Create Course; lms:create - PATCH /api/v1/lms/courses/:id — Update Course; lms:update - DELETE /api/v1/lms/courses/:id — Remove Course; lms:delete - POST /api/v1/lms/courses/:id/modules — Add Module; lms:update - DELETE /api/v1/lms/modules/:id — Remove Module; lms:update - POST /api/v1/lms/modules/:id/lessons — Add Lesson; lms:update - DELETE /api/v1/lms/lessons/:id — Remove Lesson; lms:update - POST /api/v1/lms/lessons/:id/video — Upload Lesson Video; lms:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Marketing & conversion workspace Connect the public AVKUL ERP website with enquiries, campaign performance, content management and follow-up work. Category: Growth Guide: https://avkul.in/docs/guides/module-marketing/ Guided sample demo: https://avkul.in/docs/demo/module-marketing/ Snapshot: 11 October 2026 ## Features - Demo CRM - Demo calendar and tasks - Campaign Manager - Website analytics - Landing Page CMS - Media Library ## Access and setup Intended access: Platform administrator - A platform administrator account. - The academic, student or staff setup used by this workflow. ## Workflow 1. Publish reviewed landing content and choose its media. 2. Create a trackable campaign link. 3. Review accepted walkthrough enquiries in CRM. 4. Schedule demos and follow-ups and monitor measured conversion. ## Fields and controls - content (Record, declared required) - draftId (string, declared required) - revisionId (string, declared required) - source (string, declared required) - medium (string, declared required) - version (number, declared required) - status (string, declared required) - assignedToId (string|null, optional) - followUpAt (string | null, optional) - demoAt (string | null, optional) - note (string, optional) - name (string, declared required) - title (string, declared required) - altText (string, declared required) - folderId (string|null, declared required) - x (number, declared required) - y (number, declared required) - width (number, declared required) - height (number, declared required) - dueAt (string, declared required) - priority (string, declared required) - leadId (string|null, optional) - action (string, declared required) - at (string, optional) ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/landing-page - https://avkul.in/en/saas/marketing-campaigns - https://avkul.in/en/saas/marketing-leads - https://avkul.in/en/saas/marketing-workspace - https://avkul.in/en/saas/media - https://avkul.in/en/saas/website-analytics ## API reference - GET /api/v1/saas/landing-page — Workspace; Platform admin - GET /api/v1/saas/landing-page/versions/:id — Revision; Platform admin - POST /api/v1/saas/landing-page/draft — Save; Platform admin - POST /api/v1/saas/landing-page/preview — Preview; Platform admin - POST /api/v1/saas/landing-page/publish — Publish; Platform admin - POST /api/v1/saas/landing-page/restore — Restore; Platform admin - GET /api/v1/public/landing — Html; Public/capability access - GET /api/v1/saas/marketing-campaigns — List; Platform admin - GET /api/v1/saas/marketing-campaigns/export — Export; Platform admin - POST /api/v1/saas/marketing-campaigns — Create; Platform admin - GET /api/v1/saas/marketing-campaigns/:id — Get; Platform admin - PATCH /api/v1/saas/marketing-campaigns/:id — Update; Platform admin - GET /api/v1/saas/marketing-leads — List; Platform admin - GET /api/v1/saas/marketing-leads/owners — Owners; Platform admin - GET /api/v1/saas/marketing-leads/export — Export; Platform admin - GET /api/v1/saas/marketing-leads/:id — Get; Platform admin - PATCH /api/v1/saas/marketing-leads/:id — Update; Platform admin - POST /api/v1/saas/marketing-leads/:id/notes — Note; Platform admin - GET /api/v1/saas/media — List; Platform admin - GET /api/v1/saas/media/folders — Folders; Platform admin - POST /api/v1/saas/media/folders — Create Folder; Platform admin - PATCH /api/v1/saas/media/folders/:id — Update Folder; Platform admin - POST /api/v1/saas/media/folders/:id/remove — Remove Folder; Platform admin - POST /api/v1/saas/media/upload — Upload; Platform admin - GET /api/v1/saas/media/:id — Get; Platform admin - PATCH /api/v1/saas/media/:id — Update; Platform admin - POST /api/v1/saas/media/:id/crop — Crop; Platform admin - POST /api/v1/saas/media/:id/archive — Archive; Platform admin - POST /api/v1/saas/media/:id/restore — Restore; Platform admin - GET /api/v1/public/media/:id/:variant.webp — File; Public/capability access - GET /api/v1/saas/marketing-workspace — List; Platform admin - GET /api/v1/saas/marketing-workspace/leads — Leads; Platform admin - GET /api/v1/saas/marketing-workspace/tasks/:id — Task; Platform admin - POST /api/v1/saas/marketing-workspace/tasks — Create; Platform admin - PATCH /api/v1/saas/marketing-workspace/tasks/:id — Update; Platform admin - POST /api/v1/saas/marketing-workspace/leads/:id/demo — Demo; Platform admin - POST /api/v1/saas/marketing-workspace/leads/:id/follow-up — Follow; Platform admin - POST /api/v1/public/enquiries — Save a AVKUL ERP walkthrough or privacy enquiry; does not send outbound messages; Public/capability access - POST /api/v1/public/website-events — Track; Public/capability access - GET /api/v1/saas/website-analytics — Report; Platform admin - GET /api/v1/saas/website-analytics/export — Export; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Family & personal workspace Let families, learners and staff see only their linked children or personal records. Category: Family portal Guide: https://avkul.in/docs/guides/module-me/ Guided sample demo: https://avkul.in/docs/demo/module-me/ Snapshot: 11 October 2026 ## Features - Linked children - Attendance and fees - Published results - Homework and courses - Timetable - Library - PTM - Transport - Personal documents ## Access and setup Intended access: Linked parent / learner account - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. ## Workflow 1. Sign in with the assigned account. 2. Select the linked child where a selector is available. 3. Open the relevant learning or school-service screen. 4. Review the record or complete the permitted self-service action. ## Fields and controls - token (string, declared required) - platform (string, declared required) - studentId (string, optional) - interests (string, optional) - psychometric (Record, optional) - opportunityType (string, optional) - interestArea (string, optional) ## Current limits - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/ask - https://avkul.in/en/portal/attendance - https://avkul.in/en/portal/bus - https://avkul.in/en/portal/complaints - https://avkul.in/en/portal/exams - https://avkul.in/en/portal/explain - https://avkul.in/en/portal/fees - https://avkul.in/en/portal/homework - https://avkul.in/en/portal/journey - https://avkul.in/en/portal/learning-path - https://avkul.in/en/portal/leave - https://avkul.in/en/portal/library - https://avkul.in/en/portal/live-classes - https://avkul.in/en/portal/live-classes — select the actual record from this list. - https://avkul.in/en/portal/lms - https://avkul.in/en/portal/lms — select the actual record from this list. - https://avkul.in/en/portal/notices - https://avkul.in/en/portal - https://avkul.in/en/portal/profile - https://avkul.in/en/portal/ptm - https://avkul.in/en/portal/results - https://avkul.in/en/portal/timetable - https://avkul.in/en/portal/wellbeing - https://avkul.in/en/school/my-department - https://avkul.in/en/school/my-payslips ## API reference - GET /api/v1/me/library — Library; Authenticated scope - POST /api/v1/me/library/reservations — Library Reserve; Authenticated scope - POST /api/v1/me/library/reservations/:id/cancel — Library Cancel; Authenticated scope - POST /api/v1/me/library/issues/:id/renew — Library Renew; Authenticated scope - GET /api/v1/me/timetable — Timetable; Authenticated scope - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/profile — Profile; Authenticated scope - GET /api/v1/me/attendance — Attendance; Authenticated scope - GET /api/v1/me/attendance/calendar — Attendance Calendar; Authenticated scope - GET /api/v1/me/health — My Health; Authenticated scope - GET /api/v1/me/certificates — My Certificates; Authenticated scope - GET /api/v1/me/wellbeing — My Wellbeing; Authenticated scope - GET /api/v1/me/documents — My Documents; Authenticated scope - GET /api/v1/me/payslips — The signed-in staff member's own payslips; Authenticated scope - GET /api/v1/me/payslips/:id — My Payslip; Authenticated scope - GET /api/v1/me/fees — Fees; Authenticated scope - GET /api/v1/me/fees/receipts/:id — Fee Receipt; Authenticated scope - GET /api/v1/me/results — Results; Authenticated scope - GET /api/v1/me/results/:id/print — Result Print; Authenticated scope - GET /api/v1/me/inbox — Inbox; Authenticated scope - GET /api/v1/me/inbox/unread-count — Unread Count; Authenticated scope - POST /api/v1/me/inbox/:id/read — Mark Read; Authenticated scope - POST /api/v1/me/inbox/read-all — Mark All Read; Authenticated scope - GET /api/v1/me/device-tokens — My Device Tokens; Authenticated scope - POST /api/v1/me/device-token — Register this device for push notifications; Authenticated scope - DELETE /api/v1/me/device-token/:token — Stop this device receiving push (call on logout); Authenticated scope - GET /api/v1/me/notices — Notices; Authenticated scope - GET /api/v1/me/complaints — Complaints; Authenticated scope - POST /api/v1/me/complaints — Create Complaint; Authenticated scope - GET /api/v1/me/ptm — My Ptm; Authenticated scope - POST /api/v1/me/ptm/bookings — Book Ptm; Authenticated scope - POST /api/v1/me/ptm/bookings/:id/change — Change Ptm; Authenticated scope - POST /api/v1/me/ptm/follow-ups/:id — Ptm Task; Authenticated scope - GET /api/v1/me/live-classes — Live Classes List; Authenticated scope - GET /api/v1/me/lms/courses — Lms Courses; Authenticated scope - GET /api/v1/me/lms/courses/:id — Lms Course; Authenticated scope - PATCH /api/v1/me/lms/lessons/:id/progress — Lms Lesson Progress; Authenticated scope - GET /api/v1/me/assignments — Assignments List; Authenticated scope - POST /api/v1/me/assignments/:id/files — Upload Homework; Authenticated scope - GET /api/v1/me/assignment-files/:id — Homework File; Authenticated scope - POST /api/v1/me/assignments/:id/submit — Submit Assignment; Authenticated scope - GET /api/v1/me/department-team — Department Team; Authenticated scope - GET /api/v1/me/alumni-directory — Alumni Directory; Authenticated scope - POST /api/v1/me/ask-copilot — Ask Copilot; Authenticated scope - GET /api/v1/me/learning-path — Learning Path; Authenticated scope - POST /api/v1/me/learning-path — Regenerate Learning Path; Authenticated scope - PATCH /api/v1/me/learning-path-items/:itemId — Update Learning Path Item; Authenticated scope - GET /api/v1/me/explains — List Explains; Authenticated scope - GET /api/v1/me/explains/:id — Get Explain; Authenticated scope - POST /api/v1/me/explains — Generate Explain; Authenticated scope - GET /api/v1/me/transport — Transport; Authenticated scope - GET /api/v1/me/bus-eta — Bus Eta; Authenticated scope - GET /api/v1/me/adaptive-exams — Adaptive Exams List; Authenticated scope - POST /api/v1/me/adaptive-exams/:examId/start — Start Adaptive Exam; Authenticated scope - GET /api/v1/me/adaptive-attempts/:attemptId — Get Adaptive Attempt; Authenticated scope - POST /api/v1/me/adaptive-attempts/:attemptId/answer — Answer Adaptive; Authenticated scope - POST /api/v1/me/adaptive-attempts/:attemptId/submit — Submit Adaptive; Authenticated scope - GET /api/v1/me/progress-story — Progress Story; Authenticated scope - POST /api/v1/me/career-twin — Career Twin; Authenticated scope - POST /api/v1/me/alumni-opportunity — Alumni Opportunity; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Online payments & reconciliation Create gateway orders, verify callbacks and investigate payments that remain pending. Category: Finance Guide: https://avkul.in/docs/guides/module-payments/ Guided sample demo: https://avkul.in/docs/demo/module-payments/ Snapshot: 11 October 2026 ## Features - Payment orders - Callback verification - Pending payment review - Reconciliation - Gateway connection check ## Access and 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. Permission keys: fee:view, fee:manage, fee:create ## Workflow 1. Review the invoice and provider readiness. 2. Create an order through the permitted checkout workflow. 3. Verify the gateway response before treating the invoice as paid. 4. Investigate a pending payment through reconciliation. ## Fields and controls - abandon (boolean, optional) - reason (string, optional) - invoiceId (string, declared required) - amount (number, optional) - paymentId (string, declared required) - razorpayPaymentId (string, optional) - razorpaySignature (string, optional) ## Current limits - External collection requires approved gateway credentials and verified callbacks. The public guided demo does not charge money. ## Actual application access - https://avkul.in/en/school/payments ## API reference - POST /api/v1/webhooks/payments/razorpay — Razorpay; Public/capability access - GET /api/v1/payments/stuck — Payments left pending far longer than a checkout takes; fee:view - POST /api/v1/payments/:id/reconcile — Ask the gateway what happened, and settle the payment; fee:manage - GET /api/v1/payments/orders — List Orders; fee:view - GET /api/v1/payments/test-connection — Test Connection; fee:view - POST /api/v1/payments/orders — Create Order; fee:create - POST /api/v1/payments/verify — Verify Payment; fee:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notifications & integrations Review notifications, integration settings, webhook records and shared AI request state. Category: Administration Guide: https://avkul.in/docs/guides/module-platform/ Guided sample demo: https://avkul.in/docs/demo/module-platform/ Snapshot: 11 October 2026 ## Features - In-app notifications - Integration status - Integration configuration - Webhooks - AI requests ## Access and 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. Permission keys: dashboard:view, communication:create, settings:view, settings:create, settings:update, settings:delete ## Workflow 1. Open the relevant integration or notification view. 2. Review status and permitted settings. 3. Configure a provider using approved credentials outside public documentation. 4. Use a controlled test and inspect the actual result. ## Fields and controls - title (string, declared required) - body (string, optional) - userId (string, optional) - channel (string, optional) - dataJson (Record, optional) - feature (string, declared required) - provider (string, declared required) - model (string, optional) - promptJson (Record, optional) - responseJson (Record, optional) - promptTokens (number, optional) - completionTokens (number, optional) - status (string, optional) - errorMessage (string, optional) - prompt (string, declared required) - category (string, optional) - configJson (Record, optional) - secretsRef (string, optional) - isActive (boolean, optional) - integrationId (string, optional) - event (string, declared required) - targetUrl (string, declared required) - secret (string, optional) ## Current limits - Saving settings is not proof of external delivery. No credential values are included in this documentation. ## Actual application access - https://avkul.in/en/school/integrations ## API reference - GET /api/v1/notifications — List My Notifications; dashboard:view - POST /api/v1/notifications — Create Notification; communication:create - POST /api/v1/notifications/:id/read — Mark Read; dashboard:view - GET /api/v1/ai/requests — List Ai Requests; dashboard:view - POST /api/v1/ai/requests — Log Ai Request; dashboard:view - PATCH /api/v1/ai/requests/:id/complete — Complete Ai Request; dashboard:view - POST /api/v1/ai/generate — Generate Ai; dashboard:view - GET /api/v1/integrations/status — Integration Status; settings:view - GET /api/v1/integrations — List Integrations; settings:view - POST /api/v1/integrations — Create Integration; settings:create - PATCH /api/v1/integrations/:id — Update Integration; settings:update - DELETE /api/v1/integrations/:id — Remove Integration; settings:delete - GET /api/v1/webhooks — List Webhooks; settings:view - POST /api/v1/webhooks — Create Webhook; settings:create - PATCH /api/v1/webhooks/:id — Update Webhook; settings:update - POST /api/v1/webhooks/:id/test — Test Webhook; settings:update - DELETE /api/v1/webhooks/:id — Remove Webhook; settings:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Year-end rollover Preview new-session student placement and apply or revert a recorded promotion batch. Category: School office Guide: https://avkul.in/docs/guides/module-promotion/ Guided sample demo: https://avkul.in/docs/demo/module-promotion/ Snapshot: 11 October 2026 ## Features - Rollover preview - Structure clone - Promotion commit - Batch history - Revert - Enrollment history ## Access and 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. Permission keys: promotion:view, promotion:create, promotion:manage, promotion:delete, student:view ## Workflow 1. Choose the source and target academic sessions. 2. Clone or prepare the target class structure. 3. Review the dry-run placement and exceptions. 4. Commit only the reviewed batch and keep its reversal reference. ## Fields and controls - fromSessionId (string, declared required) - toSessionId (string, declared required) - criteria (PromotionCriteriaDto, optional) - includeTimetables (boolean, optional) - decisions (StudentDecisionDto[], declared required) - activateTargetSession (boolean, optional) - notes (string, optional) - graduationYear (number, optional) ## Current limits - Preview writes nothing; commit changes enrollment. Locked sessions and school ownership checks still apply. ## Actual application access - https://avkul.in/en/school/promotion ## API reference - POST /api/v1/promotions/preview — Dry-run a rollover — writes nothing; promotion:view - POST /api/v1/promotions/clone-structure — Copy classes/sections/subjects into the new session; promotion:create - POST /api/v1/promotions/commit — Apply the rollover (transactional); promotion:manage - POST /api/v1/promotions/batches/:id/revert — Revert; promotion:delete - GET /api/v1/promotions/batches — Batches; promotion:view - GET /api/v1/promotions/enrollments — Per-session placement history for a student; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Parent–teacher meetings Publish meeting slots, book families, record discussion outcomes and manage follow-up tasks. Category: Community Guide: https://avkul.in/docs/guides/module-ptm/ Guided sample demo: https://avkul.in/docs/demo/module-ptm/ Snapshot: 11 October 2026 ## Features - Teacher slots - Family bookings - Reschedule and cancel - Meeting notes - Family-visible follow-ups - In-app reminders ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Teacher - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. Permission keys: communication:view, communication:create, communication:delete, communication:update ## Workflow 1. Create or choose the permitted teacher meeting slot. 2. Book the linked child and verify availability. 3. Record the meeting outcome with the correct note visibility. 4. Assign and complete any follow-up action. ## Fields and controls - id (string, optional) - staffId (string, declared required) - date (string, declared required) - startTime (string, declared required) - endTime (string, declared required) - capacity (number, optional) - location (string, optional) - isActive (boolean, optional) - version (string, optional) - slotId (string, declared required) - studentId (string, declared required) - notes (string, optional) - status (string, declared required) - reason (string, optional) - privateNotes (string, optional) - feedback (string, optional) - bookingId (string, declared required) - title (string, declared required) - owner ("SCHOOL" | "FAMILY", declared required) - dueDate (string, optional) - force (boolean, optional) - parentId (string, optional) ## Current limits - Private staff notes and family-visible notes differ. Reminder actions do not guarantee external SMS, email or push delivery. ## Actual application access - https://avkul.in/en/school/ptm ## API reference - GET /api/v1/ptm/workspace — Read; communication:view - POST /api/v1/ptm/workspace/slots — Slot; communication:create - POST /api/v1/ptm/workspace/slots/:id/delete — Remove; communication:delete - POST /api/v1/ptm/workspace/bookings — Book; communication:create - POST /api/v1/ptm/workspace/bookings/:id/change — Change; communication:update - POST /api/v1/ptm/workspace/bookings/:id/notes — Notes; communication:update - POST /api/v1/ptm/workspace/follow-ups — Task; communication:update - POST /api/v1/ptm/workspace/remind — Remind; communication:create - GET /api/v1/ptm/slots — List Slots; communication:view - POST /api/v1/ptm/slots — Create Slot; communication:create - PATCH /api/v1/ptm/slots/:id — Update Slot; communication:update - DELETE /api/v1/ptm/slots/:id — Remove Slot; communication:delete - GET /api/v1/ptm/bookings — List Bookings; communication:view - POST /api/v1/ptm/bookings — Create Booking; communication:create - PATCH /api/v1/ptm/bookings/:id/status — Update Booking Status; communication:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School reports Review fee summaries, student distribution and examination summaries from permitted school data. Category: Finance Guide: https://avkul.in/docs/guides/module-report/ Guided sample demo: https://avkul.in/docs/demo/module-report/ Snapshot: 11 October 2026 ## Features - Fee summary - Students by class - Exam summary ## Access and 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. Permission keys: report:view ## Workflow 1. Choose the report and reporting context. 2. Inspect the totals and available filters. 3. Compare the summary with the underlying records. 4. Use the available export or print action when present. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - A summary is only as current as the entered records. Each report uses its implemented date and scope rules. ## Actual application access - https://avkul.in/en/school/reports ## API reference - GET /api/v1/reports/exam-summary — Exam Summary; report:view - GET /api/v1/reports/fee-summary — Fee Summary; report:view - GET /api/v1/reports/students-by-class — Students By Class; report:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform administration Manage tenants, schools, plans, subscriptions, billing and cross-tenant reporting. Category: Platform Guide: https://avkul.in/docs/guides/module-saas/ Guided sample demo: https://avkul.in/docs/demo/module-saas/ Snapshot: 11 October 2026 ## Features - Tenant onboarding - Schools and quotas - Plans and module toggles - Subscriptions - Invoices and coupons - Analytics and reports - Usage - Audit and support ## Access and setup Intended access: Platform administrator - A platform administrator account. - The academic, student or staff setup used by this workflow. ## Workflow 1. Select the tenant or platform overview. 2. Review plan, subscription, usage and school details. 3. Apply an authorized administrative action. 4. Review the resulting invoice, audit or report. ## Fields and controls - code (string, declared required) - description (string, optional) - type (string, optional) - value (number, declared required) - maxRedemptions (number, optional) - validFrom (string, optional) - validUntil (string, optional) - isActive (boolean, optional) - question (string, declared required) - planCode (string, optional) - amount (number, optional) - paymentLogId (string, declared required) - razorpayPaymentId (string, optional) - razorpaySignature (string, optional) - name (string, declared required) - billingCycle (string, optional) - priceMonthly (number, optional) - priceYearly (number, optional) - trialDays (number, optional) - maxStudents (number, optional) - maxStaff (number, optional) - maxSchools (number, optional) - maxBranches (number, optional) - isPublic (boolean, optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/ai-center - https://avkul.in/en/saas/analytics - https://avkul.in/en/saas/audit-log - https://avkul.in/en/saas/command-center - https://avkul.in/en/saas/coupons - https://avkul.in/en/saas/invoices - https://avkul.in/en/saas/invoices — select the actual record from this list. - https://avkul.in/en/saas - https://avkul.in/en/saas/plans - https://avkul.in/en/saas/reports - https://avkul.in/en/saas/subscriptions - https://avkul.in/en/saas/tenants - https://avkul.in/en/saas/tenants — select the actual record from this list. - https://avkul.in/en/saas/usage - https://avkul.in/en/school/plan ## API reference - GET /api/v1/saas/coupons — List discount codes with their redemption counts; Platform admin - POST /api/v1/saas/coupons — Issue a discount code; Platform admin - PATCH /api/v1/saas/coupons/:id — Change a code’s window, cap or active flag; Platform admin - GET /api/v1/saas/coupons/preview/:code — What a code would do to an invoice, without spending it; Platform admin - POST /api/v1/saas/coupons/invoices/:invoiceId/apply — Apply a code to an invoice and spend one redemption; Platform admin - DELETE /api/v1/saas/coupons/invoices/:invoiceId — Take the code back off an invoice; Platform admin - POST /api/v1/saas/ai-center/ask — Ask a plain-English question about the platform — answered from real, computed aggregates; Platform admin - GET /api/v1/saas/analytics — Cross-tenant growth/revenue/churn analytics with an AI-generated narrative summary; Platform admin - GET /api/v1/saas/audit-log — Platform activity trail — every superadmin action across every tenant; Platform admin - GET /api/v1/saas/subscriptions — List subscriptions across all tenants; Platform admin - PATCH /api/v1/saas/subscriptions/:id/plan — Upgrade/downgrade a tenant subscription; Platform admin - GET /api/v1/saas/invoices — List SaaS invoices; Platform admin - GET /api/v1/saas/invoices/:id — Invoice; Platform admin - POST /api/v1/saas/invoices/:id/payment-order — Create a Razorpay order to collect payment against an invoice; Platform admin - POST /api/v1/saas/payments/verify — Verify a Razorpay payment callback and mark the invoice paid; Platform admin - GET /api/v1/saas/payments/test-connection — Check whether configured Razorpay credentials actually authenticate; Platform admin - GET /api/v1/saas/overview — Platform KPIs (tenants, footprint, MRR/ARR, billing); Platform admin - GET /api/v1/saas/modules — List all toggleable platform modules; Platform admin - GET /api/v1/saas/plans — List subscription plans with their modules; Platform admin - GET /api/v1/saas/plans/:id — Get One; Platform admin - POST /api/v1/saas/plans — Create a plan (with module toggles); Platform admin - PATCH /api/v1/saas/plans/:id — Update; Platform admin - DELETE /api/v1/saas/plans/:id — Soft-delete (archive) a plan; Platform admin - GET /api/v1/saas/reports/:type — Cross-tenant report (revenue/usage/churn/activity) as JSON, CSV, or PDF; Platform admin - GET /api/v1/saas/tenants — List tenants (search, status filter, paginated); Platform admin - GET /api/v1/saas/tenants/:id — Tenant detail with schools, subscription and counts; Platform admin - POST /api/v1/saas/tenants — Onboard a new tenant/school (provisions admin + plan); Platform admin - POST /api/v1/saas/tenants/:id/schools — Add a school to an existing tenant (counts against the plan); Platform admin - POST /api/v1/saas/tenants/ai-provision — AI Command Center — provision a full tenant from just school/owner facts and email the owner their access; Platform admin - PATCH /api/v1/saas/tenants/:id/status — Activate / suspend / cancel a tenant; Platform admin - POST /api/v1/saas/tenants/bulk-action — Apply activate/suspend/cancel to multiple tenants at once; Platform admin - GET /api/v1/saas/tenants/health/scores — Composite health score per tenant (status, overdue invoices, login recency, trial runway); Platform admin - PATCH /api/v1/saas/tenants/:id/branding — Update white-label branding (brand name, color, custom domain); Platform admin - POST /api/v1/saas/tenants/:id/logo — Upload the tenant logo; Platform admin - POST /api/v1/saas/tenants/:id/favicon — Upload the tenant favicon; Platform admin - POST /api/v1/saas/tenants/:id/domain — Claim a custom domain — returns a DNS TXT record to publish for ownership proof; Platform admin - DELETE /api/v1/saas/tenants/:id/domain — Remove the custom domain and reset verification; Platform admin - POST /api/v1/saas/tenants/:id/domain/verify — Verify domain ownership via a real DNS TXT lookup; Platform admin - GET /api/v1/saas/usage — Every tenant against its plan limits; Platform admin - GET /api/v1/saas/usage/:tenantId — Status; Platform admin - GET /api/v1/saas/usage/:tenantId/counters — Counters; Platform admin - POST /api/v1/saas/usage/:tenantId/refresh — Recount usage and write this period's counters; Platform admin - GET /api/v1/my-plan/usage — This tenant's usage against its own plan; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School dashboard & branches See school-wide priorities and manage the campus context used by the ERP. Category: School office Guide: https://avkul.in/docs/guides/module-school/ Guided sample demo: https://avkul.in/docs/demo/module-school/ Snapshot: 11 October 2026 ## Features - Overview metrics - Daily Action Center - School profile - Branch counts - Campus creation and update ## Access and 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. Permission keys: dashboard:view, settings:create, settings:update, settings:delete ## Workflow 1. Review the school dashboard and current session. 2. Open an outstanding action in the relevant module. 3. Inspect the campus counts and permitted branch settings. 4. Review the consequences before closing a campus. ## Fields and controls - code (string, declared required) - name (string, declared required) - addressLine1 (string, optional) - city (string, optional) - phone (string, optional) - isMain (boolean, optional) ## Current limits - Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow. ## Actual application access - https://avkul.in/en/school/branches - https://avkul.in/en/school ## API reference - GET /api/v1/school/overview — School Admin dashboard KPIs (today + footprint); dashboard:view - GET /api/v1/school/action-center — Daily Action Center: everything pending today, scoped to the caller; dashboard:view - GET /api/v1/school/profile — Current school, branches and active session; dashboard:view - GET /api/v1/school/staff — Staff directory (id + name) for dropdowns; dashboard:view - GET /api/v1/school/branches/stats — Per-branch student/staff counts and fee collection; dashboard:view - POST /api/v1/school/branches — Open another campus (counts against the plan); settings:create - PATCH /api/v1/school/branches/:id — Rename a campus, or make it the main one; settings:update - DELETE /api/v1/school/branches/:id — Close a campus (refused while anyone is posted to it); settings:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff directory & lifecycle Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement. Category: People Guide: https://avkul.in/docs/guides/module-staff/ Guided sample demo: https://avkul.in/docs/demo/module-staff/ Snapshot: 11 October 2026 ## Features - Directory - Staff creation - Profile 360 - Clearance - Offboarding - Reinstatement ## Access and 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. Permission keys: hr:view, hr:create, hr:update, hr:manage ## Workflow 1. Find or create the staff profile. 2. Review employment details and linked responsibilities. 3. Inspect clearance before offboarding. 4. Use reinstatement when returning a former staff member. ## Fields and controls - employeeCode (string, declared required) - firstName (string, declared required) - lastName (string, optional) - gender (string, optional) - dateOfBirth (string, optional) - email (string, optional) - phone (string, optional) - branchId (string, optional) - departmentId (string, optional) - designationId (string, optional) - reportsToId (string, optional) - joiningDate (string, optional) - contractType (string, optional) - qualifications (unknown, optional) - exitStatus ('RESIGNED' | 'TERMINATED' | 'RETIRED', optional) - exitDate (string, optional) - reason (string, optional) - force (boolean, optional) ## Current limits - Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action. ## Actual application access - https://avkul.in/en/school/staff - https://avkul.in/en/school/staff — select the actual record from this list. ## API reference - GET /api/v1/staff — List; hr:view - GET /api/v1/staff/former — List Former; hr:view - POST /api/v1/staff — Add a staff member; hr:create - PATCH /api/v1/staff/:id — Update; hr:update - GET /api/v1/staff/:id/clearance — What still depends on this person; hr:view - POST /api/v1/staff/:id/offboard — Mark a staff member as having left; hr:manage - POST /api/v1/staff/:id/reinstate — Reinstate; hr:manage - GET /api/v1/staff/:id — Get; hr:view - GET /api/v1/staff/:id/profile-360 — Get Profile360; hr:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff attendance Record staff check-in/out and maintain an administrative daily and monthly register. Category: People Guide: https://avkul.in/docs/guides/module-staff-attendance/ Guided sample demo: https://avkul.in/docs/demo/module-staff-attendance/ Snapshot: 11 October 2026 ## Features - Own attendance - Check-in/out - Daily roster - Corrections - Monthly register - Holiday marking ## Access and 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. Permission keys: hr:view, hr:update, hr:manage ## Workflow 1. Check the current personal attendance state. 2. Clock in or out through the self-service action. 3. Use the authorized daily roster to correct records. 4. Review the monthly register and holiday policy. ## Fields and controls - lat (number, optional) - lng (number, optional) - remark (string, optional) - date (string, declared required) - records (StaffAttendanceInput[], declared required) - force (boolean, optional) - from (string, declared required) - to (string, declared required) ## Current limits - Self-service acts on the caller’s staff profile. Administrative corrections need separate access. ## Actual application access - https://avkul.in/en/school/staff-attendance ## API reference - GET /api/v1/staff-attendance/me — The caller's own attendance history and check-in state; Authenticated scope - POST /api/v1/staff-attendance/me/check-in — Clock in for today; Authenticated scope - POST /api/v1/staff-attendance/me/check-out — Clock out for today; Authenticated scope - GET /api/v1/staff-attendance/roster — All staff with their status for a date; hr:view - POST /api/v1/staff-attendance/mark — Mark/correct staff attendance for a date; hr:update - GET /api/v1/staff-attendance/register — Monthly staff attendance register; hr:view - POST /api/v1/staff-attendance/mark-holidays — Stamp HOLIDAY rows for staff-applicable closed days; hr:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student records & lifecycle Maintain student profiles, guardians and documents, and manage campus release or school exit. Category: School office Guide: https://avkul.in/docs/guides/module-student/ Guided sample demo: https://avkul.in/docs/demo/module-student/ Snapshot: 11 October 2026 ## Features - Student directory - Profile 360 - Guardians - Document review - Gate passes - Exit clearance - Transfer certificates - Readmission ## Access and 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. Permission keys: student:view, student:update, student:manage, student:delete, student:create, student-exit:view, student-exit:create, student-exit:manage ## Workflow 1. Create or open the student profile. 2. Review guardian contacts and required documents. 3. Use the gate-pass workflow for an authorized early release. 4. Use clearance and exit workflows for withdrawal or transfer. ## Fields and controls - studentId (string, declared required) - reason (string, optional) - expectedOutAt (string, optional) - expectedBackAt (string, optional) - releaseToName (string, optional) - releaseToGuardianId (string, optional) - approve (boolean, declared required) - guardianId (string, optional) - releaseRelation (string, optional) - overrideReason (string, optional) - notes (string, optional) - type (string, declared required) - title (string, optional) - expiresAt (string, optional) - firstName (string, declared required) - middleName (string, optional) - lastName (string, optional) - admissionNo (string, declared required) - rollNo (string, optional) - gender (string, optional) - dateOfBirth (string, optional) - bloodGroup (string, optional) - sessionId (string, optional) - classId (string, optional) ## Current limits - Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record. ## Actual application access - https://avkul.in/en/school/gate-pass - https://avkul.in/en/school/student-exit - https://avkul.in/en/school/students - https://avkul.in/en/school/students — select the actual record from this list. ## API reference - GET /api/v1/gate-pass — List; student:view - GET /api/v1/gate-pass/currently-out — Students currently signed out of campus; student:view - GET /api/v1/gate-pass/student/:studentId/pickups — Who is on file to collect this student; student:view - POST /api/v1/gate-pass — Create; student:update - POST /api/v1/gate-pass/:id/decision — Approve or turn down a gate pass; student:manage - POST /api/v1/gate-pass/:id/release — Hand the student over at the gate; student:update - POST /api/v1/gate-pass/:id/return — Mark Returned; student:update - POST /api/v1/gate-pass/:id/cancel — Cancel; student:update - GET /api/v1/student-documents/expiring — Documents that have expired or are about to; student:view - GET /api/v1/student-documents/missing — Students with incomplete or unverified paperwork; student:view - GET /api/v1/student-documents/:studentId — List; student:view - POST /api/v1/student-documents/:studentId — Upload a document for a student; student:update - POST /api/v1/student-documents/verify/:id — Mark a document as checked against the original; student:manage - POST /api/v1/student-documents/reject/:id — Send a document back with a reason; student:manage - DELETE /api/v1/student-documents/:id — Remove; student:delete - GET /api/v1/students — List; student:view - GET /api/v1/students/:id — Get; student:view - GET /api/v1/students/:id/profile-360 — Get Profile360; student:view - POST /api/v1/students — Create; student:create - PATCH /api/v1/students/:id — Update; student:update - DELETE /api/v1/students/:id — Remove; student:delete - GET /api/v1/students/exit/register — Students who have left, with TC numbers; student-exit:view - GET /api/v1/students/:id/clearance — What is blocking this student from leaving; student-exit:view - POST /api/v1/students/:id/exit — Take a student off the rolls and allocate a TC number; student-exit:create - POST /api/v1/students/:id/readmit — Reverse an exit and put the student back on the rolls; student-exit:manage - POST /api/v1/students/:id/transfer-certificate — Generate the TC document for an exited student; student-exit:create - POST /api/v1/students/:id/guardians — Add Guardian; student:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tally export Prepare accounting vouchers for the configured Tally integration. Category: Finance Guide: https://avkul.in/docs/guides/module-tally/ Guided sample demo: https://avkul.in/docs/demo/module-tally/ Snapshot: 11 October 2026 ## Features - Connection test - Voucher export ## Access and 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. Permission keys: settings:view, fee:export ## Workflow 1. Review the accounting data and integration settings. 2. Check the configured connection in a controlled environment. 3. Export the selected voucher records. 4. Reconcile the receiving system with the exported result. ## Fields and controls - fromDate (string, declared required) - toDate (string, declared required) - pushToTally (boolean, optional) ## Current limits - An export endpoint does not prove that a live Tally instance is connected or that vouchers were imported successfully. ## Actual application access - https://avkul.in/en/school/tally ## API reference - GET /api/v1/tally/test-connection — Test Connection; settings:view - POST /api/v1/tally/export-vouchers — Export Vouchers; fee:export ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff tasks Assign work to school staff and let each user complete their own task list. Category: People Guide: https://avkul.in/docs/guides/module-task/ Guided sample demo: https://avkul.in/docs/demo/module-task/ Snapshot: 11 October 2026 ## Features - Administrative task list - Create and edit - My tasks - Completion ## Access and 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. Permission keys: hr:view, hr:create, hr:update, hr:delete ## Workflow 1. Create a task with the intended staff assignment. 2. Review its due date and current state. 3. The assigned user opens their own task queue. 4. Complete the task and review the updated record. ## Fields and controls - title (string, optional) - description (string, optional) - assignedToId (string, optional) - dueDate (string, optional) - priority (string, optional) - category (string, optional) - checklist (ChecklistItemDto[], optional) - status (string, optional) ## Current limits - School staff tasks are separate from the platform marketing Demo & Follow-up Workspace. ## Actual application access - https://avkul.in/en/school/tasks ## API reference - GET /api/v1/tasks/mine — Self-service: my own open tasks; Authenticated scope - POST /api/v1/tasks/mine/:id/complete — Self-service: mark my own task done; Authenticated scope - GET /api/v1/tasks — List; hr:view - POST /api/v1/tasks — Create; hr:create - PATCH /api/v1/tasks/:id — Update; hr:update - DELETE /api/v1/tasks/:id — Remove; hr:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Timetable & teacher cover Build recurring class schedules and arrange dated teacher cover with clash checks. Category: Academics Guide: https://avkul.in/docs/guides/module-timetable/ Guided sample demo: https://avkul.in/docs/demo/module-timetable/ Snapshot: 11 October 2026 ## Features - Weekly and daily views - Class and teacher filters - Periods and rooms - Time-overlap checks - Dated cover - Availability review - History and print ## Access and 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. Permission keys: timetable:view, timetable:create, timetable:delete, timetable:update ## Workflow 1. Select the section, teacher and date. 2. Create a period with its subject, time and room. 3. Resolve overlap warnings before saving. 4. Arrange dated cover and review the daily plan. ## Fields and controls - version (string, optional) - periodId (string, declared required) - date (string, declared required) - substituteStaffId (string, declared required) - reason (string, optional) - status ('PLANNED' | 'CONFIRMED' | 'CANCELLED', declared required) - sectionId (string, declared required) - dayOfWeek (number, declared required) - periodNo (number, declared required) - startTime (string, declared required) - endTime (string, declared required) - subjectId (string, optional) - teacherStaffId (string, optional) - roomNo (string, optional) - periodType (string, optional) - force (boolean, optional) - absentStaffId (string, declared required) - apply (boolean, optional) - autoGenerated (boolean, optional) ## Current limits - Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view. ## Actual application access - https://avkul.in/en/school/substitutions - https://avkul.in/en/school/timetable ## API reference - GET /api/v1/timetable/workspace — Read; timetable:view - POST /api/v1/timetable/workspace/periods — Save; timetable:create - POST /api/v1/timetable/workspace/periods/:id/delete — Remove; timetable:delete - POST /api/v1/timetable/workspace/covers — Cover; timetable:create - GET /api/v1/timetable/my — The caller’s own week — periods they teach, or their section’s; Authenticated scope - GET /api/v1/timetable — Grid; timetable:view - POST /api/v1/timetable/periods — Upsert Period; timetable:create - DELETE /api/v1/timetable/periods/:id — Remove Period; timetable:delete - GET /api/v1/timetable/clashes — Audit saved timetables for teacher/room/overlap clashes; timetable:view - GET /api/v1/timetable/day-plan — A day's timetable with substitutions applied; timetable:view - GET /api/v1/timetable/substitutions — List Substitutions; timetable:view - POST /api/v1/timetable/substitutions/suggest — Who could cover an absent teacher (suggestions only); timetable:view - POST /api/v1/timetable/substitutions/generate — Record cover for all of an absent teacher's periods on a date; timetable:create - POST /api/v1/timetable/substitutions — Assign one substitute to one period on one date; timetable:create - PATCH /api/v1/timetable/substitutions/:id/status — Set Substitution Status; timetable:update - DELETE /api/v1/timetable/substitutions/:id — Remove Substitution; timetable:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Transport operations Manage buses, routes, stops and student allocations, then run daily boarding registers. Category: Campus Guide: https://avkul.in/docs/guides/module-transport/ Guided sample demo: https://avkul.in/docs/demo/module-transport/ Snapshot: 11 October 2026 ## Features - Fleet and capacity - Routes and stops - Pickup/drop allocations - Trip start and completion - Boarding corrections - Family bus view - Fuel and recorded locations ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Transport Manager, Driver - An assigned school account with the required permissions. - The academic, student or staff setup used by this workflow. Permission keys: transport:view, transport:create, transport:delete, transport:update ## Workflow 1. Set up the bus, route and ordered stops. 2. Allocate students within the directional seat capacity. 3. Start today’s trip and record boarding/drop-off. 4. Complete the run and review family-visible updates. ## Fields and controls - regNo (string, declared required) - model (string, optional) - capacity (number, optional) - driverStaffId (string, optional) - helperStaffId (string, optional) - isActive (boolean, optional) - name (string, declared required) - vehicleId (string, declared required) - routeId (string, declared required) - sequence (number, optional) - pickupTime (string, optional) - dropTime (string, optional) - studentId (string, declared required) - stopId (string, optional) - direction (string, optional) - id (string, optional) - version (string, optional) - date (string, declared required) - status (string, declared required) - note (string, optional) - reason (string, optional) - notes (string, optional) - marks (BoardingMarkDto[], declared required) - force (boolean, optional) ## Current limits - Drivers see only their assigned operations. Recorded GPS points are not proof of an active device feed; no live tracking hardware is provisioned here. ## Actual application access - https://avkul.in/en/school/transport ## API reference - GET /api/v1/transport/workspace — Read; transport:view - POST /api/v1/transport/workspace/vehicles — Vehicle; transport:create - POST /api/v1/transport/workspace/routes — Route; transport:create - POST /api/v1/transport/workspace/stops — Stop; transport:create - POST /api/v1/transport/workspace/assignments — Assignment; transport:create - POST /api/v1/transport/workspace/:kind/:id/delete — Remove; transport:delete - POST /api/v1/transport/workspace/trips/start — Start; transport:update - POST /api/v1/transport/workspace/trips/:id/mark — Mark; transport:update - POST /api/v1/transport/workspace/trips/:id/end — End; transport:update - POST /api/v1/transport/workspace/trips/:id/notify — Notify; transport:update - GET /api/v1/transport/trips — List Trips; transport:view - GET /api/v1/transport/trips/:id/manifest — Manifest; transport:view - POST /api/v1/transport/trips/start — Start Trip; transport:update - POST /api/v1/transport/trips/:id/mark — Mark Boarding; transport:update - POST /api/v1/transport/trips/:id/end — End Trip; transport:update - POST /api/v1/transport/trips/:id/notify — Notify Families; transport:update - GET /api/v1/transport/vehicles — List Vehicles; transport:view - POST /api/v1/transport/vehicles — Create Vehicle; transport:create - PATCH /api/v1/transport/vehicles/:id — Update Vehicle; transport:update - DELETE /api/v1/transport/vehicles/:id — Remove Vehicle; transport:delete - GET /api/v1/transport/routes — List Routes; transport:view - POST /api/v1/transport/routes — Create Route; transport:create - PATCH /api/v1/transport/routes/:id — Update Route; transport:update - DELETE /api/v1/transport/routes/:id — Remove Route; transport:delete - POST /api/v1/transport/routes/:id/optimize — Optimize Route; transport:update - GET /api/v1/transport/stops — List Stops; transport:view - POST /api/v1/transport/stops — Create Stop; transport:create - PATCH /api/v1/transport/stops/:id — Update Stop; transport:update - DELETE /api/v1/transport/stops/:id — Remove Stop; transport:delete - GET /api/v1/transport/assignments — List Assignments; transport:view - POST /api/v1/transport/assignments — Create Assignment; transport:create - PATCH /api/v1/transport/assignments/:id — Update Assignment; transport:update - DELETE /api/v1/transport/assignments/:id — Remove Assignment; transport:delete - GET /api/v1/transport/fuel-logs — List Fuel Logs; transport:view - POST /api/v1/transport/fuel-logs — Create Fuel Log; transport:create - PATCH /api/v1/transport/fuel-logs/:id — Update Fuel Log; transport:update - DELETE /api/v1/transport/fuel-logs/:id — Remove Fuel Log; transport:delete - POST /api/v1/transport/vehicles/:id/location — Record Location; transport:update - GET /api/v1/transport/vehicles/:id/location/latest — Latest Location; transport:view - GET /api/v1/transport/vehicles/:id/location/history — Location History; transport:view - GET /api/v1/transport/fleet/locations — Fleet Locations; transport:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tuition batches & demos Manage tuition subjects, teaching batches, student enrollment and prospective demo classes. Category: Institutions Guide: https://avkul.in/docs/guides/module-tuition/ Guided sample demo: https://avkul.in/docs/demo/module-tuition/ Snapshot: 11 October 2026 ## Features - Subjects - Batches - Enrollment - Prospect demos - Progress reports ## Access and 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. Permission keys: student:view, student:create, student:update, student:delete ## Workflow 1. Create the subject and teaching batch. 2. Enroll the eligible student with the applicable terms. 3. Schedule and review prospective demo classes. 4. Maintain progress reports and enrollment state. ## Fields and controls - name (string, optional) - subjectId (string, declared required) - teacherStaffId (string, optional) - type (BatchType, optional) - startDate (string, declared required) - endDate (string, optional) - maxStudents (number, optional) - monthlyFee (number, optional) - schedule (string, optional) - roomNo (string, optional) - status (DemoStatus, optional) - batchId (string, declared required) - studentId (string, declared required) - enrolledAt (string, optional) - discountAmount (number, optional) - notes (string, optional) - isActive (boolean, optional) - prospectName (string, declared required) - prospectPhone (string, declared required) - prospectEmail (string, optional) - scheduledAt (string, optional) - feedbackNotes (string, optional) - converted (boolean, optional) - convertedStudentId (string, optional) ## Current limits - Tuition prospect demos are distinct from the platform’s AVKUL ERP product demos. ## Actual application access - https://avkul.in/en/school/tuition ## API reference - GET /api/v1/tuition/stats — Tuition center overview stats; student:view - GET /api/v1/tuition/subjects — List subjects available for batches; student:view - GET /api/v1/tuition/students — List students (for enrollment); student:view - GET /api/v1/tuition/batches — List all batches; student:view - POST /api/v1/tuition/batches — Create a new batch; student:create - PATCH /api/v1/tuition/batches/:id — Update a batch; student:update - DELETE /api/v1/tuition/batches/:id — Delete a batch; student:delete - GET /api/v1/tuition/enrollments — List enrollments (optionally filter by batchId); student:view - POST /api/v1/tuition/enrollments — Enroll a student in a batch; student:create - PATCH /api/v1/tuition/enrollments/:id — Update enrollment (activate/deactivate, discount); student:update - GET /api/v1/tuition/demos — List demo classes (filter by status); student:view - POST /api/v1/tuition/demos — Schedule a demo class for a prospect; student:create - PATCH /api/v1/tuition/demos/:id — Update demo class (status, feedback, conversion); student:update - GET /api/v1/tuition/progress-reports — List progress reports; student:view - POST /api/v1/tuition/progress-reports — Create a progress report; student:create - PATCH /api/v1/tuition/progress-reports/:id — Update a progress report; student:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website CMS Manage school themes, content pages and published website information from the ERP. Category: Websites Guide: https://avkul.in/docs/guides/module-website/ Guided sample demo: https://avkul.in/docs/demo/module-website/ Snapshot: 11 October 2026 ## Features - Themes - Theme activation - Page content - Draft and publish - Public school pages - Branding and contact ## Access and 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. Permission keys: website:view, website:create, website:update, website:delete ## Workflow 1. Review the school website theme and branding. 2. Create or edit the intended content page. 3. Preview and check the content and contact information. 4. Publish the page and review the public school URL. ## Fields and controls - name (string, declared required) - configJson (Record, optional) - isActive (boolean, optional) - slug (string, declared required) - title (string, declared required) - type (string, optional) - themeId (string, optional) - contentJson (Record, optional) - seoJson (Record, optional) - sortOrder (number, optional) - status (string, declared required) ## Current limits - School website content is separate from the platform marketing Landing Page CMS. Publish controls use school ownership and permissions. ## Actual application access - https://avkul.in/en/school/website ## API reference - GET /api/v1/website/themes — List Themes; website:view - POST /api/v1/website/themes — Create Theme; website:create - PATCH /api/v1/website/themes/:id — Update Theme; website:update - POST /api/v1/website/themes/:id/activate — Activate Theme; website:update - DELETE /api/v1/website/themes/:id — Remove Theme; website:delete - GET /api/v1/website/pages — List Pages; website:view - POST /api/v1/website/pages — Create Page; website:create - PATCH /api/v1/website/pages/:id — Update Page; website:update - POST /api/v1/website/pages/:id/publish — Publish Page; website:update - DELETE /api/v1/website/pages/:id — Remove Page; website:delete - GET /api/v1/website/public/:schoolCode — Get Public Site; Public/capability access - GET /api/v1/website/public/:schoolCode/:slug — Get Public Page; Public/capability access ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Approval workflows Configure approval chains and let the responsible approver act on the current step. Category: People Guide: https://avkul.in/docs/guides/module-workflow/ Guided sample demo: https://avkul.in/docs/demo/module-workflow/ Snapshot: 11 October 2026 ## Features - Workflow definitions - Approval steps - Pending for me - Instance detail - Approve/reject ## Access and 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. Permission keys: settings:view, settings:create, settings:update, settings:delete ## Workflow 1. Create a workflow definition and its ordered steps. 2. Review the workflow linked to the business record. 3. The current approver opens their pending queue. 4. Record the decision and inspect the next step. ## Fields and controls - decision ('APPROVED' | 'REJECTED', declared required) - remark (string, optional) - name (string, optional) - entityType (string, declared required) - description (string, optional) - steps (WorkflowStepDto[], optional) - isActive (boolean, optional) ## Current limits - Approval is limited to the current eligible approver; it is separate from directly editing the source business record. ## Actual application access - https://avkul.in/en/school/workflows ## API reference - GET /api/v1/workflows/pending-for-me — Approvals waiting on me right now; Authenticated scope - POST /api/v1/workflows/instances/:id/decide — Approve or reject my current step; Authenticated scope - GET /api/v1/workflows/instances/:id — Get Instance; settings:view - GET /api/v1/workflows/for-entity — Approval chains attached to one record; settings:view - GET /api/v1/workflows — List; settings:view - POST /api/v1/workflows — Create; settings:create - PATCH /api/v1/workflows/:id — Update; settings:update - DELETE /api/v1/workflows/:id — Remove; settings:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Ask School Copilot Ask a school-related question within the signed-in family’s permitted context. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-ask/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-ask/ Snapshot: 11 October 2026 ## Features - Question input - Answer review - Provider-dependent assistance ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the linked child. 2. Enter a school-related question. 3. Review the answer and verify important details with the school. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/ask ## API reference - GET /api/v1/me/children — Children; Authenticated scope - POST /api/v1/me/ask-copilot — Ask Copilot; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My attendance Review daily and calendar attendance for the selected learner. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-attendance/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-attendance/ Snapshot: 11 October 2026 ## Features - Child selector - Attendance calendar - Summary and counting policy ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked child. 2. Inspect the attendance period and status. 3. Review the counting explanation and query the school about corrections. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/attendance ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My child’s bus View assigned routes, stops, schedules and recorded trip status for your child. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-bus/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-bus/ Snapshot: 11 October 2026 ## Features - Assigned bus and route - Pickup/drop stop - Today’s boarding status - Trip history ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select your child. 2. Review the bus, route and stop schedule. 3. Check the recorded trip status and latest available history. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/bus ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Family complaints Submit a school complaint and review the visible responses or status. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-complaints/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-complaints/ Snapshot: 11 October 2026 ## Features - Complaint list - New complaint - Status review ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Review your existing complaints. 2. Enter the subject and relevant details. 3. Submit and review the recorded status. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/complaints ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/complaints — Complaints; Authenticated scope - POST /api/v1/me/complaints — Create Complaint; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Online exam attempts Open an eligible adaptive exam, answer questions and submit the learner’s attempt. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-exams/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-exams/ Snapshot: 11 October 2026 ## Features - Available exams - Start attempt - Answer selection - Submit attempt - Attempt result ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select an available exam for the learner. 2. Start the attempt and answer the questions. 3. Review answers before submitting. 4. Inspect the available completion result. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/exams ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/adaptive-attempts/:attemptId — Get Adaptive Attempt; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Learning explanations Request and review a topic explanation in the available language options. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-explain/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-explain/ Snapshot: 11 October 2026 ## Features - Topic input - Language selection - Explanation history ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked learner and topic. 2. Select the intended language. 3. Review the generated explanation before using it. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/explain ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/explains — List Explains; Authenticated scope - GET /api/v1/me/explains/:id — Get Explain; Authenticated scope - POST /api/v1/me/explains — Generate Explain; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My fee invoices & receipts Review invoices, outstanding balances and recorded receipts for your linked child. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-fees/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-fees/ Snapshot: 11 October 2026 ## Features - Child-specific invoices - Payment history - Receipt access ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select your child. 2. Open the relevant invoice and balance. 3. Review the available payment history or receipt. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/fees ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My homework & learning history Read assigned class work, submit supported work and review feedback for the selected learner. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-homework/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-homework/ Snapshot: 11 October 2026 ## Features - Assignment list - Due dates - Supported attachments - Submission - Feedback and history ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose your child and open an assignment. 2. Read the instructions and due date. 3. Attach or enter the permitted submission. 4. Review teacher feedback and learning history. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/homework ## API reference - GET /api/v1/me/children — Children; Authenticated scope - POST /api/v1/me/assignments/:id/submit — Submit Assignment; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My learning journey Review the learner’s progress story and available next actions. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-journey/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-journey/ Snapshot: 11 October 2026 ## Features - Progress story - Next actions - Learner context ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the learner. 2. Read the available progress story. 3. Open a suggested next action and review the related record. ## Fields and controls - studentId (string, optional) - interests (string, optional) - psychometric (Record, optional) - opportunityType (string, optional) - interestArea (string, optional) ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/journey ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/progress-story — Progress Story; Authenticated scope - POST /api/v1/me/career-twin — Career Twin; Authenticated scope - POST /api/v1/me/alumni-opportunity — Alumni Opportunity; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My learning path Review available focus areas and update the permitted learning-path item state. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-learning-path/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-learning-path/ Snapshot: 11 October 2026 ## Features - Focus areas - Suggested activities - Progress updates ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the learner. 2. Review the available focus areas. 3. Complete a suggested activity and update its permitted state. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/learning-path ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/learning-path — Learning Path; Authenticated scope - POST /api/v1/me/learning-path — Regenerate Learning Path; Authenticated scope - PATCH /api/v1/me/learning-path-items/:itemId — Update Learning Path Item; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Report an absence Report an absence for your linked child and review the school’s decision. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-leave/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-leave/ Snapshot: 11 October 2026 ## Features - Own absence reports - Dates and reason - Decision status ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked child. 2. Enter the absence dates and reason. 3. Submit the report and review its status. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/leave ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My library loans & reservations Review your linked learner’s loans and use available renewal or reservation actions. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-library/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-library/ Snapshot: 11 October 2026 ## Features - My loans - Due dates - Reservations - Permitted renewal ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked learner. 2. Review issued books and due dates. 3. Renew or reserve an eligible title where allowed. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/library ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My live classes Review the learner’s available live lesson schedule and open a class detail. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-live-classes/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-live-classes/ Snapshot: 11 October 2026 ## Features - Assigned class list - Schedule - Class detail ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the learner. 2. Review the available class schedule. 3. Open the intended class and joining details. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/live-classes ## API reference - GET /api/v1/me/live-classes — Live Classes List; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Join a live class Open an eligible live class and use its available live or recorded lesson experience. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-live-classes-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-live-classes-id-detail/ Snapshot: 11 October 2026 ## Features - Class details - Join experience - Available recording ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the class from your class list. 2. Review its time and current state. 3. Join using the available control or open a recording when provided. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/live-classes — select the actual record from this list. ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My courses Open courses available to the signed-in learner. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-lms/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-lms/ Snapshot: 11 October 2026 ## Features - Course catalogue - Course details - Learning progress ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the learner. 2. Choose an available course. 3. Open its modules and lessons. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/lms ## API reference - GET /api/v1/me/lms/courses — Lms Courses; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Learn a course lesson Follow the course’s modules and lessons and record permitted progress. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-lms-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-lms-id-detail/ Snapshot: 11 October 2026 ## Features - Modules and lessons - Learning content - Lesson progress ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the course from your course list. 2. Choose the lesson and review its content. 3. Record progress through the available lesson control. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/lms — select the actual record from this list. ## API reference - GET /api/v1/me/lms/courses/:id — Lms Course; Authenticated scope - PATCH /api/v1/me/lms/lessons/:id/progress — Lms Lesson Progress; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My school notices Read notices available to the signed-in school and family context. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-notices/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-notices/ Snapshot: 11 October 2026 ## Features - Linked children - Attendance and fees - Published results - Homework and courses - Timetable - Library - PTM - Transport - Personal documents ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the notices screen. 2. Choose an available notice. 3. Read the details and any attached school instructions. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/notices ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Family overview See the selected child’s school information and open the available self-service areas. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal/ Guided sample demo: https://avkul.in/docs/demo/screen-portal/ Snapshot: 11 October 2026 ## Features - Linked child selector - Quick links - Personal school overview ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the linked child. 2. Open attendance, learning, fees or another available service. 3. Review the selected child’s information. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal ## API reference - GET /api/v1/me/children — Children; Authenticated scope - GET /api/v1/me/attendance — Attendance; Authenticated scope - GET /api/v1/me/fees — Fees; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My profile & guardians Review the linked learner’s profile, guardians and available personal information. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-profile/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-profile/ Snapshot: 11 October 2026 ## Features - Learner profile - Guardian information - Personal records ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the learner. 2. Review the displayed profile and guardians. 3. Contact the school for corrections where editing is not provided. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/profile ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Book a parent–teacher meeting Book an eligible teacher slot and review family-visible meeting follow-ups. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-ptm/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-ptm/ Snapshot: 11 October 2026 ## Features - Available slots - My bookings - Reschedule/cancel - Family-visible follow-ups ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked child and available teacher slot. 2. Book the meeting and confirm its time. 3. Change the booking if needed. 4. Review family-visible notes and complete a permitted follow-up. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/ptm ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My published results Review published report cards for the selected child and open the available printable result. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-results/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-results/ Snapshot: 11 October 2026 ## Features - Published report cards - Exam results - Print view ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the child. 2. Choose a published exam result. 3. Review the report card and use the available print view. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/results ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My timetable Review the learner’s weekly timetable and daily teacher cover. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-timetable/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-timetable/ Snapshot: 11 October 2026 ## Features - Weekly view - Daily date - Subjects and times - Print ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select the child. 2. Choose the weekly or daily view. 3. Inspect the timetable and available cover information. 4. Print the selected view if needed. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/timetable ## API reference - GET /api/v1/me/children — Children; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My wellbeing information Review the wellbeing and health information available to your linked family context. Category: Family portal Guide: https://avkul.in/docs/guides/screen-portal-wellbeing/ Guided sample demo: https://avkul.in/docs/demo/screen-portal-wellbeing/ Snapshot: 11 October 2026 ## Features - Selected child - Available wellbeing information - Sick-room records ## Access and setup Intended access: Linked parent / learner account - A signed-in account linked to the selected learner or personal staff profile. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the linked child. 2. Review the permitted wellbeing and sick-room information. 3. Contact the school about information requiring attention. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Only linked children and personal records are available. Staff-only notes and administrative controls are not part of this family screen. - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/portal/wellbeing ## API reference - GET /api/v1/me/wellbeing — My Wellbeing; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform AI Support Center Ask platform questions with access to the supported aggregate context. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-ai-center/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-ai-center/ Snapshot: 11 October 2026 ## Features - Question input - Aggregate context - Provider status - Answer review ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Review the provider banner. 2. Ask a supported platform question. 3. Check the response against the relevant report. ## Fields and controls - question (string, declared required) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/ai-center ## API reference - POST /api/v1/saas/ai-center/ask — Ask a plain-English question about the platform — answered from real, computed aggregates; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform analytics Review cross-tenant growth, revenue and churn analytics. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-analytics/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-analytics/ Snapshot: 11 October 2026 ## Features - Growth - Revenue - Churn - Narrative summary ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open platform analytics. 2. Review the relevant reporting period and metrics. 3. Cross-check the generated narrative against the totals. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/analytics ## API reference - GET /api/v1/saas/analytics — Cross-tenant growth/revenue/churn analytics with an AI-generated narrative summary; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform audit trail Inspect platform administrative activity across tenants. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-audit-log/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-audit-log/ Snapshot: 11 October 2026 ## Features - Actor and action - Tenant context - Time and entity detail ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the available audit filters. 2. Find the relevant administrative action. 3. Review its tenant and entity context. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/audit-log ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # AI tenant provisioning Provision a tenant from the supported school and owner inputs. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-command-center/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-command-center/ Snapshot: 11 October 2026 ## Features - School and owner facts - Provisioning request - Provisioning result ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Enter the intended school and owner details. 2. Review the requested setup. 3. Provision only an approved tenant and review the result. ## Fields and controls - schoolName (string, declared required) - institutionType ((typeof INSTITUTION_TYPES)[number], declared required) - ownerName (string, declared required) - ownerEmail (string, declared required) - ownerPhone (string, optional) - domain (string, optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/command-center ## API reference - POST /api/v1/saas/tenants/ai-provision — AI Command Center — provision a full tenant from just school/owner facts and email the owner their access; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Subscription coupons Issue and manage billing discount codes with usage and validity controls. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-coupons/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-coupons/ Snapshot: 11 October 2026 ## Features - Code window - Redemption limits - Active flag - Invoice preview and apply ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Create the approved coupon terms. 2. Review dates and redemption caps. 3. Preview its invoice effect before applying. ## Fields and controls - code (string, optional) - description (string, optional) - type (string, declared required) - value (number, declared required) - maxRedemptions (number, optional) - validFrom (string, optional) - validUntil (string, optional) - isActive (boolean, optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/coupons ## API reference - GET /api/v1/saas/coupons — List discount codes with their redemption counts; Platform admin - POST /api/v1/saas/coupons — Issue a discount code; Platform admin - PATCH /api/v1/saas/coupons/:id — Change a code’s window, cap or active flag; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Support impersonation Inspect and manage platform support sessions separately from ordinary sign-in. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-impersonation/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-impersonation/ Snapshot: 11 October 2026 ## Features - Start/stop impersonation - Open sessions - Close lapsed sessions - Audit history ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Review the permitted support context. 2. Start the intended support session only when authorised. 3. Stop the session and review its audit record. ## Fields and controls - sessionId (string, optional) ## Current limits - Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited. ## Actual application access - https://avkul.in/en/saas/impersonation ## API reference - POST /api/v1/auth/impersonate/stop — End an impersonation session; Authenticated scope - GET /api/v1/auth/impersonate/active — Open impersonation sessions (platform admins only); Authenticated scope - POST /api/v1/auth/impersonate/close-lapsed — Close expired impersonation sessions (platform admins only); Authenticated scope - GET /api/v1/auth/impersonate/history — Impersonation audit history (platform admins only); Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform invoices Review subscription billing records across tenants. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-invoices/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-invoices/ Snapshot: 11 October 2026 ## Features - Invoice list - Invoice detail - Payment status ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Find the intended tenant invoice. 2. Review totals and payment state. 3. Open invoice details before a payment action. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/invoices ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform invoice detail Review one SaaS invoice and its available gateway collection workflow. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-invoices-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-invoices-id-detail/ Snapshot: 11 October 2026 ## Features - Invoice lines - Status and totals - Gateway order - Verified payment callback ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the invoice from the platform invoice list. 2. Review its lines and remaining balance. 3. Use online payment only with a configured gateway. ## Fields and controls - amount (number, optional) - paymentLogId (string, declared required) - razorpayPaymentId (string, optional) - razorpaySignature (string, optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/invoices — select the actual record from this list. ## API reference - GET /api/v1/saas/invoices/:id — Invoice; Platform admin - POST /api/v1/saas/invoices/:id/payment-order — Create a Razorpay order to collect payment against an invoice; Platform admin - POST /api/v1/saas/payments/verify — Verify a Razorpay payment callback and mark the invoice paid; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Landing Page CMS Edit, preview and publish the public AVKUL ERP landing page with version history. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-landing-page/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-landing-page/ Snapshot: 11 October 2026 ## Features - Draft editor - Section order and visibility - SEO fields - Private preview - Publish - History and restore ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Load the current content and edit a draft. 2. Select media and review section order and visibility. 3. Open the private preview. 4. Publish the reviewed version or restore an earlier version. ## Fields and controls - content (Record, declared required) - draftId (string, declared required) - revisionId (string, declared required) ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/landing-page ## API reference - GET /api/v1/saas/landing-page — Workspace; Platform admin - POST /api/v1/saas/landing-page/draft — Save; Platform admin - POST /api/v1/saas/landing-page/preview — Preview; Platform admin - POST /api/v1/saas/landing-page/publish — Publish; Platform admin - POST /api/v1/saas/landing-page/restore — Restore; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Campaign Manager Create trackable campaign links and review attributed visits, enquiries and conversions. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-marketing-campaigns/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-marketing-campaigns/ Snapshot: 11 October 2026 ## Features - Immutable tracking labels - Campaign dates and status - Tracking link - Period metrics - Search and CSV ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Create a draft campaign with source, medium and destination. 2. Copy its tracking link and use it in the intended campaign. 3. Review visits and accepted enquiries for a UTC period. 4. Update the administrative status without changing the tracking key. ## Fields and controls - source (string, declared required) - medium (string, declared required) ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/marketing-campaigns ## API reference - GET /api/v1/saas/marketing-campaigns — List; Platform admin - GET /api/v1/saas/marketing-campaigns/export — Export; Platform admin - POST /api/v1/saas/marketing-campaigns — Create; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Demo Enquiry CRM Assign and progress product walkthrough enquiries with contact history and scheduling. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-marketing-leads/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-marketing-leads/ Snapshot: 11 October 2026 ## Features - Walkthrough pipeline - Search and owner filters - Demo/follow-up dates - Internal notes - Attribution - CSV export ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Find a walkthrough enquiry and assign its owner. 2. Record its status, demo date or next follow-up. 3. Add an internal note after contacting the school. 4. Mark the confirmed outcome and review history. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/marketing-leads ## API reference - GET /api/v1/saas/marketing-leads — List; Platform admin - GET /api/v1/saas/marketing-leads/owners — Owners; Platform admin - GET /api/v1/saas/marketing-leads/export — Export; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Demo Calendar & Follow-ups Turn CRM dates into daily work and manage product demos and platform follow-up tasks. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-marketing-workspace/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-marketing-workspace/ Snapshot: 11 October 2026 ## Features - Today/upcoming/overdue - UTC calendar - Schedule and reschedule - Completed/no-show/cancelled outcomes - Priority tasks - In-app reminders ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Review today’s or overdue work. 2. Schedule the demo or follow-up against an open walkthrough enquiry. 3. Record the outcome and optional next follow-up. 4. Complete tasks and review the connected CRM history. ## Fields and controls - title (string, declared required) - dueAt (string, declared required) - priority (string, declared required) - assignedToId (string|null, optional) - leadId (string|null, optional) - note (string, declared required) ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/marketing-workspace ## API reference - GET /api/v1/saas/marketing-leads — List; Platform admin - GET /api/v1/saas/marketing-leads/owners — Owners; Platform admin - GET /api/v1/saas/marketing-workspace — List; Platform admin - GET /api/v1/saas/marketing-workspace/leads — Leads; Platform admin - POST /api/v1/saas/marketing-workspace/tasks — Create; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Website Media Library Upload, organise, crop and reuse supported website images. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-media/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-media/ Snapshot: 11 October 2026 ## Features - JPEG/PNG/static WebP - Folders and search - Desktop/mobile/thumbnail variants - Crop as new asset - Metadata - Archive and restore ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Upload a supported image and enter its descriptive metadata. 2. Organise it into a folder. 3. Create a crop if needed and select it from the CMS. 4. Archive only when no published, draft or historical version references it. ## Fields and controls - name (string, declared required) ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/media ## API reference - GET /api/v1/saas/media — List; Platform admin - GET /api/v1/saas/media/folders — Folders; Platform admin - POST /api/v1/saas/media/folders — Create Folder; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform overview Review platform footprint, revenue indicators and tenant status. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas/ Guided sample demo: https://avkul.in/docs/demo/screen-saas/ Snapshot: 11 October 2026 ## Features - Tenant and school counts - Subscription summary - Platform priorities ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the platform overview. 2. Review the current footprint and billing totals. 3. Open the relevant tenant or report. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas ## API reference - GET /api/v1/saas/overview — Platform KPIs (tenants, footprint, MRR/ARR, billing); Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Subscription plans & modules Create and edit subscription plans with their module toggles. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-plans/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-plans/ Snapshot: 11 October 2026 ## Features - Plan catalogue - Plan editor - Module selection - Archive ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the intended plan. 2. Review pricing fields and enabled modules. 3. Save the approved configuration or archive the plan. ## Fields and controls - name (string, declared required) - code (string, declared required) - description (string, optional) - billingCycle (string, optional) - priceMonthly (number, optional) - priceYearly (number, optional) - trialDays (number, optional) - maxStudents (number, optional) - maxStaff (number, optional) - maxSchools (number, optional) - maxBranches (number, optional) - isPublic (boolean, optional) - isActive (boolean, optional) - moduleKeys (string[], optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/plans ## API reference - GET /api/v1/saas/plans — List subscription plans with their modules; Platform admin - POST /api/v1/saas/plans — Create a plan (with module toggles); Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform reports Generate cross-tenant revenue, usage, churn or activity reports. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-reports/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-reports/ Snapshot: 11 October 2026 ## Features - Report type - JSON/CSV/PDF outputs - Platform scope ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the report type. 2. Review the reporting context. 3. Open or export the generated report in an available format. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/reports ## API reference - GET /api/v1/saas/reports/:type — Cross-tenant report (revenue/usage/churn/activity) as JSON, CSV, or PDF; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tenant subscriptions Review subscriptions and change an approved tenant plan. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-subscriptions/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-subscriptions/ Snapshot: 11 October 2026 ## Features - Subscription list - Current plan - Upgrade/downgrade ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Locate the tenant subscription. 2. Review its current plan and state. 3. Apply the approved plan change and check usage implications. ## Fields and controls - planCode (string, declared required) - name (string, declared required) - code (string, declared required) - description (string, optional) - billingCycle (string, optional) - priceMonthly (number, optional) - priceYearly (number, optional) - trialDays (number, optional) - maxStudents (number, optional) - maxStaff (number, optional) - maxSchools (number, optional) - maxBranches (number, optional) - isPublic (boolean, optional) - isActive (boolean, optional) - moduleKeys (string[], optional) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/subscriptions ## API reference - PATCH /api/v1/saas/subscriptions/:id/plan — Upgrade/downgrade a tenant subscription; Platform admin - GET /api/v1/saas/plans — List subscription plans with their modules; Platform admin - POST /api/v1/saas/plans — Create a plan (with module toggles); Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tenant & school onboarding Search tenants, inspect their health and provision approved school workspaces. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-tenants/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-tenants/ Snapshot: 11 October 2026 ## Features - Search and status - Onboarding - School creation - Status changes - Health scores ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Search for the tenant before creating one. 2. Review school, owner and plan details. 3. Onboard or update the intended tenant. 4. Inspect the resulting tenant detail. ## Fields and controls - tenantName (string, declared required) - slug (string, declared required) - schoolName (string, declared required) - schoolCode (string, declared required) - board (string, optional) - type (string, optional) - adminEmail (string, declared required) - adminPassword (string, declared required) - adminFirstName (string, declared required) - adminLastName (string, optional) - planCode (string, optional) - status (string, declared required) - ids (string[], declared required) - action ('ACTIVATE' | 'SUSPEND' | 'CANCEL', declared required) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/tenants ## API reference - GET /api/v1/saas/tenants — List tenants (search, status filter, paginated); Platform admin - POST /api/v1/saas/tenants — Onboard a new tenant/school (provisions admin + plan); Platform admin - PATCH /api/v1/saas/tenants/:id/status — Activate / suspend / cancel a tenant; Platform admin - POST /api/v1/saas/tenants/bulk-action — Apply activate/suspend/cancel to multiple tenants at once; Platform admin - GET /api/v1/saas/tenants/health/scores — Composite health score per tenant (status, overdue invoices, login recency, trial runway); Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tenant detail & branding Review tenant schools, subscription and quotas and maintain supported branding. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-tenants-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-tenants-id-detail/ Snapshot: 11 October 2026 ## Features - School list - Subscription and counts - Branding - Domain settings - Additional schools ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Open the tenant from the list. 2. Review its schools and subscription. 3. Save approved branding or add a school within quota. 4. Verify domain setup separately before relying on it. ## Fields and controls - code (string, declared required) - name (string, declared required) - type (string, optional) - board (string, optional) - adminEmail (string, optional) - adminPassword (string, optional) - adminFirstName (string, optional) - adminLastName (string, optional) - brandName (string, optional) - primaryColor (string, optional) - faviconUrl (string, optional) - domain (string, declared required) ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/tenants — select the actual record from this list. ## API reference - GET /api/v1/saas/tenants/:id — Tenant detail with schools, subscription and counts; Platform admin - POST /api/v1/saas/tenants/:id/schools — Add a school to an existing tenant (counts against the plan); Platform admin - PATCH /api/v1/saas/tenants/:id/branding — Update white-label branding (brand name, color, custom domain); Platform admin - POST /api/v1/saas/tenants/:id/domain — Claim a custom domain — returns a DNS TXT record to publish for ownership proof; Platform admin - DELETE /api/v1/saas/tenants/:id/domain — Remove the custom domain and reset verification; Platform admin - POST /api/v1/saas/tenants/:id/domain/verify — Verify domain ownership via a real DNS TXT lookup; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Platform plan usage Review quota and module usage against platform plan limits. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-usage/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-usage/ Snapshot: 11 October 2026 ## Features - Plan limits - Current usage - Module availability ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Choose the tenant or scope available to the view. 2. Compare usage with the plan limits. 3. Review upgrades or cleanup through the appropriate workflow. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/saas/usage ## API reference - GET /api/v1/saas/usage — Every tenant against its plan limits; Platform admin - POST /api/v1/saas/usage/:tenantId/refresh — Recount usage and write this period's counters; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Website Analytics Review privacy-aware website activity and accepted walkthrough conversions for a UTC period. Category: Platform Guide: https://avkul.in/docs/guides/screen-saas-website-analytics/ Guided sample demo: https://avkul.in/docs/demo/screen-saas-website-analytics/ Snapshot: 11 October 2026 ## Features - Visitors and page views - CTA/form activity - Source and campaign - Device and page reports - Conversion funnel - CSV export ## Access and setup Intended access: Platform administrator - Platform administrator access. - Choose the relevant school, academic session or child before working. ## Workflow 1. Select a UTC period of up to 90 days. 2. Review traffic and the form funnel. 3. Compare sources, campaigns and devices. 4. Export the aggregate report if needed. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Campaign links are tracked only where collection is enabled. In-app reminders do not send outbound messages. Marketing administration requires the platform-admin flag. ## Actual application access - https://avkul.in/en/saas/website-analytics ## API reference - GET /api/v1/saas/website-analytics — Report; Platform admin - GET /api/v1/saas/website-analytics/export — Export; Platform admin ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Sessions, classes & subjects Use sessions, classes & subjects in the school workspace. Create the academic structure that attendance, admissions, examinations and timetables share. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-academics/ Guided sample demo: https://avkul.in/docs/demo/screen-school-academics/ Snapshot: 11 October 2026 ## Features - List Sessions - Create Session - List Classes - Create Class - Every academic year and whether its books are closed - Close or re-open an academic year's books ## Access and 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. Permission keys: settings:view, settings:create, student:view, settings:manage ## Workflow 1. Create an academic session with dates. 2. Add classes and their sections. 3. Create subjects and select the current session. 4. Close the books only after the year-end review. ## Fields and controls - Name - Start - End - Session - Level - Class - Capacity - Code - Type ## Current limits - Session ownership and closed-year checks apply to connected workflows. ## Actual application access - https://avkul.in/en/school/academics ## API reference - GET /api/v1/academic/sessions — List Sessions; settings:view - POST /api/v1/academic/sessions — Create Session; settings:create - GET /api/v1/academic/classes — List Classes; student:view - POST /api/v1/academic/classes — Create Class; settings:create - GET /api/v1/academic/sessions/locks — Every academic year and whether its books are closed; settings:view - PATCH /api/v1/academic/sessions/:id/lock — Close or re-open an academic year's books; settings:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Adaptive exam attempt detail Use adaptive exam attempt detail in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-adaptive-exams-attempts-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-adaptive-exams-attempts-id-detail/ Snapshot: 11 October 2026 ## Features - Exam schedules - Marks entry and history - Completion status - Grade scales - Report cards - Publish and unpublish - Seating and invigilation - Adaptive exams - Mark rechecks ## Access and 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. Permission keys: exam:view ## Workflow 1. Create the exam and its subject schedules. 2. Review the candidates, seating and completion status. 3. Record and verify marks, then generate report cards. 4. Publish approved results; use the correction workflow when required. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/adaptive-exams/attempts — select the actual record from this list. ## API reference - GET /api/v1/adaptive-exams/attempts/:attemptId — Attempt Detail; exam:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Adaptive online exams Use adaptive online exams in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-adaptive-exams/ Guided sample demo: https://avkul.in/docs/demo/screen-school-adaptive-exams/ Snapshot: 11 October 2026 ## Features - Save question - Create exam - List - Create - List Questions - Create Question - Get Exam - Update Status ## Access and 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. Permission keys: exam:view, exam:create, exam:update ## Workflow 1. Create the exam and its subject schedules. 2. Review the candidates, seating and completion status. 3. Record and verify marks, then generate report cards. 4. Publish approved results; use the correction workflow when required. ## Fields and controls - title (string, declared required) - subjectId (string, declared required) - classId (string, optional) - sectionId (string, optional) - targetCount (number, optional) - durationMin (number, optional) - maxAttempts (number, optional) - questionIds (string[], optional) - publishResults (boolean, optional) - text (string, declared required) - options (string[], declared required) - correctAnswer (string, declared required) - difficulty (string, optional) - chapter (string, optional) - marks (number, optional) - status ('SCHEDULED' | 'ONGOING' | 'COMPLETED' | 'RESULT_PUBLISHED' | 'LOCKED', declared required) ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/adaptive-exams ## API reference - GET /api/v1/adaptive-exams — List; exam:view - POST /api/v1/adaptive-exams — Create; exam:create - GET /api/v1/adaptive-exams/questions — List Questions; exam:view - POST /api/v1/adaptive-exams/questions — Create Question; exam:create - GET /api/v1/adaptive-exams/:examId — Get Exam; exam:view - PATCH /api/v1/adaptive-exams/:examId/status — Update Status; exam:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Admissions & applicant journey Use admissions & applicant journey in the school workspace. Connect family enquiries, counsellor follow-ups, reviewed applications and student admission. Category: School office Guide: https://avkul.in/docs/guides/screen-school-admissions/ Guided sample demo: https://avkul.in/docs/demo/screen-school-admissions/ Snapshot: 11 October 2026 ## Features - Start application - Log call - Review application - Schedule visit - Save guardian - Save visit - Create student & guardian - Preview student fee - Queue - Leads due a follow-up, oldest overdue first - Pipeline by stage and by source, with conversion - List - History - Record a contact attempt and move the lead on ## Access and 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. Permission keys: admission:view, admission:update, admission:create, admission:manage ## Workflow 1. Record or select an enquiry and log the next follow-up. 2. Open a linked application and review guardian details. 3. Receive and verify required documents and review readiness. 4. Select session, class and section before admitting the applicant. ## Fields and controls - Student name - Parent name - Phone - Guardian email - Enquiry source - Class applying - Include leads never scheduled - Find an applicant - Guardian name - Email for parent portal - Relationship - Visit date and time ## Current limits - Application access links and parent invitations are separate from an existing family login. Admission is subject to readiness and school/session ownership. ## Actual application access - https://avkul.in/en/school/admissions ## API reference - GET /api/v1/admissions/work-queue — Queue; admission:view - GET /api/v1/admissions/enquiries/due — Leads due a follow-up, oldest overdue first; admission:view - GET /api/v1/admissions/enquiries/funnel — Pipeline by stage and by source, with conversion; admission:view - GET /api/v1/admissions/enquiries — List; admission:view - GET /api/v1/admissions/enquiries/:id/follow-ups — History; admission:view - POST /api/v1/admissions/enquiries/:id/follow-ups — Record a contact attempt and move the lead on; admission:update - POST /api/v1/admissions/enquiries — Create; admission:create - PATCH /api/v1/admissions/enquiries/:id — Update; admission:update - DELETE /api/v1/admissions/enquiries/:id — Remove; admission:update - GET /api/v1/admissions/applications — List; admission:view - GET /api/v1/admissions/applications/funnel — Where applicants are, and how many converted; admission:view - POST /api/v1/admissions/applications — Open an application, optionally from an enquiry; admission:create - POST /api/v1/admissions/applications/:id/advance — Move the application one legal step; admission:manage - GET /api/v1/admissions/applications/:id/journey — Get; admission:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # AI governance & trust Use the ai governance & trust workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-ai-governance/ Guided sample demo: https://avkul.in/docs/demo/screen-school-ai-governance/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: hostel:view, health:manage, dashboard:view, student:manage, settings:update ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - visitorLogId (string, optional) - studentId (string, optional) - vehicleId (string, optional) - days (number, optional) - requestId (string, declared required) - decision (string, declared required) - note (string, optional) - correctedText (string, optional) - biometricEnabled (boolean, optional) - faceMatchEnabled (boolean, optional) - biometricRetentionDays (number, optional) - parentOptOutDefault (boolean, optional) - consentRequiredFeatures (string[], optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/ai-governance ## API reference - POST /api/v1/ai-features/campus-safety — Campus Safety; hostel:view - GET /api/v1/ai-features/wellbeing-radar — Wellbeing Radar; health:manage - GET /api/v1/ai-features/ai-audit — Ai Audit; dashboard:view - POST /api/v1/ai-features/ai-audit/feedback — Ai Audit Feedback; dashboard:view - GET /api/v1/ai-features/fairness-monitor — Fairness Monitor; student:manage - GET /api/v1/ai-features/data-minimization — Get Data Minimization; dashboard:view - PATCH /api/v1/ai-features/data-minimization — Update Data Minimization; settings:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School AI tools Use school ai tools in the school workspace. Use assisted writing, learning support and forecasts while reviewing the provider state and human decisions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-ai-tools/ Guided sample demo: https://avkul.in/docs/demo/screen-school-ai-tools/ Snapshot: 11 October 2026 ## Features - AI configuration status; does not contact the provider or expose secrets - Generate Remark - Attendance Anomalies - Fee Risk - Generate Question Paper - Discipline Risk ## Access and 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. Permission keys: dashboard:view, exam:update, attendance:view, fee:view, exam:create, student:view, lms:view, timetable:view, inventory:view, communication:create, attendance:create, hostel:view, exam:view, student:manage, fee:manage, attendance:update, transport:view, health:manage, settings:update ## Workflow 1. Review the provider-status banner before requesting assistance. 2. Choose the school context, topic or forecast period. 3. Run the relevant tool and inspect its output and evidence. 4. Review or edit the result before using it with learners. ## Fields and controls - AI readiness ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/provider-status — AI configuration status; does not contact the provider or expose secrets; dashboard:view - POST /api/v1/ai-features/remarks — Generate Remark; exam:update - GET /api/v1/ai-features/attendance-anomalies — Attendance Anomalies; attendance:view - GET /api/v1/ai-features/fee-risk — Fee Risk; fee:view - POST /api/v1/ai-features/question-paper — Generate Question Paper; exam:create - GET /api/v1/ai-features/discipline-risk — Discipline Risk; student:view - POST /api/v1/ai-features/parent-chat — Parent Chat; dashboard:view - POST /api/v1/ai-features/study-buddy — Study Buddy; lms:view - GET /api/v1/ai-features/career-counsel/:studentId — Career Counsel; student:view - GET /api/v1/ai-features/timetable-suggest — Suggest Timetable; timetable:view - GET /api/v1/ai-features/inventory-reorder — Inventory Reorder; inventory:view - POST /api/v1/ai-features/notice-draft — Draft Notice; communication:create - POST /api/v1/ai-features/alumni-match — Match Alumni; student:view - POST /api/v1/ai-features/voice-attendance — Voice Attendance; attendance:create - POST /api/v1/ai-features/visitor-verify — Verify Visitor Photo; hostel:view - GET /api/v1/ai-features/dropout-risk — Dropout Risk; student:view - GET /api/v1/ai-features/repeat-visitors — Repeat Visitors; hostel:view - POST /api/v1/ai-features/face-match — Compare Faces; hostel:view - POST /api/v1/ai-features/learning-path — Learning Path; lms:view - POST /api/v1/ai-features/learning-gaps/scan — Run Learning Gap Scan; student:view - POST /api/v1/ai-features/adaptive-exam — Adaptive Exam; exam:view - GET /api/v1/ai-features/lesson-planner — List Lesson Plans; timetable:view - POST /api/v1/ai-features/lesson-planner — Generate Lesson Plan; timetable:view - GET /api/v1/ai-features/multilingual-explain — List Multilingual Explain; lms:view - POST /api/v1/ai-features/multilingual-explain — Generate Multilingual Explain; lms:view - GET /api/v1/ai-features/enrolment-forecast — List Enrolment Forecast; student:manage - POST /api/v1/ai-features/enrolment-forecast — Run Enrolment Forecast; student:manage - GET /api/v1/ai-features/cashflow-prediction — List Cashflow; fee:manage - POST /api/v1/ai-features/cashflow-prediction — Run Cashflow; fee:manage - GET /api/v1/ai-features/staff-workload — List Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload — Run Staff Workload; timetable:view, attendance:update - GET /api/v1/ai-features/transport-eta — List Transport Eta; transport:view - POST /api/v1/ai-features/transport-eta — Run Transport Eta; transport:view - GET /api/v1/ai-features/hostel-inventory-forecast — List Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast — Run Inventory Forecast; inventory:view - POST /api/v1/ai-features/parent-copilot — Parent Copilot; dashboard:view - POST /api/v1/ai-features/voice-assistant — Voice Assistant; dashboard:view - POST /api/v1/ai-features/progress-story — Progress Story; student:view - POST /api/v1/ai-features/career-twin — Career Twin; student:view - POST /api/v1/ai-features/alumni-opportunity — Alumni Opportunity; student:view - POST /api/v1/ai-features/campus-safety — Campus Safety; hostel:view - GET /api/v1/ai-features/wellbeing-radar — Wellbeing Radar; health:manage - GET /api/v1/ai-features/ai-audit — Ai Audit; dashboard:view - POST /api/v1/ai-features/ai-audit/feedback — Ai Audit Feedback; dashboard:view - GET /api/v1/ai-features/fairness-monitor — Fairness Monitor; student:manage - GET /api/v1/ai-features/data-minimization — Get Data Minimization; dashboard:view - PATCH /api/v1/ai-features/data-minimization — Update Data Minimization; settings:update - POST /api/v1/ai-features/auto-grade — Auto Grade; exam:update - POST /api/v1/ai-features/classroom-insights — Classroom Insights; attendance:view - POST /api/v1/ai-features/substitution-brain — Substitution Brain; timetable:view - POST /api/v1/ai-features/question-bank-intel — Question Bank Intel; exam:view - POST /api/v1/ai-features/meeting-notes — Meeting Notes; communication:create - GET /api/v1/ai-features/school-twin-benchmark — School Twin Benchmark; dashboard:view - POST /api/v1/ai-features/policy-copilot — Policy Copilot; dashboard:view - POST /api/v1/ai-features/accreditation-pack — Accreditation Pack; dashboard:view - GET /api/v1/ai-features/branch-performance — Branch Performance; dashboard:view - POST /api/v1/ai-features/whatsapp-parent-copilot/simulate — Simulate; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Alumni records Use alumni records in the school workspace. Maintain alumni information and keep former learners connected to the school community. Category: Community Guide: https://avkul.in/docs/guides/screen-school-alumni/ Guided sample demo: https://avkul.in/docs/demo/screen-school-alumni/ Snapshot: 11 October 2026 ## Features - Alumni directory - Record creation - Profile updates - Record removal ## Access and 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. Permission keys: student:view, student:create ## Workflow 1. Open the alumni directory. 2. Add the alumnus and relevant year/contact details. 3. Update the record as information changes. 4. Review scope before removing an entry. ## Fields and controls - First name - Last name - Phone ## Current limits - A directory record does not automatically provision an alumni login or send invitations. ## Actual application access - https://avkul.in/en/school/alumni ## API reference - GET /api/v1/alumni — List; student:view - POST /api/v1/alumni — Create; student:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notices, announcements & messages Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations. Category: Community Guide: https://avkul.in/docs/guides/screen-school-announcements/ Guided sample demo: https://avkul.in/docs/demo/screen-school-announcements/ Snapshot: 11 October 2026 ## Features - Delivery report - List Templates - Create Template - Count and channel-reachability for an audience - List - Per-recipient delivery report - Create ## Access and 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. Permission keys: communication:view, communication:create, communication:manage ## Workflow 1. Choose the notice, announcement or conversation workflow. 2. Select the permitted audience and prepare the content. 3. Preview reachability before sending where available. 4. Review delivery reports, replies or complaint status. ## Fields and controls - Use a template (optional) - Title - Message - Audience - Class - Section ## Current limits - External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it. ## Actual application access - https://avkul.in/en/school/announcements ## API reference - GET /api/v1/announcements/templates — List Templates; communication:view - POST /api/v1/announcements/templates — Create Template; communication:create - POST /api/v1/announcements/preview-audience — Count and channel-reachability for an audience; communication:view - GET /api/v1/announcements — List; communication:view - GET /api/v1/announcements/:id/deliveries — Per-recipient delivery report; communication:view - POST /api/v1/announcements — Create; communication:create - POST /api/v1/announcements/:id/send — Deliver the announcement across its channels; communication:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Homework & assignments Use homework & assignments in the school workspace. Create and distribute class work, collect student submissions and record grading feedback. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-assignments/ Guided sample demo: https://avkul.in/docs/demo/screen-school-assignments/ Snapshot: 11 October 2026 ## Features - New assignment - Create assignment - Save grade - Return for revision - Save assignment changes - Send due reminders - Delete empty assignment - Student work - List - Dashboard - Remind - Reminder History - History - Get ## Access and 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. Permission keys: assignment:view, assignment:update, assignment:create, assignment:delete ## Workflow 1. Select the teaching section and create an assignment. 2. Add the instructions, due date and supported files. 3. Review submitted or pending work. 4. Grade the submission and review the activity history. ## Fields and controls - Title - Assignment class - Assignment section - Subject - Due date & time - Maximum marks - Visibility - Instructions - Filter class - Filter section - Status - Marks for ## Current limits - Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel. ## Actual application access - https://avkul.in/en/school/assignments ## API reference - GET /api/v1/assignments — List; assignment:view - GET /api/v1/assignments/dashboard — Dashboard; assignment:view - POST /api/v1/assignments/remind — Remind; assignment:update - GET /api/v1/assignments/:id/reminders — Reminder History; assignment:view - GET /api/v1/assignments/:id/history — History; assignment:view - GET /api/v1/assignments/:id — Get; assignment:view - POST /api/v1/assignments — Create; assignment:create - PATCH /api/v1/assignments/:id — Update; assignment:update - DELETE /api/v1/assignments/:id — Remove; assignment:delete - PATCH /api/v1/assignments/submissions/:submissionId/grade — Grade Submission; assignment:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Assignment detail & submission review Use assignment detail & submission review in the school workspace. Create and distribute class work, collect student submissions and record grading feedback. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-assignments-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-assignments-id-detail/ Snapshot: 11 October 2026 ## Features - New assignment - Create assignment - Save grade - Return for revision - Save assignment changes - Send due reminders - Delete empty assignment - Student work - List - Dashboard - Remind - Reminder History - History - Get ## Access and 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. Permission keys: assignment:view, assignment:update, assignment:create, assignment:delete ## Workflow 1. Select the teaching section and create an assignment. 2. Add the instructions, due date and supported files. 3. Review submitted or pending work. 4. Grade the submission and review the activity history. ## Fields and controls - Title - Assignment class - Assignment section - Subject - Due date & time - Maximum marks - Visibility - Instructions - Filter class - Filter section - Status - Marks for ## Current limits - Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel. ## Actual application access - https://avkul.in/en/school/assignments — select the actual record from this list. ## API reference - GET /api/v1/assignments — List; assignment:view - GET /api/v1/assignments/dashboard — Dashboard; assignment:view - POST /api/v1/assignments/remind — Remind; assignment:update - GET /api/v1/assignments/:id/reminders — Reminder History; assignment:view - GET /api/v1/assignments/:id/history — History; assignment:view - GET /api/v1/assignments/:id — Get; assignment:view - POST /api/v1/assignments — Create; assignment:create - PATCH /api/v1/assignments/:id — Update; assignment:update - DELETE /api/v1/assignments/:id — Remove; assignment:delete - PATCH /api/v1/assignments/submissions/:submissionId/grade — Grade Submission; assignment:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student attendance Use student attendance in the school workspace. Complete a daily class register and review attendance history, shortages and family alerts. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-attendance/ Guided sample demo: https://avkul.in/docs/demo/screen-school-attendance/ Snapshot: 11 October 2026 ## Features - Mark all present - Students of a section + their status for a date - Mark/replace attendance for a section + date - Tell absent students' guardians, once per student per day - Students below the required attendance percentage - Warn guardians of students below the required percentage - What has already been sent to families ## Access and 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. Permission keys: attendance:view, attendance:create, attendance:manage ## Workflow 1. Choose a permitted section and date. 2. Mark the roster and review the section completion summary. 3. Save the register and inspect corrections/history. 4. Review shortages and recorded alerts before reminding families. ## Fields and controls - Class / section - Attendance date - Session - Correction reason - Notify absent students’ guardians in-app on save ## Current limits - Holiday and attendance policy affect denominators. Only permitted sections are visible; recording an absence is distinct from approving leave. ## Actual application access - https://avkul.in/en/school/attendance ## API reference - GET /api/v1/attendance/roster — Students of a section + their status for a date; attendance:view - POST /api/v1/attendance/mark — Mark/replace attendance for a section + date; attendance:create - POST /api/v1/attendance/alerts/absence — Tell absent students' guardians, once per student per day; attendance:manage - GET /api/v1/attendance/shortages — Students below the required attendance percentage; attendance:view - POST /api/v1/attendance/alerts/shortage — Warn guardians of students below the required percentage; attendance:manage - GET /api/v1/attendance/alerts — What has already been sent to families; attendance:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Audit trail Use audit trail in the school workspace. Review the recorded actions taken on school records and trace related entities. Category: Administration Guide: https://avkul.in/docs/guides/screen-school-audit-log/ Guided sample demo: https://avkul.in/docs/demo/screen-school-audit-log/ Snapshot: 11 October 2026 ## Features - Activity filters - Actor and action - Entity references - Record detail ## Access and 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. Permission keys: settings:view ## Workflow 1. Select an entity or activity filter. 2. Locate the relevant actor and time. 3. Open the recorded change and its entity reference. 4. Compare the trail with the current record. ## Fields and controls - Entity - Action - From ## Current limits - The audit view records permitted activity; it is not an editor for rewriting historical actions. ## Actual application access - https://avkul.in/en/school/audit-log ## API reference - GET /api/v1/audit-logs/entities — List Entities; settings:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Branch & campus management Use branch & campus management in the school workspace. See school-wide priorities and manage the campus context used by the ERP. Category: School office Guide: https://avkul.in/docs/guides/screen-school-branches/ Guided sample demo: https://avkul.in/docs/demo/screen-school-branches/ Snapshot: 11 October 2026 ## Features - Make main - Per-branch student/staff counts and fee collection - Open another campus (counts against the plan) - Rename a campus, or make it the main one - Close a campus (refused while anyone is posted to it) ## Access and 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. Permission keys: dashboard:view, settings:create, settings:update, settings:delete ## Workflow 1. Review the school dashboard and current session. 2. Open an outstanding action in the relevant module. 3. Inspect the campus counts and permitted branch settings. 4. Review the consequences before closing a campus. ## Fields and controls - code (string, declared required) - name (string, declared required) - addressLine1 (string, optional) - city (string, optional) - phone (string, optional) - isMain (boolean, optional) ## Current limits - Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow. ## Actual application access - https://avkul.in/en/school/branches ## API reference - GET /api/v1/school/branches/stats — Per-branch student/staff counts and fee collection; dashboard:view - POST /api/v1/school/branches — Open another campus (counts against the plan); settings:create - PATCH /api/v1/school/branches/:id — Rename a campus, or make it the main one; settings:update - DELETE /api/v1/school/branches/:id — Close a campus (refused while anyone is posted to it); settings:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School calendar & holidays Use school calendar & holidays in the school workspace. Publish the dates, events and holiday settings that support school planning and attendance. Category: School office Guide: https://avkul.in/docs/guides/screen-school-calendar/ Guided sample demo: https://avkul.in/docs/demo/screen-school-calendar/ Snapshot: 11 October 2026 ## Features - Today - ( ) - Remove - Feed - Working Days - Get Policy - Set Policy - List Holidays - Create Holiday ## Access and 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. Permission keys: calendar:view, settings:update, calendar:create, calendar:update, calendar:delete, communication:manage ## Workflow 1. Review the selected calendar period. 2. Add or update a permitted holiday or event. 3. Check applicability to students and staff. 4. Review working days and RSVP summaries. ## Fields and controls - guests ## Current limits - Declaring a holiday requires its own permission. The attendance and timetable workflows use their documented calendar rules. ## Actual application access - https://avkul.in/en/school/calendar ## API reference - GET /api/v1/calendar — Feed; calendar:view - GET /api/v1/calendar/working-days — Working Days; calendar:view - GET /api/v1/calendar/attendance-policy — Get Policy; calendar:view - PATCH /api/v1/calendar/attendance-policy — Set Policy; settings:update - GET /api/v1/calendar/holidays — List Holidays; calendar:view - POST /api/v1/calendar/holidays — Create Holiday; calendar:create - PATCH /api/v1/calendar/holidays/:id — Update Holiday; calendar:update - DELETE /api/v1/calendar/holidays/:id — Remove Holiday; calendar:delete - POST /api/v1/calendar/events/:id/rsvp — Rsvp; Authenticated scope - GET /api/v1/calendar/events/:id/rsvp/mine — My Rsvp; Authenticated scope - GET /api/v1/calendar/events/:id/rsvp/summary — Rsvp Summary; communication:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Cashflow prediction Use the cashflow prediction workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-cashflow/ Guided sample demo: https://avkul.in/docs/demo/screen-school-cashflow/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: fee:manage ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - scholarshipPct (number, optional) - months (number, optional) - collectionRatePct (number, optional) - label (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/cashflow ## API reference - GET /api/v1/ai-features/cashflow-prediction — List Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/compare — Compare Cashflow; fee:manage - POST /api/v1/ai-features/cashflow-prediction — Run Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/:id — Get Cashflow; fee:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Certificates & verification Use certificates & verification in the school workspace. Manage certificate templates, issue documents and provide token-based verification. Category: School office Guide: https://avkul.in/docs/guides/screen-school-certificates/ Guided sample demo: https://avkul.in/docs/demo/screen-school-certificates/ Snapshot: 11 October 2026 ## Features - Revoke - List Templates - Create Template ## Access and 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. Permission keys: certificate:view, certificate:create, certificate:update ## Workflow 1. Choose or create a certificate template. 2. Select the eligible recipient and issue the document. 3. Review the generated certificate record. 4. Use the document verification token to check validity. ## Fields and controls - Name - Type - Student ## Current limits - Verification requires an actual generated token. Sample demo certificates are not school-issued documents. ## Actual application access - https://avkul.in/en/school/certificates ## API reference - GET /api/v1/certificate/templates — List Templates; certificate:view - POST /api/v1/certificate/templates — Create Template; certificate:create - POST /api/v1/certificate/generated/:id/revoke — Revoke; certificate:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # College administration Use college administration in the school workspace. Manage department and semester structures, electives, internal marks, placements and research records. Category: Institutions Guide: https://avkul.in/docs/guides/screen-school-college/ Guided sample demo: https://avkul.in/docs/demo/screen-school-college/ Snapshot: 11 October 2026 ## Features - Add - Remove - Offer - Enrol - Record - Log - Register - College overview stats - List all departments - Create a department - Update a department - Delete a department - List semesters (filter by departmentId) ## Access and 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. Permission keys: student:view, student:create, student:update, student:delete ## Workflow 1. Create the department and semester structure. 2. Offer electives with the required limits. 3. Record eligible enrollments and internal marks. 4. Maintain placement and research records. ## Fields and controls - name (string, declared required) - code (string, declared required) - hodStaffId (string, optional) - description (string, optional) - totalSeats (number, optional) - departmentId (string, declared required) - semesterNo (number, declared required) - type (SemesterType, declared required) - startDate (string, optional) - endDate (string, optional) - totalCredits (number, optional) - subjectId (string, declared required) - semesterId (string, declared required) - maxStudents (number, optional) - credits (number, optional) - teacherStaffId (string, optional) - studentId (string, declared required) - assignment1 (number, optional) - assignment2 (number, optional) - midSem (number, optional) - attendance (number, optional) - practical (number, optional) - maxMarks (number, optional) - companyName (string, declared required) ## Current limits - College workflows share the school account and permission context; college-specific setup must exist. ## Actual application access - https://avkul.in/en/school/college ## API reference - GET /api/v1/college/stats — College overview stats; student:view - GET /api/v1/college/departments — List all departments; student:view - POST /api/v1/college/departments — Create a department; student:create - PATCH /api/v1/college/departments/:id — Update a department; student:update - DELETE /api/v1/college/departments/:id — Delete a department; student:delete - GET /api/v1/college/semesters — List semesters (filter by departmentId); student:view - POST /api/v1/college/semesters — Create a semester; student:create - GET /api/v1/college/electives — List elective subjects (filter by semesterId); student:view - POST /api/v1/college/electives — Create an elective subject offering; student:create - GET /api/v1/college/internal-marks — List internal marks (filter by semesterId, studentId); student:view - POST /api/v1/college/internal-marks — Create internal marks entry; student:create - GET /api/v1/college/placements — List placement records (filter by status); student:view - POST /api/v1/college/placements — Create a placement record; student:create - GET /api/v1/college/research — List research projects (filter by departmentId); student:view - POST /api/v1/college/research — Create a research project; student:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notices, announcements & messages Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations. Category: Community Guide: https://avkul.in/docs/guides/screen-school-communication/ Guided sample demo: https://avkul.in/docs/demo/screen-school-communication/ Snapshot: 11 October 2026 ## Features - Notices - Create Notice - Events - Create Event - Complaints - Create Complaint ## Access and 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. Permission keys: communication:view, communication:create, communication:update ## Workflow 1. Choose the notice, announcement or conversation workflow. 2. Select the permitted audience and prepare the content. 3. Preview reachability before sending where available. 4. Review delivery reports, replies or complaint status. ## Fields and controls - Title - Message - Audience - Date - Venue - Subject - Details - Priority ## Current limits - External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it. ## Actual application access - https://avkul.in/en/school/communication ## API reference - GET /api/v1/communication/notices — Notices; communication:view - POST /api/v1/communication/notices — Create Notice; communication:create - GET /api/v1/communication/events — Events; communication:view - POST /api/v1/communication/events — Create Event; communication:create - GET /api/v1/communication/complaints — Complaints; communication:view - POST /api/v1/communication/complaints — Create Complaint; communication:create - PATCH /api/v1/communication/complaints/:id — Update Complaint; communication:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Discipline & behaviour Use discipline & behaviour in the school workspace. Record incidents, review student standing and manage sanctions through dedicated access. Category: Student care Guide: https://avkul.in/docs/guides/screen-school-discipline/ Guided sample demo: https://avkul.in/docs/demo/screen-school-discipline/ Snapshot: 11 October 2026 ## Features - Schedule - Served - Waive - List - Watchlist - List Sanctions - Get Policy - Set Policy ## Access and 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. Permission keys: discipline:view, discipline:manage, discipline:update, discipline:create ## Workflow 1. Locate the student within your permitted scope. 2. Record the incident and relevant context. 3. Review standing and any suggested threshold action. 4. Schedule or close the appropriate sanction. ## Fields and controls - Description - Tell the family about every incident, not only escalations ## Current limits - Behaviour records have dedicated sensitive-data permissions; general student access does not imply access. ## Actual application access - https://avkul.in/en/school/discipline ## API reference - 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 - POST /api/v1/discipline/sanctions/:id/schedule — Schedule; discipline:update - POST /api/v1/discipline/sanctions/:id/close — Close Sanction; discipline:update - POST /api/v1/discipline — Create; discipline:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Enrolment & capacity forecast Use the enrolment & capacity forecast workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-enrolment-forecast/ Guided sample demo: https://avkul.in/docs/demo/screen-school-enrolment-forecast/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: student:manage ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - conversionPct (number, optional) - defaultSectionCapacity (number, optional) - studentsPerTeacher (number, optional) - label (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/enrolment-forecast ## API reference - GET /api/v1/ai-features/enrolment-forecast — List Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/compare — Compare Enrolment Forecast; student:manage - POST /api/v1/ai-features/enrolment-forecast — Run Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/:id — Get Enrolment Forecast; student:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Exam seating & invigilation Use exam seating & invigilation in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-exam-seating/ Guided sample demo: https://avkul.in/docs/demo/screen-school-exam-seating/ Snapshot: 11 October 2026 ## Features - Exam rooms - Room capacity - Candidate seating - Invigilator duties - Admit-card details ## Access and 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. Permission keys: exam:view, exam:create, exam:manage, exam:update ## Workflow 1. Create the required exam rooms. 2. Select the paper and allocate candidate seating. 3. Assign the invigilators and review the seating chart. ## Fields and controls - name (string, declared required) - rows (number, optional) - seatsPerRow (number, optional) - blockedSeats (number, optional) - building (string, optional) - floor (string, optional) - scheduleId (string, declared required) - roomIds (string[], optional) - replace (boolean, optional) - roomId (string, declared required) - staffId (string, declared required) - role (string, optional) - examType (string, optional) - sessionId (string, optional) - termId (string, optional) - startDate (string, optional) - endDate (string, optional) - classId (string, declared required) - sectionId (string, optional) - subjectId (string, declared required) - examDate (string, optional) - startTime (string, optional) - endTime (string, optional) - maxMarks (number, declared required) ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/exam-seating ## API reference - GET /api/v1/exam-seating/rooms — List Rooms; exam:view - POST /api/v1/exam-seating/rooms — Create Room; exam:create - POST /api/v1/exam-seating/allocate — Seat every candidate for one paper; exam:manage - DELETE /api/v1/exam-seating/schedules/:scheduleId/seats — Clear; exam:manage - GET /api/v1/exam-seating/schedules/:scheduleId/plan — Room-by-room seating chart for a paper; exam:view - POST /api/v1/exam-seating/invigilators — Assign Invigilator; exam:update - GET /api/v1/exams — List; exam:view - POST /api/v1/exams — Create; exam:create - GET /api/v1/exams/:examId/schedules — List Schedules; exam:view - POST /api/v1/exams/:examId/schedules — Create Schedule; exam:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Examinations & results Use examinations & results in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-exams/ Guided sample demo: https://avkul.in/docs/demo/screen-school-exams/ Snapshot: 11 October 2026 ## Features - Exam schedules - Marks entry and history - Completion status - Grade scales - Report cards - Publish and unpublish - Seating and invigilation - Adaptive exams - Mark rechecks ## Access and 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. Permission keys: exam:view, exam:create ## Workflow 1. Create the exam and its subject schedules. 2. Review the candidates, seating and completion status. 3. Record and verify marks, then generate report cards. 4. Publish approved results; use the correction workflow when required. ## Fields and controls - Exam name - Start date - End date - Type ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/exams ## API reference - GET /api/v1/exams — List; exam:view - POST /api/v1/exams — Create; exam:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Exam marks & report-card workspace Use exam marks & report-card workspace in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-exams-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-exams-id-detail/ Snapshot: 11 October 2026 ## Features - Save schedule - Marks - Edit - Delete - Save marks - Generate drafts - Publish to parents - Withdraw section results - List Schedules - Completion - Create Schedule - Update - Remove - Marks-entry roster for a schedule ## Access and 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. Permission keys: exam:view, exam:update, exam:delete ## Workflow 1. Create the exam and its subject schedules. 2. Review the candidates, seating and completion status. 3. Record and verify marks, then generate report cards. 4. Publish approved results; use the correction workflow when required. ## Fields and controls - Class - Section - Subject - Subject paper - Correction reason (required when changing saved marks) - Correction reason - Report card section - Withdrawal reason - Report card ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/exams — select the actual record from this list. ## API reference - GET /api/v1/exams/:examId/schedules — List Schedules; exam:view - GET /api/v1/exams/:examId/completion — Completion; exam:view - POST /api/v1/exams/:examId/schedules — Create Schedule; exam:update - PATCH /api/v1/exam-schedules/:id — Update; exam:update - DELETE /api/v1/exam-schedules/:id — Remove; exam:delete - GET /api/v1/exam-schedules/:id/marks — Marks-entry roster for a schedule; exam:view - POST /api/v1/exam-schedules/:id/marks — Save Marks; exam:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Executive Copilot Use the executive copilot workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-executive-copilot/ Guided sample demo: https://avkul.in/docs/demo/screen-school-executive-copilot/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: dashboard:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - question (string, declared required) - board (string, optional) - purpose (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/executive-copilot ## API reference - GET /api/v1/ai-features/school-twin-benchmark — School Twin Benchmark; dashboard:view - POST /api/v1/ai-features/policy-copilot — Policy Copilot; dashboard:view - POST /api/v1/ai-features/accreditation-pack — Accreditation Pack; dashboard:view - GET /api/v1/ai-features/branch-performance — Branch Performance; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Fee structures & billing setup Define fee types, installment amounts and eligible billing structures. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-fee-structures/ Guided sample demo: https://avkul.in/docs/demo/screen-school-fee-structures/ Snapshot: 11 October 2026 ## Features - Fee types - Structure editor - Installments - Billing preview - Invoice generation ## Access and 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. Permission keys: fee:view, fee:create, fee:manage ## Workflow 1. Review the academic scope and fee types. 2. Create a structure with installments. 3. Preview eligible students and existing invoices. 4. Generate the reviewed billing. ## Fields and controls - name (string, declared required) - code (string, optional) - isRecurring (boolean, optional) - isOptional (boolean, optional) - classId (string, optional) - studentId (string, optional) - sessionId (string, optional) - items (FeeStructureItemDto[], declared required) - structureId (string, declared required) - installmentNo (number, optional) - sectionId (string, optional) - dueDate (string, optional) - notes (string, optional) ## Current limits - A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation. ## Actual application access - https://avkul.in/en/school/fee-structures ## API reference - GET /api/v1/fees/types — List Types; fee:view - POST /api/v1/fees/types — Create Type; fee:create - GET /api/v1/fees/structures — List Structures; fee:view - POST /api/v1/fees/structures — Create Structure; fee:create - POST /api/v1/fees/generate/preview — Who would be billed, for how much, and who is already invoiced; fee:view - POST /api/v1/fees/generate — Generate invoices for every eligible student; fee:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Fee collections & dues Use fee collections & dues in the school workspace. Configure charges, preview billing, issue invoices and record collections and adjustments. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-fees/ Guided sample demo: https://avkul.in/docs/demo/screen-school-fees/ Snapshot: 11 October 2026 ## Features - Adjust - Apply discount - Add late fee - Write off balance - Refund - Undo - Preview reminders - Add scheme - Collections Summary - Reconcile Collection - Fine - List Types - Create Type - Concession schemes the school offers ## Access and 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. Permission keys: fee:view, fee:manage, fee:create, fee:update ## Workflow 1. Create the required fee structure and installments. 2. Preview eligible students and existing invoices. 3. Generate invoices and record a valid collection. 4. Review the receipt, remaining balance and adjustment history. ## Fields and controls - Due date - Pending longer than - Collect fee payment - Amount received - Payment method - Transaction reference - Collection notes - Payment receipt - Reconciliation - Receipt, reference or student - Reconcile collection - Cash-book / statement reference ## Current limits - A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation. ## Actual application access - https://avkul.in/en/school/fees ## API reference - GET /api/v1/fees/collections/summary — Collections Summary; fee:view - POST /api/v1/fees/payments/:id/reconcile — Reconcile Collection; fee:manage - POST /api/v1/fees/invoices/:id/fine — Fine; fee:manage - GET /api/v1/fees/types — List Types; fee:view - POST /api/v1/fees/types — Create Type; fee:create - GET /api/v1/fees/concessions/schemes — Concession schemes the school offers; fee:view - POST /api/v1/fees/concessions/schemes — Create Scheme; fee:manage - GET /api/v1/fees/concessions/report — What the school has awarded, and what it has cost; fee:view - GET /api/v1/fees/concessions — List Awards; fee:view - POST /api/v1/fees/concessions — Award a concession to a student (starts as REQUESTED); fee:update - POST /api/v1/fees/concessions/:id/decision — Approve or refuse a requested concession; fee:manage - DELETE /api/v1/fees/concessions/:id — Withdraw an award; issued invoices keep their discount; fee:manage - GET /api/v1/fees/invoices — List Invoices; fee:view - GET /api/v1/fees/dues/ageing — Outstanding fees aged per student; fee:view - POST /api/v1/fees/dues/reminders — Send a payment reminder to fee-paying guardians; fee:manage - GET /api/v1/fees/invoices/:id — Get Invoice; fee:view - POST /api/v1/fees/invoices — Create Invoice; fee:create - POST /api/v1/fees/invoices/:id/payments — Collect a payment against an invoice; fee:update - POST /api/v1/fees/payments/:paymentId/refund — Refund a collected payment (full or partial); fee:manage - POST /api/v1/fees/invoices/:id/write-off — Forgive outstanding balance; fee:manage - POST /api/v1/fees/invoices/:id/discount — Apply a concession/scholarship discount; fee:manage - POST /api/v1/fees/invoices/:id/cancel — Void an invoice raised in error; fee:manage - POST /api/v1/fees/adjustments/:id/reverse — Undo a discount / write-off / cancellation; fee:manage - GET /api/v1/fees/invoices/:id/adjustments — Invoice Adjustments; fee:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Operational forecasts Run and inspect the available operational forecast records. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-forecasts/ Guided sample demo: https://avkul.in/docs/demo/screen-school-forecasts/ Snapshot: 11 October 2026 ## Features - Forecast selection - Latest run - History and result ## Access and 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. Permission keys: inventory:view ## Workflow 1. Select the available forecast and context. 2. Review provider and data readiness. 3. Run and compare the returned result with actual records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/forecasts ## API reference - POST /api/v1/ai-features/hostel-inventory-forecast/:id/draft-po — Draft Po From Forecast; inventory:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Campus gate passes Use campus gate passes in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit. Category: School office Guide: https://avkul.in/docs/guides/screen-school-gate-pass/ Guided sample demo: https://avkul.in/docs/demo/screen-school-gate-pass/ Snapshot: 11 October 2026 ## Features - Early-release requests - Decision and reason - Authorised pickup - Campus release - Return and cancel - Currently-out register ## Access and 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. Permission keys: student:view, student:update, student:manage, student:create ## Workflow 1. Choose the student and request reason. 2. Review the pickup person and decide the request. 3. Record authorised release at the gate. 4. Record return or inspect the currently-out register. ## Fields and controls - studentId (string, declared required) - reason (string, optional) - expectedOutAt (string, optional) - expectedBackAt (string, optional) - releaseToName (string, optional) - releaseToGuardianId (string, optional) - approve (boolean, declared required) - guardianId (string, optional) - releaseRelation (string, optional) - overrideReason (string, optional) - notes (string, optional) - firstName (string, declared required) - middleName (string, optional) - lastName (string, optional) - admissionNo (string, declared required) - rollNo (string, optional) - gender (string, optional) - dateOfBirth (string, optional) - bloodGroup (string, optional) - sessionId (string, optional) - classId (string, optional) - sectionId (string, optional) - admissionDate (string, optional) - phone (string, optional) ## Current limits - Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record. ## Actual application access - https://avkul.in/en/school/gate-pass ## API reference - GET /api/v1/gate-pass — List; student:view - GET /api/v1/gate-pass/currently-out — Students currently signed out of campus; student:view - GET /api/v1/gate-pass/student/:studentId/pickups — Who is on file to collect this student; student:view - POST /api/v1/gate-pass — Create; student:update - POST /api/v1/gate-pass/:id/decision — Approve or turn down a gate pass; student:manage - POST /api/v1/gate-pass/:id/release — Hand the student over at the gate; student:update - POST /api/v1/gate-pass/:id/return — Mark Returned; student:update - GET /api/v1/students — List; student:view - POST /api/v1/students — Create; student:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Health records & infirmary Use health records & infirmary in the school workspace. Maintain school health information and record infirmary visits, medication entries and closures. Category: Student care Guide: https://avkul.in/docs/guides/screen-school-health-records/ Guided sample demo: https://avkul.in/docs/demo/screen-school-health-records/ Snapshot: 11 October 2026 ## Features - Load - Give medicine - List - Get By Student - Upsert - List Visits - Students in the sick room unusually often - Alerts ## Access and 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. Permission keys: health:view, health:update ## Workflow 1. Find the permitted student health profile. 2. Review emergency and health information. 3. Record the infirmary visit and permitted medication details. 4. Close the visit and review repeated visits where relevant. ## Fields and controls - bloodGroup (string, optional) - allergies (string, optional) - chronicConditions (string, optional) - medications (string, optional) - emergencyContactName (string, optional) - emergencyContactPhone (string, optional) - heightCm (number, optional) - weightKg (number, optional) - lastCheckupDate (string, optional) - vaccinationJson (Record, optional) - notes (string, optional) - studentId (string, declared required) - complaint (string, declared required) - observations (string, optional) - temperatureC (number, optional) - outcome ('OPEN' | 'RETURNED_TO_CLASS' | 'RESTING' | 'SENT_HOME' | 'REFERRED_HOSPITAL', declared required) - treatment (string, optional) - medicine (string, declared required) - visitId (string, optional) - dose (string, optional) - route (string, optional) - consentSource (string, optional) ## Current limits - Access is restricted by dedicated health permissions. Sample walkthrough information is fictional and is not medical advice. ## Actual application access - https://avkul.in/en/school/health-records ## API reference - GET /api/v1/health-records — List; health:view - GET /api/v1/health-records/students/:studentId — Get By Student; health:view - PUT /api/v1/health-records/students/:studentId — Upsert; health:update - GET /api/v1/infirmary/visits — List Visits; health:view - GET /api/v1/infirmary/frequent-visitors — Students in the sick room unusually often; health:view - GET /api/v1/infirmary/students/:studentId/alerts — Alerts; health:view - POST /api/v1/infirmary/visits — Book a child into the sick room; health:update - POST /api/v1/infirmary/visits/:id/close — Close Visit; health:update - POST /api/v1/infirmary/medications — Record a dose given on school premises; health:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Hostel, rooms & roll call Use hostel, rooms & roll call in the school workspace. Manage residence capacity, room/bed allocations, visitor logs and nightly attendance. Category: Campus Guide: https://avkul.in/docs/guides/screen-school-hostel/ Guided sample demo: https://avkul.in/docs/demo/screen-school-hostel/ Snapshot: 11 October 2026 ## Features - List Hostels - Create Hostel - List Rooms - Create Room - List Beds - Create Bed ## Access and 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. Permission keys: hostel:view, hostel:create, hostel:update ## Workflow 1. Set up the hostel, rooms and beds. 2. Allocate eligible residents to available accommodation. 3. Record and check out permitted visitors. 4. Open the roll call, mark residents and close the register. ## Fields and controls - Name - Type - Capacity - Room ## Current limits - Capacity and allocation state must be reviewed before assignment. Family notification delivery depends on the available channel. ## Actual application access - https://avkul.in/en/school/hostel ## API reference - GET /api/v1/hostel/hostels — List Hostels; hostel:view - POST /api/v1/hostel/hostels — Create Hostel; hostel:create - GET /api/v1/hostel/rooms — List Rooms; hostel:view - POST /api/v1/hostel/rooms — Create Room; hostel:create - GET /api/v1/hostel/beds — List Beds; hostel:view - POST /api/v1/hostel/beds — Create Bed; hostel:create - GET /api/v1/hostel/roll-call/missing — Residents not accounted for, and hostels with no roll call at all; hostel:view - GET /api/v1/hostel/roll-call/:id — Register; hostel:view - POST /api/v1/hostel/roll-call/open — Open tonight's register for a hostel; hostel:update - POST /api/v1/hostel/roll-call/:id/mark — Mark; hostel:update - POST /api/v1/hostel/roll-call/:id/close — Close the night; families of absent residents are told; hostel:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notifications & integrations Use notifications & integrations in the school workspace. Review notifications, integration settings, webhook records and shared AI request state. Category: Administration Guide: https://avkul.in/docs/guides/screen-school-integrations/ Guided sample demo: https://avkul.in/docs/demo/screen-school-integrations/ Snapshot: 11 October 2026 ## Features - In-app notifications - Integration status - Integration configuration - Webhooks - AI requests ## Access and 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. Permission keys: settings:view, settings:create ## Workflow 1. Open the relevant integration or notification view. 2. Review status and permitted settings. 3. Configure a provider using approved credentials outside public documentation. 4. Use a controlled test and inspect the actual result. ## Fields and controls - Title ## Current limits - Saving settings is not proof of external delivery. No credential values are included in this documentation. ## Actual application access - https://avkul.in/en/school/integrations ## API reference - GET /api/v1/integrations — List Integrations; settings:view - POST /api/v1/integrations — Create Integration; settings:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Inventory & purchases Use inventory & purchases in the school workspace. Manage supplies, procurement, stock movements and issued school property. Category: Campus Guide: https://avkul.in/docs/guides/screen-school-inventory/ Guided sample demo: https://avkul.in/docs/demo/screen-school-inventory/ Snapshot: 11 October 2026 ## Features - Remove line - Add order line - Add item - Record stock movement - Add vendor - New purchase order - Issue an asset - Export this view CSV - Workspace ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Accountant, Store Keeper, Inventory Manager - A school account with the permissions shown below. - Choose the relevant school, academic session or child before working. Permission keys: inventory:view ## Workflow 1. Create an item and supplier with the relevant stock unit. 2. Prepare and submit a purchase order for review. 3. Receive accepted quantities and inspect stock movements. 4. Issue or return property and review outstanding balances. ## Fields and controls - Order item - | Ordered , received - Vendor filter ## Current limits - Purchase totals exclude tax/freight and supplier accounting. Valuation uses reference prices, not FIFO or weighted-average accounting. ## Actual application access - https://avkul.in/en/school/inventory ## API reference - GET /api/v1/inventory/workspace — Workspace; inventory:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Hostel & inventory forecast Use the hostel & inventory forecast workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-inventory-forecast/ Guided sample demo: https://avkul.in/docs/demo/screen-school-inventory-forecast/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: inventory:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - lookbackDays (number, optional) - horizonDays (number, optional) - occupancyBoostPct (number, optional) - category (string, optional) - label (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/inventory-forecast ## API reference - GET /api/v1/ai-features/hostel-inventory-forecast — List Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast — Run Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast/:id/draft-po — Draft Po From Forecast; inventory:view - GET /api/v1/ai-features/hostel-inventory-forecast/:id — Get Inventory Forecast; inventory:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Early learning gaps Use the early learning gaps workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-learning-gaps/ Guided sample demo: https://avkul.in/docs/demo/screen-school-learning-gaps/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: student:view, lms:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - sectionId (string, optional) - weeks (number, optional) - status ('ACKNOWLEDGED' | 'IN_PROGRESS' | 'RESOLVED' | 'DISMISSED' | 'OPEN', declared required) - note (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/learning-gaps ## API reference - GET /api/v1/ai-features/learning-gaps — List Learning Gaps; student:view - POST /api/v1/ai-features/learning-gaps/scan — Run Learning Gap Scan; student:view - PATCH /api/v1/ai-features/learning-gaps/alerts/:alertId — Update Learning Gap Alert; student:view - POST /api/v1/ai-features/learning-gaps/alerts/:alertId/learning-path — Learning Path From Gap; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # General ledger Use general ledger in the school workspace. Maintain account records and post balanced double-entry journals with auditable reversals. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-ledger/ Guided sample demo: https://avkul.in/docs/demo/screen-school-ledger/ Snapshot: 11 October 2026 ## Features - Create a standard chart - Add line - Reverse - List Accounts - Create Account - Create a standard chart of accounts, skipping what exists - List Journals - Post a balanced double-entry transaction - Post the mirror image; the original stays on the record ## Access and 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. Permission keys: fee:view, fee:manage ## Workflow 1. Review or seed the chart of accounts. 2. Prepare matching debit and credit lines. 3. Post the balanced journal and inspect its record. 4. Use a reversal to correct an entry without erasing the original. ## Fields and controls - name (string, declared required) - code (string, optional) - type (string, declared required) - parentId (string, optional) - isPostable (boolean, optional) - lines (JournalLineDto[], declared required) - entryDate (string, optional) - narration (string, optional) - source (string, optional) - sourceRef (string, optional) ## Current limits - Debits and credits must balance. Ledger recording is not a bank settlement or a statutory filing. ## Actual application access - https://avkul.in/en/school/ledger ## API reference - GET /api/v1/ledger/accounts — List Accounts; fee:view - POST /api/v1/ledger/accounts — Create Account; fee:manage - POST /api/v1/ledger/accounts/seed-defaults — Create a standard chart of accounts, skipping what exists; fee:manage - GET /api/v1/ledger/journals — List Journals; fee:view - POST /api/v1/ledger/journals — Post a balanced double-entry transaction; fee:manage - POST /api/v1/ledger/journals/:id/reverse — Post the mirror image; the original stays on the record; fee:manage - GET /api/v1/ledger/trial-balance — Every account with its debit/credit totals; fee:view - GET /api/v1/ledger/income-statement — Income, expenditure and surplus for a period; fee:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # AI lesson planner Use the ai lesson planner workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-lesson-planner/ Guided sample demo: https://avkul.in/docs/demo/screen-school-lesson-planner/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: timetable:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - classId (string, declared required) - subjectId (string, declared required) - topic (string, optional) - weekOf (string, optional) - sectionId (string, optional) - regenerate (boolean, optional) - objectives (string[], optional) - activities (string[], optional) - worksheet (string, optional) - exitTicket (string, optional) - notes (string, optional) - homework (string, optional) - assessmentTip (string, optional) - summary (string, optional) - status ('DRAFT' | 'PUBLISHED' | 'ARCHIVED', declared required) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/lesson-planner ## API reference - GET /api/v1/ai-features/lesson-planner — List Lesson Plans; timetable:view - POST /api/v1/ai-features/lesson-planner — Generate Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/days/:dayId — Update Lesson Plan Day; timetable:view - GET /api/v1/ai-features/lesson-planner/:planId — Get Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId — Update Lesson Plan Meta; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId/status — Set Lesson Plan Status; timetable:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Library & circulation Use library & circulation in the school workspace. Maintain titles and copies, lend books, manage reservations and handle fines. Category: Campus Guide: https://avkul.in/docs/guides/screen-school-library/ Guided sample demo: https://avkul.in/docs/demo/screen-school-library/ Snapshot: 11 October 2026 ## Features - Add book - Add copy - Issue a book - Reserve a title - Edit policy - Edit book - Archive book - Edit copy - Workspace ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Librarian - A school account with the permissions shown below. - Choose the relevant school, academic session or child before working. Permission keys: library:view ## Workflow 1. Create a title and its physical copies. 2. Check borrower eligibility and issue an available copy. 3. Return or renew the loan and review reservations. 4. Review overdue items and any permitted fine action. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Availability, borrower policy and reservation rules affect issue/renewal. A fine record is distinct from a fee gateway payment. ## Actual application access - https://avkul.in/en/school/library ## API reference - GET /api/v1/library/workspace — Workspace; library:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Live classes & recordings Use live classes & recordings in the school workspace. Schedule live lessons, manage their lifecycle and maintain recordings where configured. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-live-classes/ Guided sample demo: https://avkul.in/docs/demo/screen-school-live-classes/ Snapshot: 11 October 2026 ## Features - List - Create - Cancel ## Access and 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. Permission keys: live-class:view, live-class:create, live-class:update ## Workflow 1. Create the class for the intended learners. 2. Review the scheduled time and class details. 3. Start the class and use the available joining experience. 4. End the session and review an available recording. ## Fields and controls - title (string, declared required) - classId (string, declared required) - sectionId (string, optional) - subjectId (string, optional) - scheduledAt (string, declared required) - durationMin (number, optional) ## Current limits - Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity. ## Actual application access - https://avkul.in/en/school/live-classes ## API reference - GET /api/v1/live-classes — List; live-class:view - POST /api/v1/live-classes — Create; live-class:create - POST /api/v1/live-classes/:id/cancel — Cancel; live-class:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Live-class workspace Use live-class workspace in the school workspace. Schedule live lessons, manage their lifecycle and maintain recordings where configured. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-live-classes-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-live-classes-id-detail/ Snapshot: 11 October 2026 ## Features - Get - Update - Remove - Start - End - Finalize Recording ## Access and 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. Permission keys: live-class:view, live-class:update, live-class:delete ## Workflow 1. Create the class for the intended learners. 2. Review the scheduled time and class details. 3. Start the class and use the available joining experience. 4. End the session and review an available recording. ## Fields and controls - title (string, optional) - scheduledAt (string, optional) - durationMin (number, optional) ## Current limits - Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity. ## Actual application access - https://avkul.in/en/school/live-classes — select the actual record from this list. ## API reference - GET /api/v1/live-classes/:id — Get; live-class:view - PATCH /api/v1/live-classes/:id — Update; live-class:update - DELETE /api/v1/live-classes/:id — Remove; live-class:delete - POST /api/v1/live-classes/:id/start — Start; live-class:update - POST /api/v1/live-classes/:id/end — End; live-class:update - POST /api/v1/live-classes/:id/recording/finalize — Finalize Recording; live-class:update - POST /api/v1/live-classes/:id/recording/recover — Recover Recording; live-class:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Courses & lessons Use courses & lessons in the school workspace. Build a course structure and let learners open lessons and record progress. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-lms/ Guided sample demo: https://avkul.in/docs/demo/screen-school-lms/ Snapshot: 11 October 2026 ## Features - Course catalogue - Modules - Lessons - Video assets - Publishing - Learner progress ## Access and 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. Permission keys: lms:view, lms:create ## Workflow 1. Create a course and its details. 2. Add modules and lessons in the intended order. 3. Attach supported learning media and review visibility. 4. Open the learner course view and track lesson progress. ## Fields and controls - Course title - Description ## Current limits - A course must be available to the learner before it appears in self-service. Video delivery depends on the stored asset and browser support. ## Actual application access - https://avkul.in/en/school/lms ## API reference - GET /api/v1/lms/courses — List Courses; lms:view - POST /api/v1/lms/courses — Create Course; lms:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Course modules & lesson editor Use course modules & lesson editor in the school workspace. Build a course structure and let learners open lessons and record progress. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-lms-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-lms-id-detail/ Snapshot: 11 October 2026 ## Features - Add module - Add lesson - Get Course - Update Course - Remove Course - Add Module - Remove Module - Add Lesson ## Access and 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. Permission keys: lms:view, lms:update, lms:delete ## Workflow 1. Create a course and its details. 2. Add modules and lessons in the intended order. 3. Attach supported learning media and review visibility. 4. Open the learner course view and track lesson progress. ## Fields and controls - isPublished (boolean, optional) - title (string, declared required) - sortOrder (number, optional) - contentType (string, declared required) - videoUrl (string, optional) - body (string, optional) - durationMin (number, optional) ## Current limits - A course must be available to the learner before it appears in self-service. Video delivery depends on the stored asset and browser support. ## Actual application access - https://avkul.in/en/school/lms — select the actual record from this list. ## API reference - GET /api/v1/lms/courses/:id — Get Course; lms:view - PATCH /api/v1/lms/courses/:id — Update Course; lms:update - DELETE /api/v1/lms/courses/:id — Remove Course; lms:delete - POST /api/v1/lms/courses/:id/modules — Add Module; lms:update - DELETE /api/v1/lms/modules/:id — Remove Module; lms:update - POST /api/v1/lms/modules/:id/lessons — Add Lesson; lms:update - DELETE /api/v1/lms/lessons/:id — Remove Lesson; lms:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Mark rechecks Use mark rechecks in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-mark-rechecks/ Guided sample demo: https://avkul.in/docs/demo/screen-school-mark-rechecks/ Snapshot: 11 October 2026 ## Features - Published-mark query - Review acknowledgement - Uphold/revise/reject decision ## Access and 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. Permission keys: exam:view, exam:manage ## Workflow 1. Locate the published mark query. 2. Acknowledge review of the paper. 3. Record the permitted decision and review its result. ## Fields and controls - examScheduleId (string, declared required) - studentId (string, declared required) - reason (string, declared required) - outcome ('UPHELD' | 'REVISED' | 'REJECTED', declared required) - revisedMarks (number, optional) - notes (string, optional) ## Current limits - Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows. ## Actual application access - https://avkul.in/en/school/mark-rechecks ## API reference - GET /api/v1/mark-rechecks — List; exam:view - POST /api/v1/mark-rechecks — Query a published mark; Authenticated scope - POST /api/v1/mark-rechecks/:id/review — Acknowledge that the paper is being re-read; exam:manage - POST /api/v1/mark-rechecks/:id/decision — Uphold, revise or reject a recheck; exam:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Notices, announcements & messages Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations. Category: Community Guide: https://avkul.in/docs/guides/screen-school-messages/ Guided sample demo: https://avkul.in/docs/demo/screen-school-messages/ Snapshot: 11 October 2026 ## Features - New - withdraw - Addressable contacts for the signed-in user - My conversations, most recent first - Get Thread - Start a conversation (or add to the existing one) - Send - Mark Read ## Access and 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. ## Workflow 1. Choose the notice, announcement or conversation workflow. 2. Select the permitted audience and prepare the content. 3. Preview reachability before sending where available. 4. Review delivery reports, replies or complaint status. ## Fields and controls - toUserId (string, declared required) - body (string, declared required) - subject (string, optional) - studentId (string, optional) - muted (boolean, declared required) ## Current limits - External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it. ## Actual application access - https://avkul.in/en/school/messages ## API reference - GET /api/v1/messages/contacts — Addressable contacts for the signed-in user; Authenticated scope - GET /api/v1/messages — My conversations, most recent first; Authenticated scope - GET /api/v1/messages/:id — Get Thread; Authenticated scope - POST /api/v1/messages — Start a conversation (or add to the existing one); Authenticated scope - POST /api/v1/messages/:id/messages — Send; Authenticated scope - POST /api/v1/messages/:id/read — Mark Read; Authenticated scope - POST /api/v1/messages/:id/mute — Mute; Authenticated scope - DELETE /api/v1/messages/messages/:messageId — Withdraw your own message; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Multilingual explanations Use the multilingual explanations workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-multilingual-explain/ Guided sample demo: https://avkul.in/docs/demo/screen-school-multilingual-explain/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: lms:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - concept (string, optional) - level (string, optional) - languages (string[], optional) - subjectId (string | null, optional) - classId (string | null, optional) - audience ('STUDENT' | 'PARENT' | 'BOTH', optional) - publish (boolean, optional) - title (string, optional) - body (string, optional) - parentTip (string, optional) - status ('DRAFT' | 'PUBLISHED' | 'PRIVATE' | 'ARCHIVED', declared required) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/multilingual-explain ## API reference - GET /api/v1/ai-features/multilingual-explain — List Multilingual Explain; lms:view - POST /api/v1/ai-features/multilingual-explain — Generate Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/langs/:langId — Update Multilingual Explain Lang; lms:view - GET /api/v1/ai-features/multilingual-explain/:id — Get Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id — Update Multilingual Explain Meta; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id/status — Set Multilingual Explain Status; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My department team Use my department team in the school workspace. Let families, learners and staff see only their linked children or personal records. Category: Family portal Guide: https://avkul.in/docs/guides/screen-school-my-department/ Guided sample demo: https://avkul.in/docs/demo/screen-school-my-department/ Snapshot: 11 October 2026 ## Features - Linked children - Attendance and fees - Published results - Homework and courses - Timetable - Library - PTM - Transport - Personal documents ## Access and 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. ## Workflow 1. Sign in with the assigned department context. 2. Review your department and team. 3. Use the displayed information within your own scope. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/school/my-department ## API reference - GET /api/v1/me/department-team — Department Team; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # My payslips Use my payslips in the school workspace. Let families, learners and staff see only their linked children or personal records. Category: Family portal Guide: https://avkul.in/docs/guides/screen-school-my-payslips/ Guided sample demo: https://avkul.in/docs/demo/screen-school-my-payslips/ Snapshot: 11 October 2026 ## Features - Own salary slips - Period selection - Slip detail ## Access and 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. ## Workflow 1. Sign in with a linked staff account. 2. Select a salary slip for the intended period. 3. Review your own available salary breakdown. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls. ## Actual application access - https://avkul.in/en/school/my-payslips ## API reference - GET /api/v1/me/payslips — The signed-in staff member's own payslips; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School dashboard Use school dashboard in the school workspace. See school-wide priorities and manage the campus context used by the ERP. Category: School office Guide: https://avkul.in/docs/guides/screen-school/ Guided sample demo: https://avkul.in/docs/demo/screen-school/ Snapshot: 11 October 2026 ## Features - School Admin dashboard KPIs (today + footprint) - Daily Action Center: everything pending today, scoped to the caller - Current school, branches and active session ## Access and 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. Permission keys: dashboard:view ## Workflow 1. Review the school dashboard and current session. 2. Open an outstanding action in the relevant module. 3. Inspect the campus counts and permitted branch settings. 4. Review the consequences before closing a campus. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow. ## Actual application access - https://avkul.in/en/school ## API reference - GET /api/v1/school/overview — School Admin dashboard KPIs (today + footprint); dashboard:view - GET /api/v1/school/action-center — Daily Action Center: everything pending today, scoped to the caller; dashboard:view - GET /api/v1/school/profile — Current school, branches and active session; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Online payments & reconciliation Use online payments & reconciliation in the school workspace. Create gateway orders, verify callbacks and investigate payments that remain pending. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-payments/ Guided sample demo: https://avkul.in/docs/demo/screen-school-payments/ Snapshot: 11 October 2026 ## Features - Payment orders - Callback verification - Pending payment review - Reconciliation - Gateway connection check ## Access and 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. Permission keys: fee:view, fee:create ## Workflow 1. Review the invoice and provider readiness. 2. Create an order through the permitted checkout workflow. 3. Verify the gateway response before treating the invoice as paid. 4. Investigate a pending payment through reconciliation. ## Fields and controls - Invoice ID - Amount (blank = full balance) ## Current limits - External collection requires approved gateway credentials and verified callbacks. The public guided demo does not charge money. ## Actual application access - https://avkul.in/en/school/payments ## API reference - GET /api/v1/payments/orders — List Orders; fee:view - POST /api/v1/payments/orders — Create Order; fee:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Payroll & salary structures Use payroll & salary structures in the school workspace. Prepare salary structures, process payroll, review approvals and maintain salary slips. Category: People Guide: https://avkul.in/docs/guides/screen-school-payroll/ Guided sample demo: https://avkul.in/docs/demo/screen-school-payroll/ Snapshot: 11 October 2026 ## Features - Salary structures - Payroll processing - Approval - Mark paid - Salary slips - PDF generation ## Access and 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. Permission keys: payroll:manage ## Workflow 1. Create the applicable salary structure. 2. Process payroll for the selected period. 3. Review calculations and approve the run. 4. Record payment status and review salary slips. ## Fields and controls - Name ## Current limits - Marking payroll paid records an administrative state; this feature does not by itself transfer money to a bank. ## Actual application access - https://avkul.in/en/school/payroll ## API reference - POST /api/v1/hr/payrolls/process — Process Payroll; payroll:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School plan & usage Review your school’s plan, module access and quota usage. Category: Platform Guide: https://avkul.in/docs/guides/screen-school-plan/ Guided sample demo: https://avkul.in/docs/demo/screen-school-plan/ Snapshot: 11 October 2026 ## Features - Current plan - Usage limits - Enabled modules ## Access and 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. ## Workflow 1. Open the school plan view. 2. Review current quota consumption. 3. Contact the platform administrator for a plan change when needed. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers. ## Actual application access - https://avkul.in/en/school/plan ## API reference - GET /api/v1/my-plan/usage — This tenant's usage against its own plan; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Year-end rollover Use year-end rollover in the school workspace. Preview new-session student placement and apply or revert a recorded promotion batch. Category: School office Guide: https://avkul.in/docs/guides/screen-school-promotion/ Guided sample demo: https://avkul.in/docs/demo/screen-school-promotion/ Snapshot: 11 October 2026 ## Features - Copy classes & sections across - Undo - Dry-run a rollover — writes nothing - Copy classes/sections/subjects into the new session - Apply the rollover (transactional) - Revert - Batches ## Access and 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. Permission keys: promotion:view, promotion:create, promotion:manage, promotion:delete ## Workflow 1. Choose the source and target academic sessions. 2. Clone or prepare the target class structure. 3. Review the dry-run placement and exceptions. 4. Commit only the reviewed batch and keep its reversal reference. ## Fields and controls - From (closing) - To (new year) - Min attendance % - Min average % - Hold students with dues ## Current limits - Preview writes nothing; commit changes enrollment. Locked sessions and school ownership checks still apply. ## Actual application access - https://avkul.in/en/school/promotion ## API reference - POST /api/v1/promotions/preview — Dry-run a rollover — writes nothing; promotion:view - POST /api/v1/promotions/clone-structure — Copy classes/sections/subjects into the new session; promotion:create - POST /api/v1/promotions/commit — Apply the rollover (transactional); promotion:manage - POST /api/v1/promotions/batches/:id/revert — Revert; promotion:delete - GET /api/v1/promotions/batches — Batches; promotion:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Parent–teacher meetings Use parent–teacher meetings in the school workspace. Publish meeting slots, book families, record discussion outcomes and manage follow-up tasks. Category: Community Guide: https://avkul.in/docs/guides/screen-school-ptm/ Guided sample demo: https://avkul.in/docs/demo/screen-school-ptm/ Snapshot: 11 October 2026 ## Features - Save meeting notes - Mark - Reschedule meeting - Add follow-up - New meeting slot - Save meeting slot - Edit slot - Book family - Read ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Teacher - A school account with the permissions shown below. - Choose the relevant school, academic session or child before working. Permission keys: communication:view ## Workflow 1. Create or choose the permitted teacher meeting slot. 2. Book the linked child and verify availability. 3. Record the meeting outcome with the correct note visibility. 4. Assign and complete any follow-up action. ## Fields and controls - Private staff notes - Feedback shared with family - Outcome / cancellation reason - Move to another slot - Follow-up title - Task owner - Follow-up due date - Meeting month - Meeting teacher - Slot teacher - Student - Booking student ## Current limits - Private staff notes and family-visible notes differ. Reminder actions do not guarantee external SMS, email or push delivery. ## Actual application access - https://avkul.in/en/school/ptm ## API reference - GET /api/v1/ptm/workspace — Read; communication:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School reports Use school reports in the school workspace. Review fee summaries, student distribution and examination summaries from permitted school data. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-reports/ Guided sample demo: https://avkul.in/docs/demo/screen-school-reports/ Snapshot: 11 October 2026 ## Features - Exam Summary - Fee Summary - Students By Class ## Access and 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. Permission keys: report:view ## Workflow 1. Choose the report and reporting context. 2. Inspect the totals and available filters. 3. Compare the summary with the underlying records. 4. Use the available export or print action when present. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - A summary is only as current as the entered records. Each report uses its implemented date and scope rules. ## Actual application access - https://avkul.in/en/school/reports ## API reference - GET /api/v1/reports/exam-summary — Exam Summary; report:view - GET /api/v1/reports/fee-summary — Fee Summary; report:view - GET /api/v1/reports/students-by-class — Students By Class; report:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Roles & permissions Use roles & permissions in the school workspace. Control which school users can view, create, edit, export and manage records. Category: Administration Guide: https://avkul.in/docs/guides/screen-school-settings-roles/ Guided sample demo: https://avkul.in/docs/demo/screen-school-settings-roles/ Snapshot: 11 October 2026 ## Features - Role catalogue - Permission catalogue - Role grants - User assignment ## Access and 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. Permission keys: role:view, role:create ## Workflow 1. Open a role and inspect its existing permissions. 2. Choose only the required permission keys. 3. Save the role and assign eligible users. 4. Sign in as the affected role to review access. ## Fields and controls - name (string, declared required) - key (string, declared required) - description (string, optional) ## Current limits - A role name alone does not grant platform administration. School scope and explicit guards still apply. ## Actual application access - https://avkul.in/en/school/settings/roles ## API reference - GET /api/v1/access-control/roles — List; role:view - POST /api/v1/access-control/roles — Create; role:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Role permissions & user assignments Use role permissions & user assignments in the school workspace. Control which school users can view, create, edit, export and manage records. Category: Administration Guide: https://avkul.in/docs/guides/screen-school-settings-roles-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-settings-roles-id-detail/ Snapshot: 11 October 2026 ## Features - Permission Catalog - Get - Update - Remove - Set Permissions - Assignable Users ## Access and 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. Permission keys: role:view, role:update, role:delete, role:manage ## Workflow 1. Open a role and inspect its existing permissions. 2. Choose only the required permission keys. 3. Save the role and assign eligible users. 4. Sign in as the affected role to review access. ## Fields and controls - name (string, optional) - description (string, optional) - permissionKeys (string[], declared required) - userId (string, declared required) ## Current limits - A role name alone does not grant platform administration. School scope and explicit guards still apply. ## Actual application access - https://avkul.in/en/school/settings/roles — select the actual record from this list. ## API reference - GET /api/v1/access-control/permissions — Permission Catalog; role:view - GET /api/v1/access-control/roles/:id — Get; role:view - PATCH /api/v1/access-control/roles/:id — Update; role:update - DELETE /api/v1/access-control/roles/:id — Remove; role:delete - PUT /api/v1/access-control/roles/:id/permissions — Set Permissions; role:manage - GET /api/v1/access-control/roles/:id/assignable-users — Assignable Users; role:manage - POST /api/v1/access-control/roles/:id/users — Assign User; role:manage - DELETE /api/v1/access-control/roles/:id/users/:userId — Unassign User; role:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff directory & lifecycle Use staff directory & lifecycle in the school workspace. Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement. Category: People Guide: https://avkul.in/docs/guides/screen-school-staff/ Guided sample demo: https://avkul.in/docs/demo/screen-school-staff/ Snapshot: 11 October 2026 ## Features - Offboard - Reinstate - Download Template - Export to Excel - List - List Former - Add a staff member - What still depends on this person - Mark a staff member as having left ## Access and 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. Permission keys: hr:view, hr:create, hr:manage ## Workflow 1. Find or create the staff profile. 2. Review employment details and linked responsibilities. 3. Inspect clearance before offboarding. 4. Use reinstatement when returning a former staff member. ## Fields and controls - employeeCode (string, declared required) - firstName (string, declared required) - lastName (string, optional) - gender (string, optional) - dateOfBirth (string, optional) - email (string, optional) - phone (string, optional) - branchId (string, optional) - departmentId (string, optional) - designationId (string, optional) - reportsToId (string, optional) - joiningDate (string, optional) - contractType (string, optional) - qualifications (unknown, optional) - exitStatus ('RESIGNED' | 'TERMINATED' | 'RETIRED', optional) - exitDate (string, optional) - reason (string, optional) - force (boolean, optional) ## Current limits - Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action. ## Actual application access - https://avkul.in/en/school/staff ## API reference - GET /api/v1/staff — List; hr:view - GET /api/v1/staff/former — List Former; hr:view - POST /api/v1/staff — Add a staff member; hr:create - GET /api/v1/staff/:id/clearance — What still depends on this person; hr:view - POST /api/v1/staff/:id/offboard — Mark a staff member as having left; hr:manage - POST /api/v1/staff/:id/reinstate — Reinstate; hr:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff profile & clearance Use staff profile & clearance in the school workspace. Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement. Category: People Guide: https://avkul.in/docs/guides/screen-school-staff-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-staff-id-detail/ Snapshot: 11 October 2026 ## Features - Directory - Staff creation - Profile 360 - Clearance - Offboarding - Reinstatement ## Access and 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. Permission keys: hr:view ## Workflow 1. Find or create the staff profile. 2. Review employment details and linked responsibilities. 3. Inspect clearance before offboarding. 4. Use reinstatement when returning a former staff member. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action. ## Actual application access - https://avkul.in/en/school/staff — select the actual record from this list. ## API reference - GET /api/v1/staff/:id/profile-360 — Get Profile360; hr:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff attendance Use staff attendance in the school workspace. Record staff check-in/out and maintain an administrative daily and monthly register. Category: People Guide: https://avkul.in/docs/guides/screen-school-staff-attendance/ Guided sample demo: https://avkul.in/docs/demo/screen-school-staff-attendance/ Snapshot: 11 October 2026 ## Features - Check in - Check out - Mark all present - The caller's own attendance history and check-in state - All staff with their status for a date - Mark/correct staff attendance for a date ## Access and 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. Permission keys: hr:view, hr:update ## Workflow 1. Check the current personal attendance state. 2. Clock in or out through the self-service action. 3. Use the authorized daily roster to correct records. 4. Review the monthly register and holiday policy. ## Fields and controls - Date ## Current limits - Self-service acts on the caller’s staff profile. Administrative corrections need separate access. ## Actual application access - https://avkul.in/en/school/staff-attendance ## API reference - GET /api/v1/staff-attendance/me — The caller's own attendance history and check-in state; Authenticated scope - GET /api/v1/staff-attendance/roster — All staff with their status for a date; hr:view - POST /api/v1/staff-attendance/mark — Mark/correct staff attendance for a date; hr:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff leave requests Use staff leave requests in the school workspace. Keep staff leave requests and student absence reports in their respective review workflows. Category: People Guide: https://avkul.in/docs/guides/screen-school-staff-leave/ Guided sample demo: https://avkul.in/docs/demo/screen-school-staff-leave/ Snapshot: 11 October 2026 ## Features - Approve - Decline - Self-service: apply for leave (resolves the caller's own staff profile) - Self-service: my own leave history - Admin: pending leave requests awaiting a decision - Admin: approve or reject a leave request ## Access and 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. Permission keys: hr:view, hr:update ## Workflow 1. Choose staff leave or student absence reporting. 2. Enter the applicable dates and reason. 3. Submit or review through the permitted role. 4. Check the final decision and attendance impact. ## Fields and controls - Book the suggested stand-ins, not just plan them ## Current limits - Staff and student approval rules differ. The family view resolves linked-child ownership. ## Actual application access - https://avkul.in/en/school/staff-leave ## API reference - POST /api/v1/leave/apply — Self-service: apply for leave (resolves the caller's own staff profile); Authenticated scope - GET /api/v1/leave/mine — Self-service: my own leave history; Authenticated scope - 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 ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff workload Use the staff workload workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-staff-workload/ Guided sample demo: https://avkul.in/docs/demo/screen-school-staff-workload/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: timetable:view, attendance:update ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - overloadThreshold (number, optional) - mediumThreshold (number, optional) - underutilizedRatio (number, optional) - label (string, optional) - absentStaffId (string, declared required) - date (string, optional) - apply (boolean, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/staff-workload ## API reference - GET /api/v1/ai-features/staff-workload — List Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload — Run Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload/substitutions — Suggest Substitutions; timetable:view, attendance:update - GET /api/v1/ai-features/staff-workload/:id — Get Staff Workload; timetable:view, attendance:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student exit & transfer certificates Use student exit & transfer certificates in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit. Category: School office Guide: https://avkul.in/docs/guides/screen-school-student-exit/ Guided sample demo: https://avkul.in/docs/demo/screen-school-student-exit/ Snapshot: 11 October 2026 ## Features - Clearance review - Outstanding dependency checks - Exit register - Transfer-certificate number - TC generation - Readmission ## Access and 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. Permission keys: student:view, student:create, student-exit:view, student-exit:create, student-exit:manage ## Workflow 1. Locate the student and review clearance. 2. Resolve blockers before recording the exit. 3. Review the allocated TC number and generate the permitted document. 4. Use readmission only for an approved reversal. ## Fields and controls - firstName (string, declared required) - middleName (string, optional) - lastName (string, optional) - admissionNo (string, declared required) - rollNo (string, optional) - gender (string, optional) - dateOfBirth (string, optional) - bloodGroup (string, optional) - sessionId (string, optional) - classId (string, optional) - sectionId (string, optional) - admissionDate (string, optional) - phone (string, optional) - email (string, optional) - status (string, declared required) - exitDate (string, optional) - reason (string, optional) - remark (string, optional) - issueTc (boolean, optional) - force (boolean, optional) ## Current limits - Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record. ## Actual application access - https://avkul.in/en/school/student-exit ## API reference - GET /api/v1/students — List; student:view - POST /api/v1/students — Create; student:create - GET /api/v1/students/exit/register — Students who have left, with TC numbers; student-exit:view - GET /api/v1/students/:id/clearance — What is blocking this student from leaving; student-exit:view - POST /api/v1/students/:id/exit — Take a student off the rolls and allocate a TC number; student-exit:create - POST /api/v1/students/:id/readmit — Reverse an exit and put the student back on the rolls; student-exit:manage - POST /api/v1/students/:id/transfer-certificate — Generate the TC document for an exited student; student-exit:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student absence review Use student absence review in the school workspace. Keep staff leave requests and student absence reports in their respective review workflows. Category: People Guide: https://avkul.in/docs/guides/screen-school-student-leave/ Guided sample demo: https://avkul.in/docs/demo/screen-school-student-leave/ Snapshot: 11 October 2026 ## Features - Approve - Decline - Withdraw - Report a planned or past absence for a student - List - Approve an absence, marking those days excused - Cancel ## Access and 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. Permission keys: attendance:view, attendance:manage ## Workflow 1. Choose staff leave or student absence reporting. 2. Enter the applicable dates and reason. 3. Submit or review through the permitted role. 4. Check the final decision and attendance impact. ## Fields and controls - studentId (string, declared required) - fromDate (string, declared required) - toDate (string, optional) - reason (string, optional) - leaveType (string, optional) - attachmentUrl (string, optional) - approve (boolean, declared required) ## Current limits - Staff and student approval rules differ. The family view resolves linked-child ownership. ## Actual application access - https://avkul.in/en/school/student-leave ## API reference - POST /api/v1/student-leave — Report a planned or past absence for a student; Authenticated scope - GET /api/v1/student-leave — List; attendance:view - PATCH /api/v1/student-leave/:id/decision — Approve an absence, marking those days excused; attendance:manage - PATCH /api/v1/student-leave/:id/cancel — Cancel; Authenticated scope ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student directory Use student directory in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit. Category: School office Guide: https://avkul.in/docs/guides/screen-school-students/ Guided sample demo: https://avkul.in/docs/demo/screen-school-students/ Snapshot: 11 October 2026 ## Features - Download Template - Export to Excel - List - Create ## Access and 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. Permission keys: student:view, student:create ## Workflow 1. Create or open the student profile. 2. Review guardian contacts and required documents. 3. Use the gate-pass workflow for an authorized early release. 4. Use clearance and exit workflows for withdrawal or transfer. ## Fields and controls - Admission No - First name - Last name - Gender - Section ## Current limits - Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record. ## Actual application access - https://avkul.in/en/school/students ## API reference - GET /api/v1/students — List; student:view - POST /api/v1/students — Create; student:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Student profile & guardians Use student profile & guardians in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit. Category: School office Guide: https://avkul.in/docs/guides/screen-school-students-id-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-school-students-id-detail/ Snapshot: 11 October 2026 ## Features - Verify - Send back - Remove - List - Upload a document for a student - Mark a document as checked against the original - Send a document back with a reason - Get Profile360 ## Access and 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. Permission keys: student:view, student:update, student:manage, student:delete ## Workflow 1. Create or open the student profile. 2. Review guardian contacts and required documents. 3. Use the gate-pass workflow for an authorized early release. 4. Use clearance and exit workflows for withdrawal or transfer. ## Fields and controls - type (string, declared required) - title (string, optional) - expiresAt (string, optional) - reason (string, declared required) ## Current limits - Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record. ## Actual application access - https://avkul.in/en/school/students — select the actual record from this list. ## API reference - GET /api/v1/student-documents/:studentId — List; student:view - POST /api/v1/student-documents/:studentId — Upload a document for a student; student:update - POST /api/v1/student-documents/verify/:id — Mark a document as checked against the original; student:manage - POST /api/v1/student-documents/reject/:id — Send a document back with a reason; student:manage - DELETE /api/v1/student-documents/:id — Remove; student:delete - GET /api/v1/students/:id/profile-360 — Get Profile360; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Teacher cover Use teacher cover in the school workspace. Build recurring class schedules and arrange dated teacher cover with clash checks. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-substitutions/ Guided sample demo: https://avkul.in/docs/demo/screen-school-substitutions/ Snapshot: 11 October 2026 ## Features - Assign - Withdraw - A day's timetable with substitutions applied - List Substitutions - Who could cover an absent teacher (suggestions only) - Record cover for all of an absent teacher's periods on a date - Assign one substitute to one period on one date - Remove Substitution ## Access and 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. Permission keys: timetable:view, timetable:create, timetable:delete ## Workflow 1. Select the section, teacher and date. 2. Create a period with its subject, time and room. 3. Resolve overlap warnings before saving. 4. Arrange dated cover and review the daily plan. ## Fields and controls - absentStaffId (string, declared required) - date (string, declared required) - apply (boolean, optional) - reason (string, optional) - autoGenerated (boolean, optional) - periodId (string, declared required) - substituteStaffId (string, declared required) ## Current limits - Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view. ## Actual application access - https://avkul.in/en/school/substitutions ## API reference - GET /api/v1/timetable/day-plan — A day's timetable with substitutions applied; timetable:view - GET /api/v1/timetable/substitutions — List Substitutions; timetable:view - POST /api/v1/timetable/substitutions/suggest — Who could cover an absent teacher (suggestions only); timetable:view - POST /api/v1/timetable/substitutions/generate — Record cover for all of an absent teacher's periods on a date; timetable:create - POST /api/v1/timetable/substitutions — Assign one substitute to one period on one date; timetable:create - DELETE /api/v1/timetable/substitutions/:id — Remove Substitution; timetable:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tally export Use tally export in the school workspace. Prepare accounting vouchers for the configured Tally integration. Category: Finance Guide: https://avkul.in/docs/guides/screen-school-tally/ Guided sample demo: https://avkul.in/docs/demo/screen-school-tally/ Snapshot: 11 October 2026 ## Features - Download XML - Test Connection - Export Vouchers ## Access and 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. Permission keys: settings:view, fee:export ## Workflow 1. Review the accounting data and integration settings. 2. Check the configured connection in a controlled environment. 3. Export the selected voucher records. 4. Reconcile the receiving system with the exported result. ## Fields and controls - From Date - To Date ## Current limits - An export endpoint does not prove that a live Tally instance is connected or that vouchers were imported successfully. ## Actual application access - https://avkul.in/en/school/tally ## API reference - GET /api/v1/tally/test-connection — Test Connection; settings:view - POST /api/v1/tally/export-vouchers — Export Vouchers; fee:export ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Staff tasks Use staff tasks in the school workspace. Assign work to school staff and let each user complete their own task list. Category: People Guide: https://avkul.in/docs/guides/screen-school-tasks/ Guided sample demo: https://avkul.in/docs/demo/screen-school-tasks/ Snapshot: 11 October 2026 ## Features - Mark done - List - Create ## Access and 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. Permission keys: hr:view, hr:create ## Workflow 1. Create a task with the intended staff assignment. 2. Review its due date and current state. 3. The assigned user opens their own task queue. 4. Complete the task and review the updated record. ## Fields and controls - title (string, declared required) - description (string, optional) - assignedToId (string, declared required) - dueDate (string, optional) - priority (string, optional) - category (string, optional) - checklist (ChecklistItemDto[], optional) ## Current limits - School staff tasks are separate from the platform marketing Demo & Follow-up Workspace. ## Actual application access - https://avkul.in/en/school/tasks ## API reference - GET /api/v1/tasks — List; hr:view - POST /api/v1/tasks — Create; hr:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Timetable & teacher cover Use timetable & teacher cover in the school workspace. Build recurring class schedules and arrange dated teacher cover with clash checks. Category: Academics Guide: https://avkul.in/docs/guides/screen-school-timetable/ Guided sample demo: https://avkul.in/docs/demo/screen-school-timetable/ Snapshot: 11 October 2026 ## Features - Add period - Save period - Save cover - Edit period - Delete period - period - Daily schedule - Weekly timetable - Read ## Access and 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. Permission keys: timetable:view ## Workflow 1. Select the section, teacher and date. 2. Create a period with its subject, time and room. 3. Resolve overlap warnings before saving. 4. Arrange dated cover and review the daily plan. ## Fields and controls - Schedule date - Class / section - Teacher view - Period section - Weekday - Period number - Subject - Period teacher - Period type - Substitute teacher - Cover reason - Cover status ## Current limits - Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view. ## Actual application access - https://avkul.in/en/school/timetable ## API reference - GET /api/v1/timetable/workspace — Read; timetable:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Transport operations Use transport operations in the school workspace. Manage buses, routes, stops and student allocations, then run daily boarding registers. Category: Campus Guide: https://avkul.in/docs/guides/screen-school-transport/ Guided sample demo: https://avkul.in/docs/demo/screen-school-transport/ Snapshot: 11 October 2026 ## Features - Save - Notify families - Complete trip - Start trip - Add bus - Edit bus - Remove bus - Add route - Read - List Fuel Logs - Create Fuel Log - Fleet Locations ## Access and setup Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Transport Manager, Driver - A school account with the permissions shown below. - Choose the relevant school, academic session or child before working. Permission keys: transport:view, transport:create ## Workflow 1. Set up the bus, route and ordered stops. 2. Allocate students within the directional seat capacity. 3. Start today’s trip and record boarding/drop-off. 4. Complete the run and review family-visible updates. ## Fields and controls - Active - Correction reason - Trip closing notes - Trip date - Trip route - Trip direction - Filter route - Bus - Fill-up date - Litres - Amount - Odometer ## Current limits - Drivers see only their assigned operations. Recorded GPS points are not proof of an active device feed; no live tracking hardware is provisioned here. ## Actual application access - https://avkul.in/en/school/transport ## API reference - GET /api/v1/transport/workspace — Read; transport:view - GET /api/v1/transport/fuel-logs — List Fuel Logs; transport:view - POST /api/v1/transport/fuel-logs — Create Fuel Log; transport:create - GET /api/v1/transport/fleet/locations — Fleet Locations; transport:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Transport ETA Use the transport eta workspace to review its saved runs, context and available actions. Category: Intelligence Guide: https://avkul.in/docs/guides/screen-school-transport-eta/ Guided sample demo: https://avkul.in/docs/demo/screen-school-transport-eta/ Snapshot: 11 October 2026 ## Features - Input and context selection - Saved result review - Available history and comparisons - Human review ## Access and 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. Permission keys: transport:view ## Workflow 1. Review the input context and provider/data state. 2. Run or open the relevant saved result. 3. Inspect the available evidence and comparison. 4. Review the outcome before acting on it. ## Fields and controls - vehicleId (string, optional) - routeId (string, optional) - scope ('VEHICLE' | 'FLEET', optional) - lateThresholdMin (number, optional) - stalePingMin (number, optional) - label (string, optional) ## Current limits - The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction. ## Actual application access - https://avkul.in/en/school/transport-eta ## API reference - GET /api/v1/ai-features/transport-eta — List Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/live/:vehicleId — Live Transport Eta; transport:view - POST /api/v1/ai-features/transport-eta — Run Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/:id — Get Transport Eta; transport:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Tuition batches & demos Use tuition batches & demos in the school workspace. Manage tuition subjects, teaching batches, student enrollment and prospective demo classes. Category: Institutions Guide: https://avkul.in/docs/guides/screen-school-tuition/ Guided sample demo: https://avkul.in/docs/demo/screen-school-tuition/ Snapshot: 11 October 2026 ## Features - Create - Delete - Enrol - Book - Convert - File - Tuition center overview stats - List subjects available for batches - List students (for enrollment) - List all batches - Create a new batch - Update a batch ## Access and 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. Permission keys: student:view, student:create, student:update, student:delete ## Workflow 1. Create the subject and teaching batch. 2. Enroll the eligible student with the applicable terms. 3. Schedule and review prospective demo classes. 4. Maintain progress reports and enrollment state. ## Fields and controls - name (string, optional) - subjectId (string, declared required) - teacherStaffId (string, optional) - type (BatchType, optional) - startDate (string, declared required) - endDate (string, optional) - maxStudents (number, optional) - monthlyFee (number, optional) - schedule (string, optional) - roomNo (string, optional) - status (BatchStatus, optional) - batchId (string, declared required) - studentId (string, declared required) - enrolledAt (string, optional) - discountAmount (number, optional) - notes (string, optional) - prospectName (string, declared required) - prospectPhone (string, declared required) - prospectEmail (string, optional) - scheduledAt (string, declared required) - period (string, optional) - marksObtained (number, optional) - maxMarks (number, optional) - grade (string, optional) ## Current limits - Tuition prospect demos are distinct from the platform’s AVKUL ERP product demos. ## Actual application access - https://avkul.in/en/school/tuition ## API reference - GET /api/v1/tuition/stats — Tuition center overview stats; student:view - GET /api/v1/tuition/subjects — List subjects available for batches; student:view - GET /api/v1/tuition/students — List students (for enrollment); student:view - GET /api/v1/tuition/batches — List all batches; student:view - POST /api/v1/tuition/batches — Create a new batch; student:create - PATCH /api/v1/tuition/batches/:id — Update a batch; student:update - DELETE /api/v1/tuition/batches/:id — Delete a batch; student:delete - GET /api/v1/tuition/enrollments — List enrollments (optionally filter by batchId); student:view - POST /api/v1/tuition/enrollments — Enroll a student in a batch; student:create - GET /api/v1/tuition/demos — List demo classes (filter by status); student:view - POST /api/v1/tuition/demos — Schedule a demo class for a prospect; student:create - GET /api/v1/tuition/progress-reports — List progress reports; student:view - POST /api/v1/tuition/progress-reports — Create a progress report; student:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website CMS Use school website cms in the school workspace. Manage school themes, content pages and published website information from the ERP. Category: Websites Guide: https://avkul.in/docs/guides/screen-school-website/ Guided sample demo: https://avkul.in/docs/demo/screen-school-website/ Snapshot: 11 October 2026 ## Features - Edit Content - Activate theme - Remove - List Themes - Create Theme - Update Theme - Activate Theme - Remove Theme - List Pages ## Access and 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. Permission keys: website:view, website:create, website:update, website:delete ## Workflow 1. Review the school website theme and branding. 2. Create or edit the intended content page. 3. Preview and check the content and contact information. 4. Publish the page and review the public school URL. ## Fields and controls - Name - Title - Type ## Current limits - School website content is separate from the platform marketing Landing Page CMS. Publish controls use school ownership and permissions. ## Actual application access - https://avkul.in/en/school/website ## API reference - GET /api/v1/website/themes — List Themes; website:view - POST /api/v1/website/themes — Create Theme; website:create - PATCH /api/v1/website/themes/:id — Update Theme; website:update - POST /api/v1/website/themes/:id/activate — Activate Theme; website:update - DELETE /api/v1/website/themes/:id — Remove Theme; website:delete - GET /api/v1/website/pages — List Pages; website:view - POST /api/v1/website/pages — Create Page; website:create - PATCH /api/v1/website/pages/:id — Update Page; website:update - POST /api/v1/website/pages/:id/publish — Publish Page; website:update - DELETE /api/v1/website/pages/:id — Remove Page; website:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Approval workflows Use approval workflows in the school workspace. Configure approval chains and let the responsible approver act on the current step. Category: People Guide: https://avkul.in/docs/guides/screen-school-workflows/ Guided sample demo: https://avkul.in/docs/demo/screen-school-workflows/ Snapshot: 11 October 2026 ## Features - Approve - Reject - Remove - + Add step - Approvals waiting on me right now - Approve or reject my current step - List - Create - Update ## Access and 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. Permission keys: settings:view, settings:create, settings:update, settings:delete ## Workflow 1. Create a workflow definition and its ordered steps. 2. Review the workflow linked to the business record. 3. The current approver opens their pending queue. 4. Record the decision and inspect the next step. ## Fields and controls - decision ('APPROVED' | 'REJECTED', declared required) - remark (string, optional) - name (string, optional) - entityType (string, declared required) - description (string, optional) - steps (WorkflowStepDto[], optional) - isActive (boolean, optional) ## Current limits - Approval is limited to the current eligible approver; it is separate from directly editing the source business record. ## Actual application access - https://avkul.in/en/school/workflows ## API reference - GET /api/v1/workflows/pending-for-me — Approvals waiting on me right now; Authenticated scope - POST /api/v1/workflows/instances/:id/decide — Approve or reject my current step; Authenticated scope - GET /api/v1/workflows — List; settings:view - POST /api/v1/workflows — Create; settings:create - PATCH /api/v1/workflows/:id — Update; settings:update - DELETE /api/v1/workflows/:id — Remove; settings:delete ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # ERP sign-in Sign in to the ERP using your assigned account. The public guided demo runs separately with fictional data. Category: Administration Guide: https://avkul.in/docs/guides/screen-login/ Guided sample demo: https://avkul.in/docs/demo/screen-login/ Snapshot: 11 October 2026 ## Features - Assigned identifier - Password - School code where required - Role-based workspace ## Access and 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. ## Workflow 1. Open the ERP sign-in page. 2. Enter the assigned identifier, password and school code when required. 3. Open the workspace available to your role. 4. Log out when finished. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited. ## Actual application access - https://avkul.in/en/login ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Choose your ERP workspace Navigate between the platform console, school office and family portal using the signed-in role. Category: Administration Guide: https://avkul.in/docs/guides/screen-workspace-navigation/ Guided sample demo: https://avkul.in/docs/demo/screen-workspace-navigation/ Snapshot: 11 October 2026 ## Features - Platform workspace - School workspace - Family portal ## Access and 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. ## Workflow 1. Sign in with the assigned account. 2. Open the workspace available to your role. 3. Use the navigation to open a permitted module. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited. ## Actual application access - https://avkul.in/en ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Public certificate verification Check a school-issued certificate using its verification link or token. Category: School office Guide: https://avkul.in/docs/guides/screen-verify-token-detail/ Guided sample demo: https://avkul.in/docs/demo/screen-verify-token-detail/ Snapshot: 11 October 2026 ## Features - Token verification - Certificate validity - Revoked or unavailable feedback ## Access and 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. ## Workflow 1. Open the verification link printed on the issued document. 2. Review the returned certificate status. 3. Ask the issuing school about an invalid or revoked document. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - Verification requires an actual generated token. Sample demo certificates are not school-issued documents. ## Actual application access - https://avkul.in/en/verify — select the actual record from this list. ## API reference - GET /api/v1/certificate/verify/:qrToken — Verify; Public/capability access ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Auto Report Card Remarks Auto Report Card Remarks is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-remarks/ Guided sample demo: https://avkul.in/docs/demo/ai-remarks/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: exam:update ## Workflow 1. Open School AI Tools and select “Auto Report Card Remarks”. 2. Enter the available student id fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/remarks — Generate Remark; exam:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Attendance Anomaly Detection Attendance Anomaly Detection is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-attendance-anomalies/ Guided sample demo: https://avkul.in/docs/demo/ai-attendance-anomalies/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: attendance:view ## Workflow 1. Open School AI Tools and select “Attendance Anomaly Detection”. 2. Enter the available section id fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Section Id ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/attendance-anomalies — Attendance Anomalies; attendance:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Fee Defaulter Prediction Fee Defaulter Prediction is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-fee-risk/ Guided sample demo: https://avkul.in/docs/demo/ai-fee-risk/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: fee:view ## Workflow 1. Open School AI Tools and select “Fee Defaulter Prediction”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/fee-risk — Fee Risk; fee:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Question Paper Generator AI Question Paper Generator is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-question-paper/ Guided sample demo: https://avkul.in/docs/demo/ai-question-paper/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: exam:create ## Workflow 1. Open School AI Tools and select “AI Question Paper Generator”. 2. Enter the available subject, topic, count, difficulty fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Subject - Topic - Count - Difficulty ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/question-paper — Generate Question Paper; exam:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Discipline Pattern Detection Discipline Pattern Detection is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-discipline-risk/ Guided sample demo: https://avkul.in/docs/demo/ai-discipline-risk/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Discipline Pattern Detection”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/discipline-risk — Discipline Risk; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Parent Chatbot Parent Chatbot is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-parent-chat/ Guided sample demo: https://avkul.in/docs/demo/ai-parent-chat/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “Parent Chatbot”. 2. Enter the available student id, question fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Question ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/parent-chat — Parent Chat; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Study Buddy AI Study Buddy is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-study-buddy/ Guided sample demo: https://avkul.in/docs/demo/ai-study-buddy/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: lms:view ## Workflow 1. Open School AI Tools and select “AI Study Buddy”. 2. Enter the available lesson id, question fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Lesson Id - Question ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/study-buddy — Study Buddy; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Career/Stream Counselor Career/Stream Counselor is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-career-counsel/ Guided sample demo: https://avkul.in/docs/demo/ai-career-counsel/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Career/Stream Counselor”. 2. Enter the available student id fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/career-counsel/:studentId — Career Counsel; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Timetable Optimizer Timetable Optimizer is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-timetable-suggest/ Guided sample demo: https://avkul.in/docs/demo/ai-timetable-suggest/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: timetable:view ## Workflow 1. Open School AI Tools and select “Timetable Optimizer”. 2. Enter the available timetable id fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Timetable Id ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/timetable-suggest — Suggest Timetable; timetable:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Smart Inventory Reorder Smart Inventory Reorder is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-inventory-reorder/ Guided sample demo: https://avkul.in/docs/demo/ai-inventory-reorder/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: inventory:view ## Workflow 1. Open School AI Tools and select “Smart Inventory Reorder”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/inventory-reorder — Inventory Reorder; inventory:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Notice/Circular Writer AI Notice/Circular Writer is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-notice-draft/ Guided sample demo: https://avkul.in/docs/demo/ai-notice-draft/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: communication:create ## Workflow 1. Open School AI Tools and select “AI Notice/Circular Writer”. 2. Enter the available bullet points, language fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Bullet Points - Language ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/notice-draft — Draft Notice; communication:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Alumni Mentorship Matching Alumni Mentorship Matching is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-alumni-match/ Guided sample demo: https://avkul.in/docs/demo/ai-alumni-match/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Alumni Mentorship Matching”. 2. Enter the available student id, interest area fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Interest Area ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/alumni-match — Match Alumni; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Voice-to-Attendance Voice-to-Attendance is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-voice-attendance/ Guided sample demo: https://avkul.in/docs/demo/ai-voice-attendance/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: attendance:create ## Workflow 1. Open School AI Tools and select “Voice-to-Attendance”. 2. Enter the available section id, transcript fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Section Id - Transcript ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/voice-attendance — Voice Attendance; attendance:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Photo-based Visitor Verification Photo-based Visitor Verification is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-visitor-verify/ Guided sample demo: https://avkul.in/docs/demo/ai-visitor-verify/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: hostel:view ## Workflow 1. Open School AI Tools and select “Photo-based Visitor Verification”. 2. Enter the available image url, claimed name, visitor log id, reference image url fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Image Url - Claimed Name - Visitor Log Id - Reference Image Url ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/visitor-verify — Verify Visitor Photo; hostel:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Repeat Visitor Pattern Detection Repeat Visitor Pattern Detection is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-repeat-visitors/ Guided sample demo: https://avkul.in/docs/demo/ai-repeat-visitors/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: hostel:view ## Workflow 1. Open School AI Tools and select “Repeat Visitor Pattern Detection”. 2. Enter the available days fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Days ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/repeat-visitors — Repeat Visitors; hostel:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Biometric Face Match Biometric Face Match is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-face-match/ Guided sample demo: https://avkul.in/docs/demo/ai-face-match/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: hostel:view ## Workflow 1. Open School AI Tools and select “Biometric Face Match”. 2. Enter the available source image url, target image url fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Source Image Url - Target Image Url ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/face-match — Compare Faces; hostel:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Predictive Dropout Risk Predictive Dropout Risk is an available tool in the School AI Tools workspace (Existing). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-dropout-risk/ Guided sample demo: https://avkul.in/docs/demo/ai-dropout-risk/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Predictive Dropout Risk”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/dropout-risk — Dropout Risk; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Personalized Learning Path Personalized Learning Path is an available tool in the School AI Tools workspace (Academic Intelligence). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-learning-path/ Guided sample demo: https://avkul.in/docs/demo/ai-learning-path/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: lms:view ## Workflow 1. Open School AI Tools and select “Personalized Learning Path”. 2. Enter the available student id, days, regenerate fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Days - Regenerate ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/learning-path — Learning Path; lms:view - GET /api/v1/ai-features/learning-path/:studentId — Get Learning Path; lms:view - GET /api/v1/ai-features/learning-path/:studentId/history — Learning Path History; lms:view - PATCH /api/v1/ai-features/learning-path-items/:itemId — Update Learning Path Item; lms:view - POST /api/v1/ai-features/learning-gaps/alerts/:alertId/learning-path — Learning Path From Gap; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Early Learning Gap Detection Early Learning Gap Detection is an available tool in the School AI Tools workspace (Academic Intelligence). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-learning-gaps/ Guided sample demo: https://avkul.in/docs/demo/ai-learning-gaps/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view, lms:view ## Workflow 1. Open School AI Tools and select “Early Learning Gap Detection”. 2. Enter the available section id, weeks fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Section Id - Weeks ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/learning-gaps — List Learning Gaps; student:view - GET /api/v1/ai-features/learning-gaps/latest — Latest Learning Gap Scan; student:view - POST /api/v1/ai-features/learning-gaps/scan — Run Learning Gap Scan; student:view - PATCH /api/v1/ai-features/learning-gaps/alerts/:alertId — Update Learning Gap Alert; student:view - POST /api/v1/ai-features/learning-gaps/alerts/:alertId/learning-path — Learning Path From Gap; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Adaptive Online Exams Adaptive Online Exams is an available tool in the School AI Tools workspace (Academic Intelligence). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-adaptive-exam/ Guided sample demo: https://avkul.in/docs/demo/ai-adaptive-exam/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: exam:view ## Workflow 1. Open School AI Tools and select “Adaptive Online Exams”. 2. Enter the available student id, subject id, answers json fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Subject Id - Answers Json ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/adaptive-exam — Adaptive Exam; exam:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Lesson Planner AI Lesson Planner is an available tool in the School AI Tools workspace (Academic Intelligence). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-lesson-planner/ Guided sample demo: https://avkul.in/docs/demo/ai-lesson-planner/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: timetable:view ## Workflow 1. Open School AI Tools and select “AI Lesson Planner”. 2. Enter the available class id, subject id, topic, week of, regenerate fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Class Id - Subject Id - Topic - Week Of - Regenerate ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/lesson-planner — List Lesson Plans; timetable:view - POST /api/v1/ai-features/lesson-planner — Generate Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/days/:dayId — Update Lesson Plan Day; timetable:view - GET /api/v1/ai-features/lesson-planner/:planId — Get Lesson Plan; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId — Update Lesson Plan Meta; timetable:view - PATCH /api/v1/ai-features/lesson-planner/:planId/status — Set Lesson Plan Status; timetable:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Multilingual Explain Multilingual Explain is an available tool in the School AI Tools workspace (Academic Intelligence). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-multilingual-explain/ Guided sample demo: https://avkul.in/docs/demo/ai-multilingual-explain/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: lms:view ## Workflow 1. Open School AI Tools and select “Multilingual Explain”. 2. Enter the available concept, level, languages, publish fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Concept - Level - Languages - Publish ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/multilingual-explain — List Multilingual Explain; lms:view - POST /api/v1/ai-features/multilingual-explain — Generate Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/langs/:langId — Update Multilingual Explain Lang; lms:view - GET /api/v1/ai-features/multilingual-explain/:id — Get Multilingual Explain; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id — Update Multilingual Explain Meta; lms:view - PATCH /api/v1/ai-features/multilingual-explain/:id/status — Set Multilingual Explain Status; lms:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Enrolment & Capacity Forecast Enrolment & Capacity Forecast is an available tool in the School AI Tools workspace (Predictive Ops). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-enrolment-forecast/ Guided sample demo: https://avkul.in/docs/demo/ai-enrolment-forecast/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:manage ## Workflow 1. Open School AI Tools and select “Enrolment & Capacity Forecast”. 2. Enter the available conversion pct, default section capacity, students per teacher, label fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Conversion Pct - Default Section Capacity - Students Per Teacher - Label ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/enrolment-forecast — List Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/latest — Latest Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/compare — Compare Enrolment Forecast; student:manage - POST /api/v1/ai-features/enrolment-forecast — Run Enrolment Forecast; student:manage - GET /api/v1/ai-features/enrolment-forecast/:id — Get Enrolment Forecast; student:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Cashflow Prediction Cashflow Prediction is an available tool in the School AI Tools workspace (Predictive Ops). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-cashflow-prediction/ Guided sample demo: https://avkul.in/docs/demo/ai-cashflow-prediction/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: fee:manage ## Workflow 1. Open School AI Tools and select “Cashflow Prediction”. 2. Enter the available scholarship pct, months, collection rate pct, label fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Scholarship Pct - Months - Collection Rate Pct - Label ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/cashflow-prediction — List Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/latest — Latest Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/compare — Compare Cashflow; fee:manage - POST /api/v1/ai-features/cashflow-prediction — Run Cashflow; fee:manage - GET /api/v1/ai-features/cashflow-prediction/:id — Get Cashflow; fee:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Staff Workload Optimizer Staff Workload Optimizer is an available tool in the School AI Tools workspace (Predictive Ops). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-staff-workload/ Guided sample demo: https://avkul.in/docs/demo/ai-staff-workload/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: timetable:view, attendance:update ## Workflow 1. Open School AI Tools and select “Staff Workload Optimizer”. 2. Enter the available overload threshold, medium threshold, underutilized ratio, label fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Overload Threshold - Medium Threshold - Underutilized Ratio - Label ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/staff-workload — List Staff Workload; timetable:view, attendance:update - GET /api/v1/ai-features/staff-workload/latest — Latest Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload — Run Staff Workload; timetable:view, attendance:update - POST /api/v1/ai-features/staff-workload/substitutions — Suggest Substitutions; timetable:view, attendance:update - GET /api/v1/ai-features/staff-workload/:id — Get Staff Workload; timetable:view, attendance:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Transport ETA + Route AI Transport ETA + Route AI is an available tool in the School AI Tools workspace (Predictive Ops). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-transport-eta/ Guided sample demo: https://avkul.in/docs/demo/ai-transport-eta/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: transport:view ## Workflow 1. Open School AI Tools and select “Transport ETA + Route AI”. 2. Enter the available scope, vehicle id, route id, late threshold min, label fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Scope - Vehicle Id - Route Id - Late Threshold Min - Label ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/transport-eta — List Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/latest — Latest Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/live/:vehicleId — Live Transport Eta; transport:view - POST /api/v1/ai-features/transport-eta — Run Transport Eta; transport:view - GET /api/v1/ai-features/transport-eta/:id — Get Transport Eta; transport:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Hostel/Inventory Demand Forecast Hostel/Inventory Demand Forecast is an available tool in the School AI Tools workspace (Predictive Ops). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-hostel-inventory-forecast/ Guided sample demo: https://avkul.in/docs/demo/ai-hostel-inventory-forecast/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: inventory:view ## Workflow 1. Open School AI Tools and select “Hostel/Inventory Demand Forecast”. 2. Enter the available lookback days, horizon days, occupancy boost pct, category, label fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Lookback Days - Horizon Days - Occupancy Boost Pct - Category - Label ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/hostel-inventory-forecast — List Inventory Forecast; inventory:view - GET /api/v1/ai-features/hostel-inventory-forecast/latest — Latest Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast — Run Inventory Forecast; inventory:view - POST /api/v1/ai-features/hostel-inventory-forecast/:id/draft-po — Draft Po From Forecast; inventory:view - GET /api/v1/ai-features/hostel-inventory-forecast/:id — Get Inventory Forecast; inventory:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Parent Copilot (WhatsApp) AI Parent Copilot (WhatsApp) is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-parent-copilot/ Guided sample demo: https://avkul.in/docs/demo/ai-parent-copilot/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “AI Parent Copilot (WhatsApp)”. 2. Enter the available student id, question, channel fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Question - Channel ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/parent-copilot — Parent Copilot; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # WhatsApp Copilot Simulator WhatsApp Copilot Simulator is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-whatsapp-parent-copilot/ Guided sample demo: https://avkul.in/docs/demo/ai-whatsapp-parent-copilot/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “WhatsApp Copilot Simulator”. 2. Enter the available from, text, dry run fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - From - Text - Dry Run ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/whatsapp-parent-copilot/simulate — Simulate; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Voice School Assistant Voice School Assistant is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-voice-assistant/ Guided sample demo: https://avkul.in/docs/demo/ai-voice-assistant/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “Voice School Assistant”. 2. Enter the available student id, transcript fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Transcript ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/voice-assistant — Voice Assistant; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Progress Story for Parents Progress Story for Parents is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-progress-story/ Guided sample demo: https://avkul.in/docs/demo/ai-progress-story/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Progress Story for Parents”. 2. Enter the available student id, language fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Language ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/progress-story — Progress Story; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Career Twin Career Twin is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-career-twin/ Guided sample demo: https://avkul.in/docs/demo/ai-career-twin/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Career Twin”. 2. Enter the available student id, interests, psychometric json fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Interests - Psychometric Json ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/career-twin — Career Twin; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Alumni Opportunity Matcher Alumni Opportunity Matcher is an available tool in the School AI Tools workspace (Parent & Student). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-alumni-opportunity/ Guided sample demo: https://avkul.in/docs/demo/ai-alumni-opportunity/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:view ## Workflow 1. Open School AI Tools and select “Alumni Opportunity Matcher”. 2. Enter the available student id, opportunity type, interest area fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Student Id - Opportunity Type - Interest Area ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/alumni-opportunity — Alumni Opportunity; student:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Campus Safety AI Campus Safety AI is an available tool in the School AI Tools workspace (Safety & Trust). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-campus-safety/ Guided sample demo: https://avkul.in/docs/demo/ai-campus-safety/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: hostel:view ## Workflow 1. Open School AI Tools and select “Campus Safety AI”. 2. Enter the available vehicle id, days fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Vehicle Id - Days ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/campus-safety — Campus Safety; hostel:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Wellbeing / Sentiment Radar Wellbeing / Sentiment Radar is an available tool in the School AI Tools workspace (Safety & Trust). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-wellbeing-radar/ Guided sample demo: https://avkul.in/docs/demo/ai-wellbeing-radar/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: health:manage ## Workflow 1. Open School AI Tools and select “Wellbeing / Sentiment Radar”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/wellbeing-radar — Wellbeing Radar; health:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # AI Audit Trail AI Audit Trail is an available tool in the School AI Tools workspace (Safety & Trust). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-ai-audit/ Guided sample demo: https://avkul.in/docs/demo/ai-ai-audit/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “AI Audit Trail”. 2. Enter the available decision, request id, note, corrected text, feature fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Decision - Request Id - Note - Corrected Text - Feature ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/ai-audit — Ai Audit; dashboard:view - POST /api/v1/ai-features/ai-audit/feedback — Ai Audit Feedback; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Fairness Monitor Fairness Monitor is an available tool in the School AI Tools workspace (Safety & Trust). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-fairness-monitor/ Guided sample demo: https://avkul.in/docs/demo/ai-fairness-monitor/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: student:manage ## Workflow 1. Open School AI Tools and select “Fairness Monitor”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/fairness-monitor — Fairness Monitor; student:manage ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Data Minimization Mode Data Minimization Mode is an available tool in the School AI Tools workspace (Safety & Trust). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-data-minimization/ Guided sample demo: https://avkul.in/docs/demo/ai-data-minimization/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view, settings:update ## Workflow 1. Open School AI Tools and select “Data Minimization Mode”. 2. Enter the available save, biometric enabled, face match enabled, biometric retention days, parent opt out default fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Save - Biometric Enabled - Face Match Enabled - Biometric Retention Days - Parent Opt Out Default ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/data-minimization — Get Data Minimization; dashboard:view - PATCH /api/v1/ai-features/data-minimization — Update Data Minimization; settings:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Auto Grading + Rubric Feedback Auto Grading + Rubric Feedback is an available tool in the School AI Tools workspace (Teacher Productivity). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-auto-grade/ Guided sample demo: https://avkul.in/docs/demo/ai-auto-grade/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: exam:update ## Workflow 1. Open School AI Tools and select “Auto Grading + Rubric Feedback”. 2. Enter the available assignment id, student id, submission text, publish fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Assignment Id - Student Id - Submission Text - Publish ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/auto-grade — Auto Grade; exam:update ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Classroom Insight Board Classroom Insight Board is an available tool in the School AI Tools workspace (Teacher Productivity). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-classroom-insights/ Guided sample demo: https://avkul.in/docs/demo/ai-classroom-insights/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: attendance:view ## Workflow 1. Open School AI Tools and select “Classroom Insight Board”. 2. Enter the available section id fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Section Id ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/classroom-insights — Classroom Insights; attendance:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Substitution Brain Substitution Brain is an available tool in the School AI Tools workspace (Teacher Productivity). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-substitution-brain/ Guided sample demo: https://avkul.in/docs/demo/ai-substitution-brain/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: timetable:view ## Workflow 1. Open School AI Tools and select “Substitution Brain”. 2. Enter the available absent staff id, date fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Absent Staff Id - Date ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/substitution-brain — Substitution Brain; timetable:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Question Bank Intelligence Question Bank Intelligence is an available tool in the School AI Tools workspace (Teacher Productivity). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-question-bank-intel/ Guided sample demo: https://avkul.in/docs/demo/ai-question-bank-intel/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: exam:view ## Workflow 1. Open School AI Tools and select “Question Bank Intelligence”. 2. Enter the available subject id, paper size fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Subject Id - Paper Size ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/question-bank-intel — Question Bank Intel; exam:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Meeting Notes → Actions Meeting Notes → Actions is an available tool in the School AI Tools workspace (Teacher Productivity). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-meeting-notes/ Guided sample demo: https://avkul.in/docs/demo/ai-meeting-notes/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: communication:create ## Workflow 1. Open School AI Tools and select “Meeting Notes → Actions”. 2. Enter the available transcript, meeting type fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Transcript - Meeting Type ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/meeting-notes — Meeting Notes; communication:create ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # School Twin Benchmarking School Twin Benchmarking is an available tool in the School AI Tools workspace (SaaS Moat). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-school-twin-benchmark/ Guided sample demo: https://avkul.in/docs/demo/ai-school-twin-benchmark/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “School Twin Benchmarking”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/school-twin-benchmark — School Twin Benchmark; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Policy Copilot Policy Copilot is an available tool in the School AI Tools workspace (SaaS Moat). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-policy-copilot/ Guided sample demo: https://avkul.in/docs/demo/ai-policy-copilot/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “Policy Copilot”. 2. Enter the available question, board fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Question - Board ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/policy-copilot — Policy Copilot; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Auto Accreditation Pack Auto Accreditation Pack is an available tool in the School AI Tools workspace (SaaS Moat). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-accreditation-pack/ Guided sample demo: https://avkul.in/docs/demo/ai-accreditation-pack/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “Auto Accreditation Pack”. 2. Enter the available purpose fields. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls - Purpose ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - POST /api/v1/ai-features/accreditation-pack — Accreditation Pack; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # Branch Performance Copilot Branch Performance Copilot is an available tool in the School AI Tools workspace (SaaS Moat). Review the required context and the returned output before using it. Category: Intelligence Guide: https://avkul.in/docs/guides/ai-branch-performance/ Guided sample demo: https://avkul.in/docs/demo/ai-branch-performance/ Snapshot: 11 October 2026 ## Features - Tool-specific input - Available result review - Provider-dependent output - Human review ## Access and setup Intended access: Assigned account with the required permissions - An authorised school account and the permissions for this tool. - A valid learner, staff, section or topic reference where the tool asks for one. Permission keys: dashboard:view ## Workflow 1. Open School AI Tools and select “Branch Performance Copilot”. 2. Review the available school context for this tool. 3. Run the tool and check the provider/sample-output banner. 4. Inspect the result and confirm important details against school records. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - The documentation demo uses deterministic fictional sample output, not a live AI provider. - Provider configuration, image/voice inputs and live integrations require separate verification. Human review remains necessary. ## Actual application access - https://avkul.in/en/school/ai-tools ## API reference - GET /api/v1/ai-features/branch-performance — Branch Performance; dashboard:view ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Individual tool checked in current source. This source inventory is not a certification of every external provider or device flow. --- # School website: Homepage Home at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-home/ Guided sample demo: https://avkul.in/docs/demo/website-home/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: About our school About our school at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-about/ Guided sample demo: https://avkul.in/docs/demo/website-about/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/about/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Vision & mission Vision & mission at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-vision-mission/ Guided sample demo: https://avkul.in/docs/demo/website-vision-mission/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/vision-mission/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Principal’s message Principal’s message at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-principals-message/ Guided sample demo: https://avkul.in/docs/demo/website-principals-message/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/principals-message/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Academics Academics at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-academics/ Guided sample demo: https://avkul.in/docs/demo/website-academics/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/academics/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Curriculum & learning Curriculum & learning at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-curriculum/ Guided sample demo: https://avkul.in/docs/demo/website-curriculum/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/curriculum/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Campus & facilities Campus & facilities at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-facilities/ Guided sample demo: https://avkul.in/docs/demo/website-facilities/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/facilities/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Campus life Campus life at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-campus-life/ Guided sample demo: https://avkul.in/docs/demo/website-campus-life/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/campus-life/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Events & celebrations Events & celebrations at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-events/ Guided sample demo: https://avkul.in/docs/demo/website-events/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/events/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Gallery Gallery at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-gallery/ Guided sample demo: https://avkul.in/docs/demo/website-gallery/ Snapshot: 11 October 2026 ## Features - School image gallery - Responsive image display - Gallery navigation ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the gallery page. 2. Browse the available school images. 3. Use the gallery controls to explore individual images. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/gallery/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: School journal School journal at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-news/ Guided sample demo: https://avkul.in/docs/demo/website-news/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/news/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Admissions Admissions at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-admissions/ Guided sample demo: https://avkul.in/docs/demo/website-admissions/ Snapshot: 11 October 2026 ## Features - Published school information - Consented enquiry form - Receipt reference - ERP admissions connection ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the public school page. 2. Review school information and complete the enquiry fields. 3. Give consent and submit the request. 4. Keep the receipt reference; school staff manage the enquiry in ERP. ## Fields and controls - Guardian/contact name - Contact details - Enquiry message - Consent ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - Submitting an enquiry creates a request; it does not automatically admit a student or send a payment. ## Actual application access - https://avkul.in/ddinternationalshcool/admissions/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Fees & scholarships Fees & scholarships at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-fees/ Guided sample demo: https://avkul.in/docs/demo/website-fees/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/fees/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: School transport School transport at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-transport/ Guided sample demo: https://avkul.in/docs/demo/website-transport/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/transport/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Parent resources Parent resources at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-parent-resources/ Guided sample demo: https://avkul.in/docs/demo/website-parent-resources/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/parent-resources/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: School calendar School calendar at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-calendar/ Guided sample demo: https://avkul.in/docs/demo/website-calendar/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/calendar/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Frequently asked questions Frequently asked questions at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-faq/ Guided sample demo: https://avkul.in/docs/demo/website-faq/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/faq/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Careers Careers at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-careers/ Guided sample demo: https://avkul.in/docs/demo/website-careers/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/careers/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Contact & visits Contact & visits at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-contact/ Guided sample demo: https://avkul.in/docs/demo/website-contact/ Snapshot: 11 October 2026 ## Features - Published school information - Consented enquiry form - Receipt reference - ERP admissions connection ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the public school page. 2. Review school information and complete the enquiry fields. 3. Give consent and submit the request. 4. Keep the receipt reference; school staff manage the enquiry in ERP. ## Fields and controls - Guardian/contact name - Contact details - Enquiry message - Consent ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - Submitting an enquiry creates a request; it does not automatically admit a student or send a payment. ## Actual application access - https://avkul.in/ddinternationalshcool/contact/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # School website: Privacy & website information Privacy & website information at D&D International School — knowledge, character and community. Category: Websites Guide: https://avkul.in/docs/guides/website-privacy/ Guided sample demo: https://avkul.in/docs/demo/website-privacy/ Snapshot: 11 October 2026 ## Features - Published page content - School navigation - Responsive display - Contact and admissions links ## Access and setup Intended access: Public reader - No ERP account is required to read the public page. ## Workflow 1. Open the published page. 2. Read the available school content. 3. Use the school navigation or contact link for the next step. ## Fields and controls Use the relevant context and operation-specific form in the workspace. ## Current limits - School content and illustrative campus imagery are subject to the school’s confirmation. - School-owned content is edited through the permitted website CMS. ## Actual application access - https://avkul.in/ddinternationalshcool/privacy/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Published page metadata checked live on 11 October 2026. This source inventory is not a certification of every external provider or device flow. --- # Applicant self-service portal Use a privately issued application link to save a draft, upload documents and request a campus visit. Category: School office Guide: https://avkul.in/docs/guides/applicant-portal/ Guided sample demo: https://avkul.in/docs/demo/applicant-portal/ Snapshot: 11 October 2026 ## Features - Seven-day capability link - Draft save and resume - PDF/image documents up to 10 MB - Review feedback and resubmission - Visit preferences - Application submission ## Access and setup Intended access: Assigned account with the required permissions - Use the official link and the applicable access context. ## Workflow 1. Open the private link issued by the school. 2. Save guardian/application details and supported documents. 3. Review feedback and resubmit a rejected document if needed. 4. Submit when the required documents are received. ## Fields and controls - Application details - Guardian details - Required documents - Visit preferences ## Current limits - A bare portal URL requires the private application link; this documentation does not publish capability tokens. - Uploads are reviewed by staff. OCR, malware scanning and gateway collection are not included in this release. ## Actual application access - https://avkul.in/ddinternationalshcool/apply/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Implementation checked against the delivered release guide. This source inventory is not a certification of every external provider or device flow. --- # Parent account invitation Accept the school’s private post-admission invitation and choose a parent account password. Category: Family portal Guide: https://avkul.in/docs/guides/parent-invitation/ Guided sample demo: https://avkul.in/docs/demo/parent-invitation/ Snapshot: 11 October 2026 ## Features - 24-hour invitation - Single-use acceptance - Guardian-chosen password - Parent-only account ## Access and setup Intended access: Assigned account with the required permissions - Use the official link and the applicable access context. ## Workflow 1. Open the private invitation from the school after admission. 2. Choose and confirm the required password. 3. Accept the invitation once. 4. Sign in with the assigned guardian identifier and school code. ## Fields and controls - Password - Password confirmation ## Current limits - Existing accounts are not reset through invitations. - Invitations are not automatically delivered by SMS/email and are never included in public documentation. ## Actual application access - https://avkul.in/ddinternationalshcool/parent-setup/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Implementation checked against the delivered release guide. This source inventory is not a certification of every external provider or device flow. --- # AVKUL ERP Android app Install the published Android app and use the same assigned school account on mobile. Category: Mobile Guide: https://avkul.in/docs/guides/android-app/ Guided sample demo: https://avkul.in/docs/demo/android-app/ Snapshot: 11 October 2026 ## Features - Signed Android APK - Role-based mobile workspaces - Shared school account - 52 source screens - Logout clears account cache ## Access and setup Intended access: Assigned account with the required permissions - Use the official link and the applicable access context. ## Workflow 1. Download the AVKUL ERP Android APK from the official link. 2. Install on a compatible Android device when permitted by your device policy. 3. Sign in with the assigned account and school code. 4. Use the modules available to your role and log out when finished. ## Fields and controls - Identifier - Password - School code ## Current limits - The signed Android artifact is published; physical-device camera/microphone/media flows require device-specific testing. - iOS and Play Store distribution are separate releases. Mobile source coverage is not a certification of every native screen. ## Actual application access - https://avkul.in/downloads/avkul-erp-android-v0.1.1.apk ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Implementation checked against the delivered release guide. This source inventory is not a certification of every external provider or device flow. --- # AVKUL ERP marketing website Explore platform capabilities and request a product walkthrough from the public AVKUL ERP homepage. Category: Websites Guide: https://avkul.in/docs/guides/platform-website/ Guided sample demo: https://avkul.in/docs/demo/platform-website/ Snapshot: 11 October 2026 ## Features - Platform overview - Stakeholder views - Questions and answers - Walkthrough enquiry - Roadmap - Privacy choices ## Access and setup Intended access: Platform administrator - Use the official link and the applicable access context. ## Workflow 1. Explore the public platform sections. 2. Open a documentation guide or guided demo. 3. Use Request a walkthrough for a personalised product conversation. ## Fields and controls - Name - School - Email - Phone - Student range - Consent ## Current limits - A walkthrough enquiry does not create an ERP login. - Analytics collection follows browser privacy preferences and configured collection rules. ## Actual application access - https://avkul.in/ ## API reference See connected module reference. ## Demo access No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links. Implementation checked against the delivered release guide. This source inventory is not a certification of every external provider or device flow. # Mobile source screen reference - (app)/ai-chat.tsx - (app)/alumni-directory.tsx - (app)/attendance.tsx - (app)/certificates.tsx - (app)/complaints.tsx - (app)/concept-explainer.tsx - (app)/discipline.tsx - (app)/enquiries.tsx - (app)/events.tsx - (app)/exams/attempt.tsx - (app)/exams/index.tsx - (app)/fees.tsx - (app)/fleet.tsx - (app)/health.tsx - (app)/hostel/allocations.tsx - (app)/hostel/index.tsx - (app)/hostel/my-room.tsx - (app)/hostel/rooms.tsx - (app)/hostel/visitors.tsx - (app)/id-card.tsx - (app)/index.tsx - (app)/inventory.tsx - (app)/learning-gaps.tsx - (app)/leave.tsx - (app)/lesson-planner.tsx - (app)/library-issues.tsx - (app)/library.tsx - (app)/live-classes/index.tsx - (app)/live-classes/[id].tsx - (app)/lms/homework.tsx - (app)/lms/index.tsx - (app)/lms/learning-path.tsx - (app)/lms/lesson/[lessonId].tsx - (app)/lms/[courseId].tsx - (app)/marks-entry.tsx - (app)/notices.tsx - (app)/notifications.tsx - (app)/payroll.tsx - (app)/platform-ai.tsx - (app)/platform-tenants.tsx - (app)/profile.tsx - (app)/ptm.tsx - (app)/reports.tsx - (app)/results.tsx - (app)/staff-workload.tsx - (app)/students.tsx - (app)/system.tsx - (app)/teacher-toolkit.tsx - (app)/timetable-builder.tsx - (app)/timetable.tsx - (app)/transport.tsx - (auth)/login.tsx