AVKUL ERPDocs
SCHOOLOS · FEATURE HANDBOOK

Every workflow.
Clearly explained.

Snapshot: 11 October 2026 · 236 guides.

Public guided demos use fictional data. Live modules require an assigned account. Provider-dependent features retain the limitations in their individual guides.

Academics · Module guide

Academic setup

Create the academic structure that attendance, admissions, examinations and timetables share.

Academic setup illustrated banner

Online guide · Guided demo

What you can do

01

Academic sessions

02

Classes and sections

03

Subject catalogue

04

Current session

05

Year-end close and reopen

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
settings:viewsettings:createsettings:updatesettings:deletestudent:viewsettings:manage

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

How the workflow works

  1. 01

    Create an academic session with dates

    An assigned school account with the required permissions.

  2. 02

    Add classes and their sections

    Classes and sections is part of the documented workflow.

  3. 03

    Create subjects and select the current session

    Subject catalogue is part of the documented workflow.

  4. 04

    Close the books only after the year-end review

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
startDatestringRequired by declaration
endDatestringRequired by declaration
isCurrentbooleanOptional
sessionIdstringRequired by declaration
numericLevelnumberOptional
streamIdstringOptional
sortOrdernumberOptional
classIdstringRequired by declaration
capacitynumberOptional
classTeacherIdstringOptional
roomNostringOptional
codestringOptional
typestringOptional
isElectivebooleanOptional
creditsnumberOptional
lockedbooleanRequired by declaration
reasonstringOptional

Rules & current limits

  • Session ownership and closed-year checks apply to connected workflows.

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

Administration · Module guide

Roles & permissions

Control which school users can view, create, edit, export and manage records.

Roles & permissions illustrated banner

Online guide · Guided demo

What you can do

01

Role catalogue

02

Permission catalogue

03

Role grants

04

User assignment

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
role:viewrole:createrole:updaterole:deleterole:manage

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

How the workflow works

  1. 01

    Open a role and inspect its existing permissions

    An assigned school account with the required permissions.

  2. 02

    Choose only the required permission keys

    Permission catalogue is part of the documented workflow.

  3. 03

    Save the role and assign eligible users

    Role grants is part of the documented workflow.

  4. 04

    Sign in as the affected role to review access

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
keystringRequired by declaration
descriptionstringOptional
permissionKeysstring[]Required by declaration
userIdstringRequired by declaration

Rules & current limits

  • A role name alone does not grant platform administration. School scope and explicit guards still apply.

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

School office · Module guide

Admissions & applicant journey

Connect family enquiries, counsellor follow-ups, reviewed applications and student admission.

Admissions & applicant journey illustrated banner

Online guide · Guided demo

What you can do

01

Enquiry pipeline

02

Contact attempts

03

Application stages

04

Guardian details

05

Campus visits

06

Document review

07

Applicant access links

08

Student placement

09

Parent invitation

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
admission:manageadmission:viewadmission:updateadmission:createstudent:create

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

How the workflow works

  1. 01

    Record or select an enquiry and log the next follow-up

    An assigned school account with the required permissions.

  2. 02

    Open a linked application and review guardian details

    Contact attempts is part of the documented workflow.

  3. 03

    Receive and verify required documents and review readiness

    Application stages is part of the documented workflow.

  4. 04

    Select session, class and section before admitting the applicant

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

Request fields to understand

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

FieldDeclared typeInput
purpose'APPLICANT' | 'PARENT_INVITE'Required by declaration
versionstringRequired by declaration
studentNamestringRequired by declaration
classApplyingstringRequired by declaration
guardianNamestringRequired by declaration
phonestringRequired by declaration
emailstringOptional
relationshipstringRequired by declaration
dateOfBirthstringOptional
previousSchoolstringOptional
addressstringOptional
preferredAtstringRequired by declaration
notesstringOptional
kindstringRequired by declaration
passwordstringRequired by declaration
summarystringRequired by declaration
channelstringOptional
outcomestringOptional
statusstringRequired by declaration
followUpAtstringOptional
byStaffIdstringOptional
counsellorIdstringRequired by declaration
reasonstringOptional
parentNamestringRequired by declaration

Rules & current limits

  • Application access links and parent invitations are separate from an existing family login. Admission is subject to readiness and school/session ownership.

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

Intelligence · Module guide

AI tools & decision support

Use assisted writing, learning support and forecasts while reviewing the provider state and human decisions.

AI tools & decision support illustrated banner

Online guide · Guided demo

What you can do

01

Provider status

02

Academic assistance

03

Learning gaps

04

Lesson planning

05

Forecast scenarios

06

Staff workload

07

Transport ETA

08

Governance and review

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
dashboard:viewexam:updateattendance:viewfee:viewexam:createstudent:viewlms:viewtimetable:viewinventory:viewcommunication:createattendance:createhostel:viewexam:viewstudent:managefee:manageattendance:updatetransport:viewhealth:managesettings:update

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

How the workflow works

  1. 01

    Review the provider-status banner before requesting assistance

    An assigned school account with the required permissions.

  2. 02

    Choose the school context, topic or forecast period

    Academic assistance is part of the documented workflow.

  3. 03

    Run the relevant tool and inspect its output and evidence

    Learning gaps is part of the documented workflow.

  4. 04

    Review or edit the result before using it with learners

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

Request fields to understand

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

FieldDeclared typeInput
studentIdstringRequired by declaration
examIdstringOptional
subjectstringRequired by declaration
topicstringOptional
difficultystringOptional
countnumberOptional
questionTypestringOptional
questionstringRequired by declaration
lessonIdstringRequired by declaration
bulletPointsstringRequired by declaration
languagestringOptional
interestAreastringOptional
sectionIdstringRequired by declaration
transcriptstringRequired by declaration
datestringOptional
imageUrlstringRequired by declaration
claimedNamestringOptional
visitorLogIdstringOptional
referenceImageUrlstringOptional
sourceImageUrlstringRequired by declaration
targetImageUrlstringRequired by declaration
daysnumberOptional
regeneratebooleanOptional
status'DRAFT' | 'PUBLISHED' | 'PRIVATE' | 'ARCHIVED'Required by declaration

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Community · Module guide

Alumni records

Maintain alumni information and keep former learners connected to the school community.

Alumni records illustrated banner

Online guide · Guided demo

What you can do

01

Alumni directory

02

Record creation

03

Profile updates

04

Record removal

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
student:viewstudent:createstudent:updatestudent:delete

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

How the workflow works

  1. 01

    Open the alumni directory

    An assigned school account with the required permissions.

  2. 02

    Add the alumnus and relevant year/contact details

    Record creation is part of the documented workflow.

  3. 03

    Update the record as information changes

    Profile updates is part of the documented workflow.

  4. 04

    Review scope before removing an entry

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

Request fields to understand

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

FieldDeclared typeInput
firstNamestringRequired by declaration
lastNamestringOptional
graduationYearnumberRequired by declaration
studentIdstringOptional
currentOccupationstringOptional
companystringOptional
emailstringOptional
phonestringOptional
linkedinUrlstringOptional
addressJsonRecord<string, unknown>Optional
notesstringOptional

Rules & current limits

  • A directory record does not automatically provision an alumni login or send invitations.

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

Academics · Module guide

Homework & assignments

Create and distribute class work, collect student submissions and record grading feedback.

Homework & assignments illustrated banner

Online guide · Guided demo

What you can do

01

Class and section scope

02

Assignment attachments

03

Submission queue

04

Grading

05

History

06

In-app reminders

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
assignment:viewassignment:updateassignment:createassignment:delete

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

How the workflow works

  1. 01

    Select the teaching section and create an assignment

    An assigned school account with the required permissions.

  2. 02

    Add the instructions, due date and supported files

    Assignment attachments is part of the documented workflow.

  3. 03

    Review submitted or pending work

    Submission queue is part of the documented workflow.

  4. 04

    Grade the submission and review the activity history

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

Request fields to understand

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

FieldDeclared typeInput
assignmentIdstringOptional
dueInDaysnumberOptional
titlestringRequired by declaration
classIdstringOptional
sectionIdstringOptional
subjectIdstringOptional
instructionsstringOptional
maxMarksnumberOptional
dueDatestringOptional
status'DRAFT' | 'PUBLISHED' | 'CLOSED'Optional
versionstringOptional
correctionReasonstringOptional
outcome'GRADED' | 'RETURNED'Optional
marksObtainednumberOptional
remarksstringOptional

Rules & current limits

  • Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel.

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

Academics · Module guide

Student attendance

Complete a daily class register and review attendance history, shortages and family alerts.

Student attendance illustrated banner

Online guide · Guided demo

What you can do

01

Section roster

02

Daily marking

03

Section completion

04

Corrections

05

Monthly register

06

Shortage review

07

Holiday stamping

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose a permitted section and date

    An assigned school account with the required permissions.

  2. 02

    Mark the roster and review the section completion summary

    Daily marking is part of the documented workflow.

  3. 03

    Save the register and inspect corrections/history

    Section completion is part of the documented workflow.

  4. 04

    Review shortages and recorded alerts before reminding families

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

Request fields to understand

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

FieldDeclared typeInput
sectionIdstringOptional
datestringRequired by declaration
sessionstringOptional
recordsAttendanceRecordInput[]Required by declaration
versionstringOptional
correctionReasonstringOptional
forcebooleanOptional
notifyGuardiansbooleanOptional
fromstringRequired by declaration
tostringRequired by declaration
messagestringOptional
studentIdsstring[]Optional

Rules & current limits

  • Holiday and attendance policy affect denominators. Only permitted sections are visible; recording an absence is distinct from approving leave.

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

Administration · Module guide

Audit trail

Review the recorded actions taken on school records and trace related entities.

Audit trail illustrated banner

Online guide · Guided demo

What you can do

01

Activity filters

02

Actor and action

03

Entity references

04

Record detail

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
settings:view

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

How the workflow works

  1. 01

    Select an entity or activity filter

    An assigned school account with the required permissions.

  2. 02

    Locate the relevant actor and time

    Actor and action is part of the documented workflow.

  3. 03

    Open the recorded change and its entity reference

    Entity references is part of the documented workflow.

  4. 04

    Compare the trail with the current record

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

Rules & current limits

  • The audit view records permitted activity; it is not an editor for rewriting historical actions.

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

Administration · Module guide

Sign-in & account sessions

Sign in with assigned account details and keep platform support access separate from school accounts.

Sign-in & account sessions illustrated banner

Online guide · Guided demo

What you can do

01

Account login

02

Current profile

03

Token refresh

04

Logout

05

Platform impersonation

Access & setup

Intended access: Platform administrator.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.

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

How the workflow works

  1. 01

    Open the ERP sign-in page

    An assigned school account with the required permissions.

  2. 02

    Enter the assigned identifier and school code when required

    Current profile is part of the documented workflow.

  3. 03

    Use the workspace available to the signed-in role

    Token refresh is part of the documented workflow.

  4. 04

    Log out when the session is finished

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

Request fields to understand

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

FieldDeclared typeInput
identifierstringRequired by declaration
passwordstringRequired by declaration
schoolCodestringOptional
tenantSlugstringOptional
deviceNamestringOptional
refreshTokenstringOptional
userIdstringRequired by declaration
reasonstringRequired by declaration
minutesnumberOptional
sessionIdstringOptional

Rules & current limits

  • Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited.

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

School office · Module guide

Student & staff import/export

Prepare spreadsheet records using the provided templates and use the bulk student/staff operations.

Student & staff import/export illustrated banner

Online guide · Guided demo

What you can do

01

Student template

02

Student import and export

03

Staff template

04

Staff import and export

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
student:createstudent:viewhr:createhr:view

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

How the workflow works

  1. 01

    Download the template for the chosen record type

    An assigned school account with the required permissions.

  2. 02

    Fill the required columns with school-owned references

    Student import and export is part of the documented workflow.

  3. 03

    Submit through the permitted bulk workflow and inspect its result

    Staff template is part of the documented workflow.

  4. 04

    Export and reconcile the accepted records

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

Rules & current limits

  • Imports can modify many records. A template or export endpoint does not imply a separate bulk-import page exists.

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

School office · Module guide

School calendar & holidays

Publish the dates, events and holiday settings that support school planning and attendance.

School calendar & holidays illustrated banner

Online guide · Guided demo

What you can do

01

Calendar view

02

Working days

03

Holiday settings

04

Attendance policy

05

Event RSVP

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
calendar:viewsettings:updatecalendar:createcalendar:updatecalendar:deletecommunication:manage

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

How the workflow works

  1. 01

    Review the selected calendar period

    An assigned school account with the required permissions.

  2. 02

    Add or update a permitted holiday or event

    Working days is part of the documented workflow.

  3. 03

    Check applicability to students and staff

    Holiday settings is part of the documented workflow.

  4. 04

    Review working days and RSVP summaries

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

Request fields to understand

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

FieldDeclared typeInput
weekOffDaysnumber[]Optional
minAttendancePercentnumberOptional
dayStartsAtstringOptional
namestringOptional
descriptionstringOptional
startDatestringOptional
endDatestringOptional
typestringOptional
appliesToStudentsbooleanOptional
appliesToStaffbooleanOptional
sessionIdstringOptional
statusstringRequired by declaration
guestsnumberOptional
remarkstringOptional

Rules & current limits

  • Declaring a holiday requires its own permission. The attendance and timetable workflows use their documented calendar rules.

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

School office · Module guide

Certificates & verification

Manage certificate templates, issue documents and provide token-based verification.

Certificates & verification illustrated banner

Online guide · Guided demo

What you can do

01

Templates

02

Individual and bulk issue

03

Generated records

04

Revocation

05

Public verification

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
certificate:viewcertificate:createcertificate:updatecertificate:delete

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

How the workflow works

  1. 01

    Choose or create a certificate template

    An assigned school account with the required permissions.

  2. 02

    Select the eligible recipient and issue the document

    Individual and bulk issue is part of the documented workflow.

  3. 03

    Review the generated certificate record

    Generated records is part of the documented workflow.

  4. 04

    Use the document verification token to check validity

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
typestringRequired by declaration
bodyHtmlstringOptional
paperSizestringOptional
isActivebooleanOptional
templateIdstringRequired by declaration
studentIdstringOptional
staffIdstringOptional
dataJsonRecord<string, unknown>Optional
itemsBulkGenerateItemDto[]Required by declaration

Rules & current limits

  • Verification requires an actual generated token. Sample demo certificates are not school-issued documents.

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

Institutions · Module guide

College administration

Manage department and semester structures, electives, internal marks, placements and research records.

College administration illustrated banner

Online guide · Guided demo

What you can do

01

Departments

02

Semesters

03

Electives and enrollment

04

Internal marks

05

Placements

06

Research projects

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
student:viewstudent:createstudent:updatestudent:delete

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

How the workflow works

  1. 01

    Create the department and semester structure

    An assigned school account with the required permissions.

  2. 02

    Offer electives with the required limits

    Semesters is part of the documented workflow.

  3. 03

    Record eligible enrollments and internal marks

    Electives and enrollment is part of the documented workflow.

  4. 04

    Maintain placement and research records

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
codestringRequired by declaration
hodStaffIdstringOptional
descriptionstringOptional
totalSeatsnumberOptional
departmentIdstringRequired by declaration
semesterNonumberRequired by declaration
typeSemesterTypeRequired by declaration
startDatestringOptional
endDatestringOptional
totalCreditsnumberOptional
isActivebooleanOptional
subjectIdstringRequired by declaration
semesterIdstringRequired by declaration
maxStudentsnumberOptional
creditsnumberOptional
teacherStaffIdstringOptional
statusstringOptional
electiveIdstringRequired by declaration
studentIdstringRequired by declaration
assignment1numberOptional
assignment2numberOptional
midSemnumberOptional
attendancenumberOptional

Rules & current limits

  • College workflows share the school account and permission context; college-specific setup must exist.

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

Community · Module guide

Notices, announcements & messages

Coordinate school notices, events, complaints, audience-based announcements and direct conversations.

Notices, announcements & messages illustrated banner

Online guide · Guided demo

What you can do

01

Notices and events

02

Announcement templates

03

Audience preview

04

Delivery report

05

Scoped messages

06

Complaints

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
communication:viewcommunication:createcommunication:updatecommunication:deletecommunication:manage

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

How the workflow works

  1. 01

    Choose the notice, announcement or conversation workflow

    An assigned school account with the required permissions.

  2. 02

    Select the permitted audience and prepare the content

    Announcement templates is part of the documented workflow.

  3. 03

    Preview reachability before sending where available

    Audience preview is part of the documented workflow.

  4. 04

    Review delivery reports, replies or complaint status

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
categorystringOptional
subjectstringOptional
bodystringRequired by declaration
channelsstring[]Optional
isActivebooleanOptional
audiencestringOptional
targetingAudienceTargetingDtoOptional
titlestringRequired by declaration
messagestringOptional
templateIdstringOptional
scheduledAtstringOptional
isPinnedbooleanOptional
classIdstringOptional
sectionIdstringOptional
expiresAtstringOptional
descriptionstringOptional
startAtstringRequired by declaration
endAtstringOptional
venuestringOptional
rsvpEnabledbooleanOptional
isAllDaybooleanOptional
prioritystringOptional
studentIdstringOptional

Rules & current limits

  • External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it.

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

Student care · Module guide

Discipline & behaviour

Record incidents, review student standing and manage sanctions through dedicated access.

Discipline & behaviour illustrated banner

Online guide · Guided demo

What you can do

01

Incident register

02

Watchlist

03

Policy thresholds

04

Sanctions

05

Student summary

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
discipline:viewdiscipline:managediscipline:updatediscipline:creatediscipline:delete

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

How the workflow works

  1. 01

    Locate the student within your permitted scope

    An assigned school account with the required permissions.

  2. 02

    Record the incident and relevant context

    Watchlist is part of the documented workflow.

  3. 03

    Review standing and any suggested threshold action

    Policy thresholds is part of the documented workflow.

  4. 04

    Schedule or close the appropriate sanction

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

Request fields to understand

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

FieldDeclared typeInput
windowDaysnumberOptional
warnAtnumberOptional
detentionAtnumberOptional
parentMeetingAtnumberOptional
suspensionReviewAtnumberOptional
notifyFamilyOnIncidentbooleanOptional
scheduledForstringRequired by declaration
notesstringOptional
servedbooleanRequired by declaration
reasonstringOptional
studentIdstringRequired by declaration
incidentDatestringRequired by declaration
categorystringOptional
descriptionstringRequired by declaration
severitystringOptional
actionTakenstringOptional
demeritPointsnumberOptional
statusstringOptional

Rules & current limits

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

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

Academics · Module guide

Examinations & results

Plan examinations and seating, record marks, review rechecks and publish report cards.

Examinations & results illustrated banner

Online guide · Guided demo

What you can do

01

Exam schedules

02

Marks entry and history

03

Completion status

04

Grade scales

05

Report cards

06

Publish and unpublish

07

Seating and invigilation

08

Adaptive exams

09

Mark rechecks

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
exam:viewexam:createexam:updateexam:deleteexam:manage

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

How the workflow works

  1. 01

    Create the exam and its subject schedules

    An assigned school account with the required permissions.

  2. 02

    Review the candidates, seating and completion status

    Marks entry and history is part of the documented workflow.

  3. 03

    Record and verify marks, then generate report cards

    Completion status is part of the documented workflow.

  4. 04

    Publish approved results; use the correction workflow when required

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
subjectIdstringRequired by declaration
classIdstringRequired by declaration
sectionIdstringOptional
targetCountnumberOptional
durationMinnumberOptional
maxAttemptsnumberOptional
questionIdsstring[]Optional
publishResultsbooleanOptional
textstringRequired by declaration
optionsstring[]Required by declaration
correctAnswerstringRequired by declaration
difficultystringOptional
chapterstringOptional
marksnumberOptional
statusstringOptional
namestringRequired by declaration
rowsnumberOptional
seatsPerRownumberOptional
blockedSeatsnumberOptional
buildingstringOptional
floorstringOptional
isActivebooleanOptional
scheduleIdstringRequired by declaration

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Finance · Module guide

Fee structures & collections

Configure charges, preview billing, issue invoices and record collections and adjustments.

Fee structures & collections illustrated banner

Online guide · Guided demo

What you can do

01

Fee types and structures

02

Billing preview

03

Invoice generation

04

Collections and receipts

05

Dues ageing

06

Concessions

07

Refunds and reversals

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
fee:viewfee:managefee:createfee:updatefee:delete

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

How the workflow works

  1. 01

    Create the required fee structure and installments

    An assigned school account with the required permissions.

  2. 02

    Preview eligible students and existing invoices

    Billing preview is part of the documented workflow.

  3. 03

    Generate invoices and record a valid collection

    Invoice generation is part of the documented workflow.

  4. 04

    Review the receipt, remaining balance and adjustment history

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

Request fields to understand

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

FieldDeclared typeInput
referencestringOptional
notestringOptional
amountnumberOptional
reasonstringRequired by declaration
namestringOptional
codestringOptional
isRecurringbooleanOptional
isOptionalbooleanOptional
classIdstringOptional
studentIdstringRequired by declaration
sessionIdstringOptional
itemsInvoiceItemInput[]Required by declaration
structureIdstringRequired by declaration
installmentNonumberOptional
sectionIdstringOptional
dueDatestringOptional
notesstringOptional
typestringRequired by declaration
valuenumberRequired by declaration
feeTypeIdstringOptional
isActivebooleanOptional
discountIdstringOptional
statusstringRequired by declaration
studentIdsstring[]Optional

Rules & current limits

  • A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation.

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

Student care · Module guide

Health records & infirmary

Maintain school health information and record infirmary visits, medication entries and closures.

Health records & infirmary illustrated banner

Online guide · Guided demo

What you can do

01

Health profiles

02

Emergency contact

03

Infirmary visits

04

Medication records

05

Frequent-visit review

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
health:viewhealth:update

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

How the workflow works

  1. 01

    Find the permitted student health profile

    An assigned school account with the required permissions.

  2. 02

    Review emergency and health information

    Emergency contact is part of the documented workflow.

  3. 03

    Record the infirmary visit and permitted medication details

    Infirmary visits is part of the documented workflow.

  4. 04

    Close the visit and review repeated visits where relevant

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

Request fields to understand

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

FieldDeclared typeInput
bloodGroupstringOptional
allergiesstringOptional
chronicConditionsstringOptional
medicationsstringOptional
emergencyContactNamestringOptional
emergencyContactPhonestringOptional
heightCmnumberOptional
weightKgnumberOptional
lastCheckupDatestringOptional
vaccinationJsonRecord<string, unknown>Optional
notesstringOptional
studentIdstringRequired by declaration
complaintstringRequired by declaration
observationsstringOptional
temperatureCnumberOptional
outcome'OPEN' | 'RETURNED_TO_CLASS' | 'RESTING' | 'SENT_HOME' | 'REFERRED_HOSPITAL'Required by declaration
treatmentstringOptional
medicinestringRequired by declaration
visitIdstringOptional
dosestringOptional
routestringOptional
consentSourcestringOptional

Rules & current limits

  • Access is restricted by dedicated health permissions. Sample walkthrough information is fictional and is not medical advice.

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

Campus · Module guide

Hostel, rooms & roll call

Manage residence capacity, room/bed allocations, visitor logs and nightly attendance.

Hostel, rooms & roll call illustrated banner

Online guide · Guided demo

What you can do

01

Hostels and rooms

02

Beds

03

Resident allocations

04

Visitor check-in/out

05

Night roll call

06

Missing residents

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
hostel:viewhostel:createhostel:updatehostel:delete

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

How the workflow works

  1. 01

    Set up the hostel, rooms and beds

    An assigned school account with the required permissions.

  2. 02

    Allocate eligible residents to available accommodation

    Beds is part of the documented workflow.

  3. 03

    Record and check out permitted visitors

    Resident allocations is part of the documented workflow.

  4. 04

    Open the roll call, mark residents and close the register

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
typestringOptional
wardenStaffIdstringOptional
addressstringOptional
hostelIdstringRequired by declaration
roomNostringRequired by declaration
floorstringOptional
capacitynumberOptional
farenumberOptional
roomIdstringRequired by declaration
bedNostringRequired by declaration
studentIdstringOptional
bedIdstringRequired by declaration
fromDatestringRequired by declaration
toDatestringOptional
visitorNamestringRequired by declaration
purposestringOptional
idProofstringOptional
outTimestringOptional
datestringOptional
marksResidentMarkDto[]Required by declaration
forcebooleanOptional
notesstringOptional

Rules & current limits

  • Capacity and allocation state must be reviewed before assignment. Family notification delivery depends on the available channel.

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

People · Module guide

Payroll & salary structures

Prepare salary structures, process payroll, review approvals and maintain salary slips.

Payroll & salary structures illustrated banner

Online guide · Guided demo

What you can do

01

Salary structures

02

Payroll processing

03

Approval

04

Mark paid

05

Salary slips

06

PDF generation

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
payroll:viewpayroll:createpayroll:updatepayroll:deletepayroll:manage

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

How the workflow works

  1. 01

    Create the applicable salary structure

    An assigned school account with the required permissions.

  2. 02

    Process payroll for the selected period

    Payroll processing is part of the documented workflow.

  3. 03

    Review calculations and approve the run

    Approval is part of the documented workflow.

  4. 04

    Record payment status and review salary slips

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
staffIdstringOptional
basicnumberRequired by declaration
componentsJsonSalaryComponentDto[]Optional
ctcnumberOptional
effectiveFromstringOptional
isActivebooleanOptional
monthnumberRequired by declaration
yearnumberRequired by declaration
applyLossOfPaybooleanOptional
paidDaysnumberOptional
loanRecoverynumberOptional
taxnumberOptional

Rules & current limits

  • Marking payroll paid records an administrative state; this feature does not by itself transfer money to a bank.

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

Campus · Module guide

Inventory & purchases

Manage supplies, procurement, stock movements and issued school property.

Inventory & purchases illustrated banner

Online guide · Guided demo

What you can do

01

Items and vendors

02

Purchase orders

03

Approval and partial receipt

04

Stock transactions

05

Low stock

06

Asset issue/return

07

History and export

Access & 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.
Required permission keys
inventory:viewinventory:createinventory:updateinventory:manage

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

How the workflow works

  1. 01

    Create an item and supplier with the relevant stock unit

    An assigned school account with the required permissions.

  2. 02

    Prepare and submit a purchase order for review

    Purchase orders is part of the documented workflow.

  3. 03

    Receive accepted quantities and inspect stock movements

    Approval and partial receipt is part of the documented workflow.

  4. 04

    Issue or return property and review outstanding balances

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
categorystringOptional
skustringOptional
unitstringOptional
quantitynumberRequired by declaration
reorderLevelnumberOptional
unitPricenumberOptional
contactstringOptional
phonestringOptional
emailstringOptional
gstinstringOptional
addressstringOptional
poNumberstringRequired by declaration
vendorIdstringRequired by declaration
expectedAtstringOptional
notesstringOptional
itemsInvPoLineDto[]Required by declaration
idstringOptional
versionstringOptional
reasonstringOptional
actionstringRequired by declaration
referencestringRequired by declaration
linesInvReceiveLineDto[]Required by declaration
itemIdstringRequired by declaration

Rules & current limits

  • Purchase totals exclude tax/freight and supplier accounting. Valuation uses reference prices, not FIFO or weighted-average accounting.

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

People · Module guide

Staff leave & student absences

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

Staff leave & student absences illustrated banner

Online guide · Guided demo

What you can do

01

Self-service staff leave

02

Pending review

03

Approve or reject

04

Student absence report

05

Approval and cancellation

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose staff leave or student absence reporting

    An assigned school account with the required permissions.

  2. 02

    Enter the applicable dates and reason

    Pending review is part of the documented workflow.

  3. 03

    Submit or review through the permitted role

    Approve or reject is part of the documented workflow.

  4. 04

    Check the final decision and attendance impact

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

Request fields to understand

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

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

Rules & current limits

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

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

Finance · Module guide

General ledger

Maintain account records and post balanced double-entry journals with auditable reversals.

General ledger illustrated banner

Online guide · Guided demo

What you can do

01

Chart of accounts

02

Balanced journals

03

Journal reversal

04

Trial balance

05

Income statement

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review or seed the chart of accounts

    An assigned school account with the required permissions.

  2. 02

    Prepare matching debit and credit lines

    Balanced journals is part of the documented workflow.

  3. 03

    Post the balanced journal and inspect its record

    Journal reversal is part of the documented workflow.

  4. 04

    Use a reversal to correct an entry without erasing the original

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
codestringOptional
typestringRequired by declaration
parentIdstringOptional
isPostablebooleanOptional
isActivebooleanOptional
linesJournalLineDto[]Required by declaration
entryDatestringOptional
narrationstringOptional
sourcestringOptional
sourceRefstringOptional

Rules & current limits

  • Debits and credits must balance. Ledger recording is not a bank settlement or a statutory filing.

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

Campus · Module guide

Library & circulation

Maintain titles and copies, lend books, manage reservations and handle fines.

Library & circulation illustrated banner

Online guide · Guided demo

What you can do

01

Book catalogue

02

Copy availability

03

Issue and return

04

Renewal

05

Reservations

06

Library policy

07

Fine collection and waiver

Access & 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.
Required permission keys
library:viewlibrary:createlibrary:updatelibrary:deletelibrary:manage

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

How the workflow works

  1. 01

    Create a title and its physical copies

    An assigned school account with the required permissions.

  2. 02

    Check borrower eligibility and issue an available copy

    Copy availability is part of the documented workflow.

  3. 03

    Return or renew the loan and review reservations

    Issue and return is part of the documented workflow.

  4. 04

    Review overdue items and any permitted fine action

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
authorstringOptional
publisherstringOptional
isbnstringOptional
categorystringOptional
editionstringOptional
rackNostringOptional
pricenumberOptional
idstringOptional
versionstringOptional
reasonstringOptional
bookIdstringRequired by declaration
barcodestringRequired by declaration
statusstringOptional
copyIdstringRequired by declaration
dueDatestringOptional
conditionstringRequired by declaration
additionalChargenumberOptional
loanDaysnumberOptional
finePerDaynumberOptional
graceDaysnumberOptional
maxBooksPerBorrowernumberOptional
maxFinePerIssuenumberOptional
blockIssueOverDuesnumberOptional

Rules & current limits

  • Availability, borrower policy and reservation rules affect issue/renewal. A fine record is distinct from a fee gateway payment.

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

Academics · Module guide

Live classes & recordings

Schedule live lessons, manage their lifecycle and maintain recordings where configured.

Live classes & recordings illustrated banner

Online guide · Guided demo

What you can do

01

Class schedule

02

Start and end

03

Learner join view

04

Recording upload

05

Chunk finalize and recovery

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
live-class:viewlive-class:createlive-class:updatelive-class:delete

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

How the workflow works

  1. 01

    Create the class for the intended learners

    An assigned school account with the required permissions.

  2. 02

    Review the scheduled time and class details

    Start and end is part of the documented workflow.

  3. 03

    Start the class and use the available joining experience

    Learner join view is part of the documented workflow.

  4. 04

    End the session and review an available recording

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

Request fields to understand

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

FieldDeclared typeInput
titlestringOptional
classIdstringRequired by declaration
sectionIdstringOptional
subjectIdstringOptional
scheduledAtstringOptional
durationMinnumberOptional

Rules & current limits

  • Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity.

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

Academics · Module guide

Courses & lessons

Build a course structure and let learners open lessons and record progress.

Courses & lessons illustrated banner

Online guide · Guided demo

What you can do

01

Course catalogue

02

Modules

03

Lessons

04

Video assets

05

Publishing

06

Learner progress

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
lms:viewlms:createlms:updatelms:delete

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

How the workflow works

  1. 01

    Create a course and its details

    An assigned school account with the required permissions.

  2. 02

    Add modules and lessons in the intended order

    Modules is part of the documented workflow.

  3. 03

    Attach supported learning media and review visibility

    Lessons is part of the documented workflow.

  4. 04

    Open the learner course view and track lesson progress

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
descriptionstringOptional
subjectIdstringOptional
classIdstringOptional
isPublishedbooleanOptional
sortOrdernumberOptional
contentTypestringRequired by declaration
videoUrlstringOptional
bodystringOptional
durationMinnumberOptional

Rules & 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.

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

Growth · Module guide

Marketing & conversion workspace

Connect the public AVKUL ERP website with enquiries, campaign performance, content management and follow-up work.

Marketing & conversion workspace illustrated banner

Online guide · Guided demo

What you can do

01

Demo CRM

02

Demo calendar and tasks

03

Campaign Manager

04

Website analytics

05

Landing Page CMS

06

Media Library

Access & setup

Intended access: Platform administrator.

  • A platform administrator account.
  • The academic, student or staff setup used by this workflow.

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

How the workflow works

  1. 01

    Publish reviewed landing content and choose its media

    A platform administrator account.

  2. 02

    Create a trackable campaign link

    Demo calendar and tasks is part of the documented workflow.

  3. 03

    Review accepted walkthrough enquiries in CRM

    Campaign Manager is part of the documented workflow.

  4. 04

    Schedule demos and follow-ups and monitor measured conversion

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

Request fields to understand

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

FieldDeclared typeInput
contentRecord<string,unknown>Required by declaration
draftIdstringRequired by declaration
revisionIdstringRequired by declaration
sourcestringRequired by declaration
mediumstringRequired by declaration
versionnumberRequired by declaration
statusstringRequired by declaration
assignedToIdstring|nullOptional
followUpAtstring | nullOptional
demoAtstring | nullOptional
notestringOptional
namestringRequired by declaration
titlestringRequired by declaration
altTextstringRequired by declaration
folderIdstring|nullRequired by declaration
xnumberRequired by declaration
ynumberRequired by declaration
widthnumberRequired by declaration
heightnumberRequired by declaration
dueAtstringRequired by declaration
prioritystringRequired by declaration
leadIdstring|nullOptional
actionstringRequired by declaration
atstringOptional

Rules & 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.

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

Family portal · Module guide

Family & personal workspace

Let families, learners and staff see only their linked children or personal records.

Family & personal workspace illustrated banner

Online guide · Guided demo

What you can do

01

Linked children

02

Attendance and fees

03

Published results

04

Homework and courses

05

Timetable

06

Library

07

PTM

08

Transport

09

Personal documents

Access & 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.

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

How the workflow works

  1. 01

    Sign in with the assigned account

    An assigned school account with the required permissions.

  2. 02

    Select the linked child where a selector is available

    Attendance and fees is part of the documented workflow.

  3. 03

    Open the relevant learning or school-service screen

    Published results is part of the documented workflow.

  4. 04

    Review the record or complete the permitted self-service action

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

Request fields to understand

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

FieldDeclared typeInput
tokenstringRequired by declaration
platformstringRequired by declaration
studentIdstringOptional
interestsstringOptional
psychometricRecord<string, number>Optional
opportunityTypestringOptional
interestAreastringOptional

Rules & current limits

  • Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls.

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

Finance · Module guide

Online payments & reconciliation

Create gateway orders, verify callbacks and investigate payments that remain pending.

Online payments & reconciliation illustrated banner

Online guide · Guided demo

What you can do

01

Payment orders

02

Callback verification

03

Pending payment review

04

Reconciliation

05

Gateway connection check

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
fee:viewfee:managefee:create

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

How the workflow works

  1. 01

    Review the invoice and provider readiness

    An assigned school account with the required permissions.

  2. 02

    Create an order through the permitted checkout workflow

    Callback verification is part of the documented workflow.

  3. 03

    Verify the gateway response before treating the invoice as paid

    Pending payment review is part of the documented workflow.

  4. 04

    Investigate a pending payment through reconciliation

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

Request fields to understand

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

FieldDeclared typeInput
abandonbooleanOptional
reasonstringOptional
invoiceIdstringRequired by declaration
amountnumberOptional
paymentIdstringRequired by declaration
razorpayPaymentIdstringOptional
razorpaySignaturestringOptional

Rules & current limits

  • External collection requires approved gateway credentials and verified callbacks. The public guided demo does not charge money.

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

Administration · Module guide

Notifications & integrations

Review notifications, integration settings, webhook records and shared AI request state.

Notifications & integrations illustrated banner

Online guide · Guided demo

What you can do

01

In-app notifications

02

Integration status

03

Integration configuration

04

Webhooks

05

AI requests

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
dashboard:viewcommunication:createsettings:viewsettings:createsettings:updatesettings:delete

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

How the workflow works

  1. 01

    Open the relevant integration or notification view

    An assigned school account with the required permissions.

  2. 02

    Review status and permitted settings

    Integration status is part of the documented workflow.

  3. 03

    Configure a provider using approved credentials outside public documentation

    Integration configuration is part of the documented workflow.

  4. 04

    Use a controlled test and inspect the actual result

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
bodystringOptional
userIdstringOptional
channelstringOptional
dataJsonRecord<string, unknown>Optional
featurestringRequired by declaration
providerstringRequired by declaration
modelstringOptional
promptJsonRecord<string, unknown>Optional
responseJsonRecord<string, unknown>Optional
promptTokensnumberOptional
completionTokensnumberOptional
statusstringOptional
errorMessagestringOptional
promptstringRequired by declaration
categorystringOptional
configJsonRecord<string, unknown>Optional
secretsRefstringOptional
isActivebooleanOptional
integrationIdstringOptional
eventstringRequired by declaration
targetUrlstringRequired by declaration
secretstringOptional

Rules & current limits

  • Saving settings is not proof of external delivery. No credential values are included in this documentation.

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

School office · Module guide

Year-end rollover

Preview new-session student placement and apply or revert a recorded promotion batch.

Year-end rollover illustrated banner

Online guide · Guided demo

What you can do

01

Rollover preview

02

Structure clone

03

Promotion commit

04

Batch history

05

Revert

06

Enrollment history

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
promotion:viewpromotion:createpromotion:managepromotion:deletestudent:view

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

How the workflow works

  1. 01

    Choose the source and target academic sessions

    An assigned school account with the required permissions.

  2. 02

    Clone or prepare the target class structure

    Structure clone is part of the documented workflow.

  3. 03

    Review the dry-run placement and exceptions

    Promotion commit is part of the documented workflow.

  4. 04

    Commit only the reviewed batch and keep its reversal reference

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

Request fields to understand

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

FieldDeclared typeInput
fromSessionIdstringRequired by declaration
toSessionIdstringRequired by declaration
criteriaPromotionCriteriaDtoOptional
includeTimetablesbooleanOptional
decisionsStudentDecisionDto[]Required by declaration
activateTargetSessionbooleanOptional
notesstringOptional
graduationYearnumberOptional

Rules & current limits

  • Preview writes nothing; commit changes enrollment. Locked sessions and school ownership checks still apply.

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

Community · Module guide

Parent–teacher meetings

Publish meeting slots, book families, record discussion outcomes and manage follow-up tasks.

Parent–teacher meetings illustrated banner

Online guide · Guided demo

What you can do

01

Teacher slots

02

Family bookings

03

Reschedule and cancel

04

Meeting notes

05

Family-visible follow-ups

06

In-app reminders

Access & 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.
Required permission keys
communication:viewcommunication:createcommunication:deletecommunication:update

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

How the workflow works

  1. 01

    Create or choose the permitted teacher meeting slot

    An assigned school account with the required permissions.

  2. 02

    Book the linked child and verify availability

    Family bookings is part of the documented workflow.

  3. 03

    Record the meeting outcome with the correct note visibility

    Reschedule and cancel is part of the documented workflow.

  4. 04

    Assign and complete any follow-up action

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

Request fields to understand

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

FieldDeclared typeInput
idstringOptional
staffIdstringRequired by declaration
datestringRequired by declaration
startTimestringRequired by declaration
endTimestringRequired by declaration
capacitynumberOptional
locationstringOptional
isActivebooleanOptional
versionstringOptional
slotIdstringRequired by declaration
studentIdstringRequired by declaration
notesstringOptional
statusstringRequired by declaration
reasonstringOptional
privateNotesstringOptional
feedbackstringOptional
bookingIdstringRequired by declaration
titlestringRequired by declaration
owner"SCHOOL" | "FAMILY"Required by declaration
dueDatestringOptional
forcebooleanOptional
parentIdstringOptional

Rules & current limits

  • Private staff notes and family-visible notes differ. Reminder actions do not guarantee external SMS, email or push delivery.

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

Finance · Module guide

School reports

Review fee summaries, student distribution and examination summaries from permitted school data.

School reports illustrated banner

Online guide · Guided demo

What you can do

01

Fee summary

02

Students by class

03

Exam summary

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
report:view

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

How the workflow works

  1. 01

    Choose the report and reporting context

    An assigned school account with the required permissions.

  2. 02

    Inspect the totals and available filters

    Students by class is part of the documented workflow.

  3. 03

    Compare the summary with the underlying records

    Exam summary is part of the documented workflow.

  4. 04

    Use the available export or print action when present

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

Rules & current limits

  • A summary is only as current as the entered records. Each report uses its implemented date and scope rules.

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

Platform · Module guide

Platform administration

Manage tenants, schools, plans, subscriptions, billing and cross-tenant reporting.

Platform administration illustrated banner

Online guide · Guided demo

What you can do

01

Tenant onboarding

02

Schools and quotas

03

Plans and module toggles

04

Subscriptions

05

Invoices and coupons

06

Analytics and reports

07

Usage

08

Audit and support

Access & setup

Intended access: Platform administrator.

  • A platform administrator account.
  • The academic, student or staff setup used by this workflow.

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

How the workflow works

  1. 01

    Select the tenant or platform overview

    A platform administrator account.

  2. 02

    Review plan, subscription, usage and school details

    Schools and quotas is part of the documented workflow.

  3. 03

    Apply an authorized administrative action

    Plans and module toggles is part of the documented workflow.

  4. 04

    Review the resulting invoice, audit or report

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

Request fields to understand

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

FieldDeclared typeInput
codestringRequired by declaration
descriptionstringOptional
typestringOptional
valuenumberRequired by declaration
maxRedemptionsnumberOptional
validFromstringOptional
validUntilstringOptional
isActivebooleanOptional
questionstringRequired by declaration
planCodestringOptional
amountnumberOptional
paymentLogIdstringRequired by declaration
razorpayPaymentIdstringOptional
razorpaySignaturestringOptional
namestringRequired by declaration
billingCyclestringOptional
priceMonthlynumberOptional
priceYearlynumberOptional
trialDaysnumberOptional
maxStudentsnumberOptional
maxStaffnumberOptional
maxSchoolsnumberOptional
maxBranchesnumberOptional
isPublicbooleanOptional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

School office · Module guide

School dashboard & branches

See school-wide priorities and manage the campus context used by the ERP.

School dashboard & branches illustrated banner

Online guide · Guided demo

What you can do

01

Overview metrics

02

Daily Action Center

03

School profile

04

Branch counts

05

Campus creation and update

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
dashboard:viewsettings:createsettings:updatesettings:delete

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

How the workflow works

  1. 01

    Review the school dashboard and current session

    An assigned school account with the required permissions.

  2. 02

    Open an outstanding action in the relevant module

    Daily Action Center is part of the documented workflow.

  3. 03

    Inspect the campus counts and permitted branch settings

    School profile is part of the documented workflow.

  4. 04

    Review the consequences before closing a campus

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

Request fields to understand

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

FieldDeclared typeInput
codestringRequired by declaration
namestringRequired by declaration
addressLine1stringOptional
citystringOptional
phonestringOptional
isMainbooleanOptional

Rules & current limits

  • Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow.

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

People · Module guide

Staff directory & lifecycle

Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement.

Staff directory & lifecycle illustrated banner

Online guide · Guided demo

What you can do

01

Directory

02

Staff creation

03

Profile 360

04

Clearance

05

Offboarding

06

Reinstatement

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Find or create the staff profile

    An assigned school account with the required permissions.

  2. 02

    Review employment details and linked responsibilities

    Staff creation is part of the documented workflow.

  3. 03

    Inspect clearance before offboarding

    Profile 360 is part of the documented workflow.

  4. 04

    Use reinstatement when returning a former staff member

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

Request fields to understand

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

FieldDeclared typeInput
employeeCodestringRequired by declaration
firstNamestringRequired by declaration
lastNamestringOptional
genderstringOptional
dateOfBirthstringOptional
emailstringOptional
phonestringOptional
branchIdstringOptional
departmentIdstringOptional
designationIdstringOptional
reportsToIdstringOptional
joiningDatestringOptional
contractTypestringOptional
qualificationsunknownOptional
exitStatus'RESIGNED' | 'TERMINATED' | 'RETIRED'Optional
exitDatestringOptional
reasonstringOptional
forcebooleanOptional

Rules & current limits

  • Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action.

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

People · Module guide

Staff attendance

Record staff check-in/out and maintain an administrative daily and monthly register.

Staff attendance illustrated banner

Online guide · Guided demo

What you can do

01

Own attendance

02

Check-in/out

03

Daily roster

04

Corrections

05

Monthly register

06

Holiday marking

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Check the current personal attendance state

    An assigned school account with the required permissions.

  2. 02

    Clock in or out through the self-service action

    Check-in/out is part of the documented workflow.

  3. 03

    Use the authorized daily roster to correct records

    Daily roster is part of the documented workflow.

  4. 04

    Review the monthly register and holiday policy

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

Request fields to understand

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

FieldDeclared typeInput
latnumberOptional
lngnumberOptional
remarkstringOptional
datestringRequired by declaration
recordsStaffAttendanceInput[]Required by declaration
forcebooleanOptional
fromstringRequired by declaration
tostringRequired by declaration

Rules & current limits

  • Self-service acts on the caller’s staff profile. Administrative corrections need separate access.

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

School office · Module guide

Student records & lifecycle

Maintain student profiles, guardians and documents, and manage campus release or school exit.

Student records & lifecycle illustrated banner

Online guide · Guided demo

What you can do

01

Student directory

02

Profile 360

03

Guardians

04

Document review

05

Gate passes

06

Exit clearance

07

Transfer certificates

08

Readmission

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
student:viewstudent:updatestudent:managestudent:deletestudent:createstudent-exit:viewstudent-exit:createstudent-exit:manage

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

How the workflow works

  1. 01

    Create or open the student profile

    An assigned school account with the required permissions.

  2. 02

    Review guardian contacts and required documents

    Profile 360 is part of the documented workflow.

  3. 03

    Use the gate-pass workflow for an authorized early release

    Guardians is part of the documented workflow.

  4. 04

    Use clearance and exit workflows for withdrawal or transfer

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

Request fields to understand

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

FieldDeclared typeInput
studentIdstringRequired by declaration
reasonstringOptional
expectedOutAtstringOptional
expectedBackAtstringOptional
releaseToNamestringOptional
releaseToGuardianIdstringOptional
approvebooleanRequired by declaration
guardianIdstringOptional
releaseRelationstringOptional
overrideReasonstringOptional
notesstringOptional
typestringRequired by declaration
titlestringOptional
expiresAtstringOptional
firstNamestringRequired by declaration
middleNamestringOptional
lastNamestringOptional
admissionNostringRequired by declaration
rollNostringOptional
genderstringOptional
dateOfBirthstringOptional
bloodGroupstringOptional
sessionIdstringOptional
classIdstringOptional

Rules & current limits

  • Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record.

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

Finance · Module guide

Tally export

Prepare accounting vouchers for the configured Tally integration.

Tally export illustrated banner

Online guide · Guided demo

What you can do

01

Connection test

02

Voucher export

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
settings:viewfee:export

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

How the workflow works

  1. 01

    Review the accounting data and integration settings

    An assigned school account with the required permissions.

  2. 02

    Check the configured connection in a controlled environment

    Voucher export is part of the documented workflow.

  3. 03

    Export the selected voucher records

    Voucher export is part of the documented workflow.

  4. 04

    Reconcile the receiving system with the exported result

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

Request fields to understand

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

FieldDeclared typeInput
fromDatestringRequired by declaration
toDatestringRequired by declaration
pushToTallybooleanOptional

Rules & current limits

  • An export endpoint does not prove that a live Tally instance is connected or that vouchers were imported successfully.

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

People · Module guide

Staff tasks

Assign work to school staff and let each user complete their own task list.

Staff tasks illustrated banner

Online guide · Guided demo

What you can do

01

Administrative task list

02

Create and edit

03

My tasks

04

Completion

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create a task with the intended staff assignment

    An assigned school account with the required permissions.

  2. 02

    Review its due date and current state

    Create and edit is part of the documented workflow.

  3. 03

    The assigned user opens their own task queue

    My tasks is part of the documented workflow.

  4. 04

    Complete the task and review the updated record

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

Request fields to understand

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

FieldDeclared typeInput
titlestringOptional
descriptionstringOptional
assignedToIdstringOptional
dueDatestringOptional
prioritystringOptional
categorystringOptional
checklistChecklistItemDto[]Optional
statusstringOptional

Rules & current limits

  • School staff tasks are separate from the platform marketing Demo & Follow-up Workspace.

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

Academics · Module guide

Timetable & teacher cover

Build recurring class schedules and arrange dated teacher cover with clash checks.

Timetable & teacher cover illustrated banner

Online guide · Guided demo

What you can do

01

Weekly and daily views

02

Class and teacher filters

03

Periods and rooms

04

Time-overlap checks

05

Dated cover

06

Availability review

07

History and print

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
timetable:viewtimetable:createtimetable:deletetimetable:update

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

How the workflow works

  1. 01

    Select the section, teacher and date

    An assigned school account with the required permissions.

  2. 02

    Create a period with its subject, time and room

    Class and teacher filters is part of the documented workflow.

  3. 03

    Resolve overlap warnings before saving

    Periods and rooms is part of the documented workflow.

  4. 04

    Arrange dated cover and review the daily plan

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

Request fields to understand

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

FieldDeclared typeInput
versionstringOptional
periodIdstringRequired by declaration
datestringRequired by declaration
substituteStaffIdstringRequired by declaration
reasonstringOptional
status'PLANNED' | 'CONFIRMED' | 'CANCELLED'Required by declaration
sectionIdstringRequired by declaration
dayOfWeeknumberRequired by declaration
periodNonumberRequired by declaration
startTimestringRequired by declaration
endTimestringRequired by declaration
subjectIdstringOptional
teacherStaffIdstringOptional
roomNostringOptional
periodTypestringOptional
forcebooleanOptional
absentStaffIdstringRequired by declaration
applybooleanOptional
autoGeneratedbooleanOptional

Rules & current limits

  • Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view.

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

Campus · Module guide

Transport operations

Manage buses, routes, stops and student allocations, then run daily boarding registers.

Transport operations illustrated banner

Online guide · Guided demo

What you can do

01

Fleet and capacity

02

Routes and stops

03

Pickup/drop allocations

04

Trip start and completion

05

Boarding corrections

06

Family bus view

07

Fuel and recorded locations

Access & 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.
Required permission keys
transport:viewtransport:createtransport:deletetransport:update

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

How the workflow works

  1. 01

    Set up the bus, route and ordered stops

    An assigned school account with the required permissions.

  2. 02

    Allocate students within the directional seat capacity

    Routes and stops is part of the documented workflow.

  3. 03

    Start today’s trip and record boarding/drop-off

    Pickup/drop allocations is part of the documented workflow.

  4. 04

    Complete the run and review family-visible updates

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

Request fields to understand

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

FieldDeclared typeInput
regNostringRequired by declaration
modelstringOptional
capacitynumberOptional
driverStaffIdstringOptional
helperStaffIdstringOptional
isActivebooleanOptional
namestringRequired by declaration
vehicleIdstringRequired by declaration
routeIdstringRequired by declaration
sequencenumberOptional
pickupTimestringOptional
dropTimestringOptional
studentIdstringRequired by declaration
stopIdstringOptional
directionstringOptional
idstringOptional
versionstringOptional
datestringRequired by declaration
statusstringRequired by declaration
notestringOptional
reasonstringOptional
notesstringOptional
marksBoardingMarkDto[]Required by declaration
forcebooleanOptional

Rules & 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.

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

Institutions · Module guide

Tuition batches & demos

Manage tuition subjects, teaching batches, student enrollment and prospective demo classes.

Tuition batches & demos illustrated banner

Online guide · Guided demo

What you can do

01

Subjects

02

Batches

03

Enrollment

04

Prospect demos

05

Progress reports

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
student:viewstudent:createstudent:updatestudent:delete

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

How the workflow works

  1. 01

    Create the subject and teaching batch

    An assigned school account with the required permissions.

  2. 02

    Enroll the eligible student with the applicable terms

    Batches is part of the documented workflow.

  3. 03

    Schedule and review prospective demo classes

    Enrollment is part of the documented workflow.

  4. 04

    Maintain progress reports and enrollment state

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
subjectIdstringRequired by declaration
teacherStaffIdstringOptional
typeBatchTypeOptional
startDatestringRequired by declaration
endDatestringOptional
maxStudentsnumberOptional
monthlyFeenumberOptional
schedulestringOptional
roomNostringOptional
statusDemoStatusOptional
batchIdstringRequired by declaration
studentIdstringRequired by declaration
enrolledAtstringOptional
discountAmountnumberOptional
notesstringOptional
isActivebooleanOptional
prospectNamestringRequired by declaration
prospectPhonestringRequired by declaration
prospectEmailstringOptional
scheduledAtstringOptional
feedbackNotesstringOptional
convertedbooleanOptional
convertedStudentIdstringOptional

Rules & current limits

  • Tuition prospect demos are distinct from the platform’s AVKUL ERP product demos.

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

Websites · Module guide

School website CMS

Manage school themes, content pages and published website information from the ERP.

School website CMS illustrated banner

Online guide · Guided demo

What you can do

01

Themes

02

Theme activation

03

Page content

04

Draft and publish

05

Public school pages

06

Branding and contact

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
website:viewwebsite:createwebsite:updatewebsite:delete

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

How the workflow works

  1. 01

    Review the school website theme and branding

    An assigned school account with the required permissions.

  2. 02

    Create or edit the intended content page

    Theme activation is part of the documented workflow.

  3. 03

    Preview and check the content and contact information

    Page content is part of the documented workflow.

  4. 04

    Publish the page and review the public school URL

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
configJsonRecord<string, unknown>Optional
isActivebooleanOptional
slugstringRequired by declaration
titlestringRequired by declaration
typestringOptional
themeIdstringOptional
contentJsonRecord<string, unknown>Optional
seoJsonRecord<string, unknown>Optional
sortOrdernumberOptional
statusstringRequired by declaration

Rules & current limits

  • School website content is separate from the platform marketing Landing Page CMS. Publish controls use school ownership and permissions.

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

People · Module guide

Approval workflows

Configure approval chains and let the responsible approver act on the current step.

Approval workflows illustrated banner

Online guide · Guided demo

What you can do

01

Workflow definitions

02

Approval steps

03

Pending for me

04

Instance detail

05

Approve/reject

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
settings:viewsettings:createsettings:updatesettings:delete

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

How the workflow works

  1. 01

    Create a workflow definition and its ordered steps

    An assigned school account with the required permissions.

  2. 02

    Review the workflow linked to the business record

    Approval steps is part of the documented workflow.

  3. 03

    The current approver opens their pending queue

    Pending for me is part of the documented workflow.

  4. 04

    Record the decision and inspect the next step

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

Request fields to understand

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

FieldDeclared typeInput
decision'APPROVED' | 'REJECTED'Required by declaration
remarkstringOptional
namestringOptional
entityTypestringRequired by declaration
descriptionstringOptional
stepsWorkflowStepDto[]Optional
isActivebooleanOptional

Rules & current limits

  • Approval is limited to the current eligible approver; it is separate from directly editing the source business record.

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

Family portal · Family guide

Ask School Copilot

Ask a school-related question within the signed-in family’s permitted context.

Ask School Copilot illustrated banner

Online guide · Guided demo

What you can do

01

Question input

02

Answer review

03

Provider-dependent assistance

Access & 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.

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

How the workflow works

  1. 01

    Select the linked child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Enter a school-related question

    Answer review is part of the documented workflow.

  3. 03

    Review the answer and verify important details with the school

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

Rules & 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.

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

Family portal · Family guide

My attendance

Review daily and calendar attendance for the selected learner.

My attendance illustrated banner

Online guide · Guided demo

What you can do

01

Child selector

02

Attendance calendar

03

Summary and counting policy

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Inspect the attendance period and status

    Attendance calendar is part of the documented workflow.

  3. 03

    Review the counting explanation and query the school about corrections

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

Rules & 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.

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

Family portal · Family guide

My child’s bus

View assigned routes, stops, schedules and recorded trip status for your child.

My child’s bus illustrated banner

Online guide · Guided demo

What you can do

01

Assigned bus and route

02

Pickup/drop stop

03

Today’s boarding status

04

Trip history

Access & 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.

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

How the workflow works

  1. 01

    Select your child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review the bus, route and stop schedule

    Pickup/drop stop is part of the documented workflow.

  3. 03

    Check the recorded trip status and latest available history

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

Rules & 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.

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

Family portal · Family guide

Family complaints

Submit a school complaint and review the visible responses or status.

Family complaints illustrated banner

Online guide · Guided demo

What you can do

01

Complaint list

02

New complaint

03

Status review

Access & 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.

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

How the workflow works

  1. 01

    Review your existing complaints

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Enter the subject and relevant details

    New complaint is part of the documented workflow.

  3. 03

    Submit and review the recorded status

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

Rules & 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.

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

Family portal · Family guide

Online exam attempts

Open an eligible adaptive exam, answer questions and submit the learner’s attempt.

Online exam attempts illustrated banner

Online guide · Guided demo

What you can do

01

Available exams

02

Start attempt

03

Answer selection

04

Submit attempt

05

Attempt result

Access & 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.

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

How the workflow works

  1. 01

    Select an available exam for the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Start the attempt and answer the questions

    Start attempt is part of the documented workflow.

  3. 03

    Review answers before submitting

    Answer selection is part of the documented workflow.

  4. 04

    Inspect the available completion result

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

Rules & 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.

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

Family portal · Family guide

Learning explanations

Request and review a topic explanation in the available language options.

Learning explanations illustrated banner

Online guide · Guided demo

What you can do

01

Topic input

02

Language selection

03

Explanation history

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked learner and topic

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Select the intended language

    Language selection is part of the documented workflow.

  3. 03

    Review the generated explanation before using it

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

Rules & 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.

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

Family portal · Family guide

My fee invoices & receipts

Review invoices, outstanding balances and recorded receipts for your linked child.

My fee invoices & receipts illustrated banner

Online guide · Guided demo

What you can do

01

Child-specific invoices

02

Payment history

03

Receipt access

Access & 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.

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

How the workflow works

  1. 01

    Select your child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Open the relevant invoice and balance

    Payment history is part of the documented workflow.

  3. 03

    Review the available payment history or receipt

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

Rules & 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.

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

Family portal · Family guide

My homework & learning history

Read assigned class work, submit supported work and review feedback for the selected learner.

My homework & learning history illustrated banner

Online guide · Guided demo

What you can do

01

Assignment list

02

Due dates

03

Supported attachments

04

Submission

05

Feedback and history

Access & 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.

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

How the workflow works

  1. 01

    Choose your child and open an assignment

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Read the instructions and due date

    Due dates is part of the documented workflow.

  3. 03

    Attach or enter the permitted submission

    Supported attachments is part of the documented workflow.

  4. 04

    Review teacher feedback and learning history

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

Rules & 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.

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

Family portal · Family guide

My learning journey

Review the learner’s progress story and available next actions.

My learning journey illustrated banner

Online guide · Guided demo

What you can do

01

Progress story

02

Next actions

03

Learner context

Access & 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.

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

How the workflow works

  1. 01

    Select the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Read the available progress story

    Next actions is part of the documented workflow.

  3. 03

    Open a suggested next action and review the related record

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

Request fields to understand

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

FieldDeclared typeInput
studentIdstringOptional
interestsstringOptional
psychometricRecord<string, number>Optional
opportunityTypestringOptional
interestAreastringOptional

Rules & 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.

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

Family portal · Family guide

My learning path

Review available focus areas and update the permitted learning-path item state.

My learning path illustrated banner

Online guide · Guided demo

What you can do

01

Focus areas

02

Suggested activities

03

Progress updates

Access & 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.

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

How the workflow works

  1. 01

    Select the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review the available focus areas

    Suggested activities is part of the documented workflow.

  3. 03

    Complete a suggested activity and update its permitted state

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

Rules & 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.

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

Family portal · Family guide

Report an absence

Report an absence for your linked child and review the school’s decision.

Report an absence illustrated banner

Online guide · Guided demo

What you can do

01

Own absence reports

02

Dates and reason

03

Decision status

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Enter the absence dates and reason

    Dates and reason is part of the documented workflow.

  3. 03

    Submit the report and review its status

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

Rules & 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.

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

Family portal · Family guide

My library loans & reservations

Review your linked learner’s loans and use available renewal or reservation actions.

My library loans & reservations illustrated banner

Online guide · Guided demo

What you can do

01

My loans

02

Due dates

03

Reservations

04

Permitted renewal

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review issued books and due dates

    Due dates is part of the documented workflow.

  3. 03

    Renew or reserve an eligible title where allowed

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

Rules & 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.

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

Family portal · Family guide

My live classes

Review the learner’s available live lesson schedule and open a class detail.

My live classes illustrated banner

Online guide · Guided demo

What you can do

01

Assigned class list

02

Schedule

03

Class detail

Access & 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.

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

How the workflow works

  1. 01

    Choose the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review the available class schedule

    Schedule is part of the documented workflow.

  3. 03

    Open the intended class and joining details

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

Rules & 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.

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

Family portal · Family guide

Join a live class

Open an eligible live class and use its available live or recorded lesson experience.

Join a live class illustrated banner

Online guide · Guided demo

What you can do

01

Class details

02

Join experience

03

Available recording

Access & 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.

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

How the workflow works

  1. 01

    Open the class from your class list

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review its time and current state

    Join experience is part of the documented workflow.

  3. 03

    Join using the available control or open a recording when provided

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

Rules & 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.

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

Family portal · Family guide

My courses

Open courses available to the signed-in learner.

My courses illustrated banner

Online guide · Guided demo

What you can do

01

Course catalogue

02

Course details

03

Learning progress

Access & 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.

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

How the workflow works

  1. 01

    Select the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Choose an available course

    Course details is part of the documented workflow.

  3. 03

    Open its modules and lessons

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

Rules & 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.

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

Family portal · Family guide

Learn a course lesson

Follow the course’s modules and lessons and record permitted progress.

Learn a course lesson illustrated banner

Online guide · Guided demo

What you can do

01

Modules and lessons

02

Learning content

03

Lesson progress

Access & 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.

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

How the workflow works

  1. 01

    Open the course from your course list

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Choose the lesson and review its content

    Learning content is part of the documented workflow.

  3. 03

    Record progress through the available lesson control

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

Rules & 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.

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

Family portal · Family guide

My school notices

Read notices available to the signed-in school and family context.

My school notices illustrated banner

Online guide · Guided demo

What you can do

01

Linked children

02

Attendance and fees

03

Published results

04

Homework and courses

05

Timetable

06

Library

07

PTM

08

Transport

09

Personal documents

Access & 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.

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

How the workflow works

  1. 01

    Open the notices screen

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Choose an available notice

    Attendance and fees is part of the documented workflow.

  3. 03

    Read the details and any attached school instructions

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

Rules & 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.

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

Family portal · Family guide

Family overview

See the selected child’s school information and open the available self-service areas.

Family overview illustrated banner

Online guide · Guided demo

What you can do

01

Linked child selector

02

Quick links

03

Personal school overview

Access & 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.

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

How the workflow works

  1. 01

    Select the linked child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Open attendance, learning, fees or another available service

    Quick links is part of the documented workflow.

  3. 03

    Review the selected child’s information

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

Rules & 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.

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

Family portal · Family guide

My profile & guardians

Review the linked learner’s profile, guardians and available personal information.

My profile & guardians illustrated banner

Online guide · Guided demo

What you can do

01

Learner profile

02

Guardian information

03

Personal records

Access & 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.

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

How the workflow works

  1. 01

    Select the learner

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review the displayed profile and guardians

    Guardian information is part of the documented workflow.

  3. 03

    Contact the school for corrections where editing is not provided

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

Rules & 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.

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

Family portal · Family guide

Book a parent–teacher meeting

Book an eligible teacher slot and review family-visible meeting follow-ups.

Book a parent–teacher meeting illustrated banner

Online guide · Guided demo

What you can do

01

Available slots

02

My bookings

03

Reschedule/cancel

04

Family-visible follow-ups

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked child and available teacher slot

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Book the meeting and confirm its time

    My bookings is part of the documented workflow.

  3. 03

    Change the booking if needed

    Reschedule/cancel is part of the documented workflow.

  4. 04

    Review family-visible notes and complete a permitted follow-up

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

Rules & 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.

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

Family portal · Family guide

My published results

Review published report cards for the selected child and open the available printable result.

My published results illustrated banner

Online guide · Guided demo

What you can do

01

Published report cards

02

Exam results

03

Print view

Access & 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.

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

How the workflow works

  1. 01

    Select the child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Choose a published exam result

    Exam results is part of the documented workflow.

  3. 03

    Review the report card and use the available print view

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

Rules & 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.

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

Family portal · Family guide

My timetable

Review the learner’s weekly timetable and daily teacher cover.

My timetable illustrated banner

Online guide · Guided demo

What you can do

01

Weekly view

02

Daily date

03

Subjects and times

04

Print

Access & 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.

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

How the workflow works

  1. 01

    Select the child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Choose the weekly or daily view

    Daily date is part of the documented workflow.

  3. 03

    Inspect the timetable and available cover information

    Subjects and times is part of the documented workflow.

  4. 04

    Print the selected view if needed

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

Rules & 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.

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

Family portal · Family guide

My wellbeing information

Review the wellbeing and health information available to your linked family context.

My wellbeing information illustrated banner

Online guide · Guided demo

What you can do

01

Selected child

02

Available wellbeing information

03

Sick-room records

Access & 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.

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

How the workflow works

  1. 01

    Choose the linked child

    A signed-in account linked to the selected learner or personal staff profile.

  2. 02

    Review the permitted wellbeing and sick-room information

    Available wellbeing information is part of the documented workflow.

  3. 03

    Contact the school about information requiring attention

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

Rules & 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.

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

Platform · Screen guide

Platform AI Support Center

Ask platform questions with access to the supported aggregate context.

Platform AI Support Center illustrated banner

Online guide · Guided demo

What you can do

01

Question input

02

Aggregate context

03

Provider status

04

Answer review

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Review the provider banner

    Platform administrator access.

  2. 02

    Ask a supported platform question

    Aggregate context is part of the documented workflow.

  3. 03

    Check the response against the relevant report

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

Request fields to understand

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

FieldDeclared typeInput
questionstringRequired by declaration

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Platform analytics

Review cross-tenant growth, revenue and churn analytics.

Platform analytics illustrated banner

Online guide · Guided demo

What you can do

01

Growth

02

Revenue

03

Churn

04

Narrative summary

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open platform analytics

    Platform administrator access.

  2. 02

    Review the relevant reporting period and metrics

    Revenue is part of the documented workflow.

  3. 03

    Cross-check the generated narrative against the totals

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Platform audit trail

Inspect platform administrative activity across tenants.

Platform audit trail illustrated banner

Online guide · Guided demo

What you can do

01

Actor and action

02

Tenant context

03

Time and entity detail

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Choose the available audit filters

    Platform administrator access.

  2. 02

    Find the relevant administrative action

    Tenant context is part of the documented workflow.

  3. 03

    Review its tenant and entity context

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

AI tenant provisioning

Provision a tenant from the supported school and owner inputs.

AI tenant provisioning illustrated banner

Online guide · Guided demo

What you can do

01

School and owner facts

02

Provisioning request

03

Provisioning result

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Enter the intended school and owner details

    Platform administrator access.

  2. 02

    Review the requested setup

    Provisioning request is part of the documented workflow.

  3. 03

    Provision only an approved tenant and review the result

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

Request fields to understand

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

FieldDeclared typeInput
schoolNamestringRequired by declaration
institutionType(typeof INSTITUTION_TYPES)[number]Required by declaration
ownerNamestringRequired by declaration
ownerEmailstringRequired by declaration
ownerPhonestringOptional
domainstringOptional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Subscription coupons

Issue and manage billing discount codes with usage and validity controls.

Subscription coupons illustrated banner

Online guide · Guided demo

What you can do

01

Code window

02

Redemption limits

03

Active flag

04

Invoice preview and apply

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Create the approved coupon terms

    Platform administrator access.

  2. 02

    Review dates and redemption caps

    Redemption limits is part of the documented workflow.

  3. 03

    Preview its invoice effect before applying

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

Request fields to understand

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

FieldDeclared typeInput
codestringOptional
descriptionstringOptional
typestringRequired by declaration
valuenumberRequired by declaration
maxRedemptionsnumberOptional
validFromstringOptional
validUntilstringOptional
isActivebooleanOptional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Support impersonation

Inspect and manage platform support sessions separately from ordinary sign-in.

Support impersonation illustrated banner

Online guide · Guided demo

What you can do

01

Start/stop impersonation

02

Open sessions

03

Close lapsed sessions

04

Audit history

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Review the permitted support context

    Platform administrator access.

  2. 02

    Start the intended support session only when authorised

    Open sessions is part of the documented workflow.

  3. 03

    Stop the session and review its audit record

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

Request fields to understand

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

FieldDeclared typeInput
sessionIdstringOptional

Rules & current limits

  • Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited.

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

Platform · Screen guide

Platform invoices

Review subscription billing records across tenants.

Platform invoices illustrated banner

Online guide · Guided demo

What you can do

01

Invoice list

02

Invoice detail

03

Payment status

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Find the intended tenant invoice

    Platform administrator access.

  2. 02

    Review totals and payment state

    Invoice detail is part of the documented workflow.

  3. 03

    Open invoice details before a payment action

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Platform invoice detail

Review one SaaS invoice and its available gateway collection workflow.

Platform invoice detail illustrated banner

Online guide · Guided demo

What you can do

01

Invoice lines

02

Status and totals

03

Gateway order

04

Verified payment callback

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the invoice from the platform invoice list

    Platform administrator access.

  2. 02

    Review its lines and remaining balance

    Status and totals is part of the documented workflow.

  3. 03

    Use online payment only with a configured gateway

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

Request fields to understand

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

FieldDeclared typeInput
amountnumberOptional
paymentLogIdstringRequired by declaration
razorpayPaymentIdstringOptional
razorpaySignaturestringOptional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Landing Page CMS

Edit, preview and publish the public AVKUL ERP landing page with version history.

Landing Page CMS illustrated banner

Online guide · Guided demo

What you can do

01

Draft editor

02

Section order and visibility

03

SEO fields

04

Private preview

05

Publish

06

History and restore

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Load the current content and edit a draft

    Platform administrator access.

  2. 02

    Select media and review section order and visibility

    Section order and visibility is part of the documented workflow.

  3. 03

    Open the private preview

    SEO fields is part of the documented workflow.

  4. 04

    Publish the reviewed version or restore an earlier version

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

Request fields to understand

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

FieldDeclared typeInput
contentRecord<string,unknown>Required by declaration
draftIdstringRequired by declaration
revisionIdstringRequired by declaration

Rules & 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.

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

Platform · Screen guide

Campaign Manager

Create trackable campaign links and review attributed visits, enquiries and conversions.

Campaign Manager illustrated banner

Online guide · Guided demo

What you can do

01

Immutable tracking labels

02

Campaign dates and status

03

Tracking link

04

Period metrics

05

Search and CSV

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Create a draft campaign with source, medium and destination

    Platform administrator access.

  2. 02

    Copy its tracking link and use it in the intended campaign

    Campaign dates and status is part of the documented workflow.

  3. 03

    Review visits and accepted enquiries for a UTC period

    Tracking link is part of the documented workflow.

  4. 04

    Update the administrative status without changing the tracking key

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

Request fields to understand

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

FieldDeclared typeInput
sourcestringRequired by declaration
mediumstringRequired by declaration

Rules & 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.

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

Platform · Screen guide

Demo Enquiry CRM

Assign and progress product walkthrough enquiries with contact history and scheduling.

Demo Enquiry CRM illustrated banner

Online guide · Guided demo

What you can do

01

Walkthrough pipeline

02

Search and owner filters

03

Demo/follow-up dates

04

Internal notes

05

Attribution

06

CSV export

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Find a walkthrough enquiry and assign its owner

    Platform administrator access.

  2. 02

    Record its status, demo date or next follow-up

    Search and owner filters is part of the documented workflow.

  3. 03

    Add an internal note after contacting the school

    Demo/follow-up dates is part of the documented workflow.

  4. 04

    Mark the confirmed outcome and review history

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

Rules & 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.

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

Platform · Screen guide

Demo Calendar & Follow-ups

Turn CRM dates into daily work and manage product demos and platform follow-up tasks.

Demo Calendar & Follow-ups illustrated banner

Online guide · Guided demo

What you can do

01

Today/upcoming/overdue

02

UTC calendar

03

Schedule and reschedule

04

Completed/no-show/cancelled outcomes

05

Priority tasks

06

In-app reminders

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Review today’s or overdue work

    Platform administrator access.

  2. 02

    Schedule the demo or follow-up against an open walkthrough enquiry

    UTC calendar is part of the documented workflow.

  3. 03

    Record the outcome and optional next follow-up

    Schedule and reschedule is part of the documented workflow.

  4. 04

    Complete tasks and review the connected CRM history

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
dueAtstringRequired by declaration
prioritystringRequired by declaration
assignedToIdstring|nullOptional
leadIdstring|nullOptional
notestringRequired by declaration

Rules & 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.

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

Platform · Screen guide

Website Media Library

Upload, organise, crop and reuse supported website images.

Website Media Library illustrated banner

Online guide · Guided demo

What you can do

01

JPEG/PNG/static WebP

02

Folders and search

03

Desktop/mobile/thumbnail variants

04

Crop as new asset

05

Metadata

06

Archive and restore

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Upload a supported image and enter its descriptive metadata

    Platform administrator access.

  2. 02

    Organise it into a folder

    Folders and search is part of the documented workflow.

  3. 03

    Create a crop if needed and select it from the CMS

    Desktop/mobile/thumbnail variants is part of the documented workflow.

  4. 04

    Archive only when no published, draft or historical version references it

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration

Rules & 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.

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

Platform · Screen guide

Platform overview

Review platform footprint, revenue indicators and tenant status.

Platform overview illustrated banner

Online guide · Guided demo

What you can do

01

Tenant and school counts

02

Subscription summary

03

Platform priorities

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the platform overview

    Platform administrator access.

  2. 02

    Review the current footprint and billing totals

    Subscription summary is part of the documented workflow.

  3. 03

    Open the relevant tenant or report

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Subscription plans & modules

Create and edit subscription plans with their module toggles.

Subscription plans & modules illustrated banner

Online guide · Guided demo

What you can do

01

Plan catalogue

02

Plan editor

03

Module selection

04

Archive

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the intended plan

    Platform administrator access.

  2. 02

    Review pricing fields and enabled modules

    Plan editor is part of the documented workflow.

  3. 03

    Save the approved configuration or archive the plan

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
codestringRequired by declaration
descriptionstringOptional
billingCyclestringOptional
priceMonthlynumberOptional
priceYearlynumberOptional
trialDaysnumberOptional
maxStudentsnumberOptional
maxStaffnumberOptional
maxSchoolsnumberOptional
maxBranchesnumberOptional
isPublicbooleanOptional
isActivebooleanOptional
moduleKeysstring[]Optional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Platform reports

Generate cross-tenant revenue, usage, churn or activity reports.

Platform reports illustrated banner

Online guide · Guided demo

What you can do

01

Report type

02

JSON/CSV/PDF outputs

03

Platform scope

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Choose the report type

    Platform administrator access.

  2. 02

    Review the reporting context

    JSON/CSV/PDF outputs is part of the documented workflow.

  3. 03

    Open or export the generated report in an available format

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Tenant subscriptions

Review subscriptions and change an approved tenant plan.

Tenant subscriptions illustrated banner

Online guide · Guided demo

What you can do

01

Subscription list

02

Current plan

03

Upgrade/downgrade

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Locate the tenant subscription

    Platform administrator access.

  2. 02

    Review its current plan and state

    Current plan is part of the documented workflow.

  3. 03

    Apply the approved plan change and check usage implications

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

Request fields to understand

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

FieldDeclared typeInput
planCodestringRequired by declaration
namestringRequired by declaration
codestringRequired by declaration
descriptionstringOptional
billingCyclestringOptional
priceMonthlynumberOptional
priceYearlynumberOptional
trialDaysnumberOptional
maxStudentsnumberOptional
maxStaffnumberOptional
maxSchoolsnumberOptional
maxBranchesnumberOptional
isPublicbooleanOptional
isActivebooleanOptional
moduleKeysstring[]Optional

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Tenant & school onboarding

Search tenants, inspect their health and provision approved school workspaces.

Tenant & school onboarding illustrated banner

Online guide · Guided demo

What you can do

01

Search and status

02

Onboarding

03

School creation

04

Status changes

05

Health scores

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Search for the tenant before creating one

    Platform administrator access.

  2. 02

    Review school, owner and plan details

    Onboarding is part of the documented workflow.

  3. 03

    Onboard or update the intended tenant

    School creation is part of the documented workflow.

  4. 04

    Inspect the resulting tenant detail

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

Request fields to understand

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

FieldDeclared typeInput
tenantNamestringRequired by declaration
slugstringRequired by declaration
schoolNamestringRequired by declaration
schoolCodestringRequired by declaration
boardstringOptional
typestringOptional
adminEmailstringRequired by declaration
adminPasswordstringRequired by declaration
adminFirstNamestringRequired by declaration
adminLastNamestringOptional
planCodestringOptional
statusstringRequired by declaration
idsstring[]Required by declaration
action'ACTIVATE' | 'SUSPEND' | 'CANCEL'Required by declaration

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Tenant detail & branding

Review tenant schools, subscription and quotas and maintain supported branding.

Tenant detail & branding illustrated banner

Online guide · Guided demo

What you can do

01

School list

02

Subscription and counts

03

Branding

04

Domain settings

05

Additional schools

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the tenant from the list

    Platform administrator access.

  2. 02

    Review its schools and subscription

    Subscription and counts is part of the documented workflow.

  3. 03

    Save approved branding or add a school within quota

    Branding is part of the documented workflow.

  4. 04

    Verify domain setup separately before relying on it

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

Request fields to understand

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

FieldDeclared typeInput
codestringRequired by declaration
namestringRequired by declaration
typestringOptional
boardstringOptional
adminEmailstringOptional
adminPasswordstringOptional
adminFirstNamestringOptional
adminLastNamestringOptional
brandNamestringOptional
primaryColorstringOptional
faviconUrlstringOptional
domainstringRequired by declaration

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Platform plan usage

Review quota and module usage against platform plan limits.

Platform plan usage illustrated banner

Online guide · Guided demo

What you can do

01

Plan limits

02

Current usage

03

Module availability

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Choose the tenant or scope available to the view

    Platform administrator access.

  2. 02

    Compare usage with the plan limits

    Current usage is part of the documented workflow.

  3. 03

    Review upgrades or cleanup through the appropriate workflow

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

Platform · Screen guide

Website Analytics

Review privacy-aware website activity and accepted walkthrough conversions for a UTC period.

Website Analytics illustrated banner

Online guide · Guided demo

What you can do

01

Visitors and page views

02

CTA/form activity

03

Source and campaign

04

Device and page reports

05

Conversion funnel

06

CSV export

Access & setup

Intended access: Platform administrator.

  • Platform administrator access.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Select a UTC period of up to 90 days

    Platform administrator access.

  2. 02

    Review traffic and the form funnel

    CTA/form activity is part of the documented workflow.

  3. 03

    Compare sources, campaigns and devices

    Source and campaign is part of the documented workflow.

  4. 04

    Export the aggregate report if needed

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

Rules & 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.

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

Academics · Screen guide

Sessions, classes & subjects

Use sessions, classes & subjects in the school workspace. Create the academic structure that attendance, admissions, examinations and timetables share.

Sessions, classes & subjects illustrated banner

Online guide · Guided demo

What you can do

01

List Sessions

02

Create Session

03

List Classes

04

Create Class

05

Every academic year and whether its books are closed

06

Close or re-open an academic year's books

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
settings:viewsettings:createstudent:viewsettings:manage

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

How the workflow works

  1. 01

    Create an academic session with dates

    A school account with the permissions shown below.

  2. 02

    Add classes and their sections

    Create Session is part of the documented workflow.

  3. 03

    Create subjects and select the current session

    List Classes is part of the documented workflow.

  4. 04

    Close the books only after the year-end review

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

Fields & controls

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

  • Name
  • Start
  • End
  • Session
  • Level
  • Class
  • Capacity
  • Code
  • Type

Rules & current limits

  • Session ownership and closed-year checks apply to connected workflows.

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

Academics · Screen guide

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.

Adaptive exam attempt detail illustrated banner

Online guide · Guided demo

What you can do

01

Exam schedules

02

Marks entry and history

03

Completion status

04

Grade scales

05

Report cards

06

Publish and unpublish

07

Seating and invigilation

08

Adaptive exams

09

Mark rechecks

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create the exam and its subject schedules

    A school account with the permissions shown below.

  2. 02

    Review the candidates, seating and completion status

    Marks entry and history is part of the documented workflow.

  3. 03

    Record and verify marks, then generate report cards

    Completion status is part of the documented workflow.

  4. 04

    Publish approved results; use the correction workflow when required

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

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Academics · Screen guide

Adaptive online exams

Use adaptive online exams in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards.

Adaptive online exams illustrated banner

Online guide · Guided demo

What you can do

01

Save question

02

Create exam

03

List

04

Create

05

List Questions

06

Create Question

07

Get Exam

08

Update Status

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create the exam and its subject schedules

    A school account with the permissions shown below.

  2. 02

    Review the candidates, seating and completion status

    Create exam is part of the documented workflow.

  3. 03

    Record and verify marks, then generate report cards

    List is part of the documented workflow.

  4. 04

    Publish approved results; use the correction workflow when required

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
subjectIdstringRequired by declaration
classIdstringOptional
sectionIdstringOptional
targetCountnumberOptional
durationMinnumberOptional
maxAttemptsnumberOptional
questionIdsstring[]Optional
publishResultsbooleanOptional
textstringRequired by declaration
optionsstring[]Required by declaration
correctAnswerstringRequired by declaration
difficultystringOptional
chapterstringOptional
marksnumberOptional
status'SCHEDULED' | 'ONGOING' | 'COMPLETED' | 'RESULT_PUBLISHED' | 'LOCKED'Required by declaration

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

School office · Screen guide

Admissions & applicant journey

Use admissions & applicant journey in the school workspace. Connect family enquiries, counsellor follow-ups, reviewed applications and student admission.

Admissions & applicant journey illustrated banner

Online guide · Guided demo

What you can do

01

Start application

02

Log call

03

Review application

04

Schedule visit

05

Save guardian

06

Save visit

07

Create student & guardian

08

Preview student fee

09

Queue

10

Leads due a follow-up, oldest overdue first

11

Pipeline by stage and by source, with conversion

12

List

13

History

14

Record a contact attempt and move the lead on

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
admission:viewadmission:updateadmission:createadmission:manage

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

How the workflow works

  1. 01

    Record or select an enquiry and log the next follow-up

    A school account with the permissions shown below.

  2. 02

    Open a linked application and review guardian details

    Log call is part of the documented workflow.

  3. 03

    Receive and verify required documents and review readiness

    Review application is part of the documented workflow.

  4. 04

    Select session, class and section before admitting the applicant

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

Fields & controls

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

  • 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

Rules & current limits

  • Application access links and parent invitations are separate from an existing family login. Admission is subject to readiness and school/session ownership.

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

Intelligence · Screen guide

AI governance & trust

Use the ai governance & trust workspace to review its saved runs, context and available actions.

AI governance & trust illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
hostel:viewhealth:managedashboard:viewstudent:managesettings:update

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
visitorLogIdstringOptional
studentIdstringOptional
vehicleIdstringOptional
daysnumberOptional
requestIdstringRequired by declaration
decisionstringRequired by declaration
notestringOptional
correctedTextstringOptional
biometricEnabledbooleanOptional
faceMatchEnabledbooleanOptional
biometricRetentionDaysnumberOptional
parentOptOutDefaultbooleanOptional
consentRequiredFeaturesstring[]Optional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Intelligence · Screen guide

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.

School AI tools illustrated banner

Online guide · Guided demo

What you can do

01

AI configuration status; does not contact the provider or expose secrets

02

Generate Remark

03

Attendance Anomalies

04

Fee Risk

05

Generate Question Paper

06

Discipline Risk

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
dashboard:viewexam:updateattendance:viewfee:viewexam:createstudent:viewlms:viewtimetable:viewinventory:viewcommunication:createattendance:createhostel:viewexam:viewstudent:managefee:manageattendance:updatetransport:viewhealth:managesettings:update

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

How the workflow works

  1. 01

    Review the provider-status banner before requesting assistance

    A school account with the permissions shown below.

  2. 02

    Choose the school context, topic or forecast period

    Generate Remark is part of the documented workflow.

  3. 03

    Run the relevant tool and inspect its output and evidence

    Attendance Anomalies is part of the documented workflow.

  4. 04

    Review or edit the result before using it with learners

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

Fields & controls

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

  • AI readiness

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Community · Screen guide

Alumni records

Use alumni records in the school workspace. Maintain alumni information and keep former learners connected to the school community.

Alumni records illustrated banner

Online guide · Guided demo

What you can do

01

Alumni directory

02

Record creation

03

Profile updates

04

Record removal

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:create

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

How the workflow works

  1. 01

    Open the alumni directory

    A school account with the permissions shown below.

  2. 02

    Add the alumnus and relevant year/contact details

    Record creation is part of the documented workflow.

  3. 03

    Update the record as information changes

    Profile updates is part of the documented workflow.

  4. 04

    Review scope before removing an entry

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

Fields & controls

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

  • First name
  • Last name
  • Phone

Rules & current limits

  • A directory record does not automatically provision an alumni login or send invitations.

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

Community · Screen guide

Notices, announcements & messages

Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations.

Notices, announcements & messages illustrated banner

Online guide · Guided demo

What you can do

01

Delivery report

02

List Templates

03

Create Template

04

Count and channel-reachability for an audience

05

List

06

Per-recipient delivery report

07

Create

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
communication:viewcommunication:createcommunication:manage

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

How the workflow works

  1. 01

    Choose the notice, announcement or conversation workflow

    A school account with the permissions shown below.

  2. 02

    Select the permitted audience and prepare the content

    List Templates is part of the documented workflow.

  3. 03

    Preview reachability before sending where available

    Create Template is part of the documented workflow.

  4. 04

    Review delivery reports, replies or complaint status

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

Fields & controls

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

  • Use a template (optional)
  • Title
  • Message
  • Audience
  • Class
  • Section

Rules & current limits

  • External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it.

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

Academics · Screen guide

Homework & assignments

Use homework & assignments in the school workspace. Create and distribute class work, collect student submissions and record grading feedback.

Homework & assignments illustrated banner

Online guide · Guided demo

What you can do

01

New assignment

02

Create assignment

03

Save grade

04

Return for revision

05

Save assignment changes

06

Send due reminders

07

Delete empty assignment

08

Student work

09

List

10

Dashboard

11

Remind

12

Reminder History

13

History

14

Get

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
assignment:viewassignment:updateassignment:createassignment:delete

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

How the workflow works

  1. 01

    Select the teaching section and create an assignment

    A school account with the permissions shown below.

  2. 02

    Add the instructions, due date and supported files

    Create assignment is part of the documented workflow.

  3. 03

    Review submitted or pending work

    Save grade is part of the documented workflow.

  4. 04

    Grade the submission and review the activity history

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

Fields & controls

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

  • Title
  • Assignment class
  • Assignment section
  • Subject
  • Due date & time
  • Maximum marks
  • Visibility
  • Instructions
  • Filter class
  • Filter section
  • Status
  • Marks for

Rules & current limits

  • Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel.

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

Academics · Screen guide

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.

Assignment detail & submission review illustrated banner

Online guide · Guided demo

What you can do

01

New assignment

02

Create assignment

03

Save grade

04

Return for revision

05

Save assignment changes

06

Send due reminders

07

Delete empty assignment

08

Student work

09

List

10

Dashboard

11

Remind

12

Reminder History

13

History

14

Get

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
assignment:viewassignment:updateassignment:createassignment:delete

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

How the workflow works

  1. 01

    Select the teaching section and create an assignment

    A school account with the permissions shown below.

  2. 02

    Add the instructions, due date and supported files

    Create assignment is part of the documented workflow.

  3. 03

    Review submitted or pending work

    Save grade is part of the documented workflow.

  4. 04

    Grade the submission and review the activity history

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

Fields & controls

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

  • Title
  • Assignment class
  • Assignment section
  • Subject
  • Due date & time
  • Maximum marks
  • Visibility
  • Instructions
  • Filter class
  • Filter section
  • Status
  • Marks for

Rules & current limits

  • Attachment access and learner submissions follow school and child ownership. Reminder delivery depends on the configured channel.

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

Academics · Screen guide

Student attendance

Use student attendance in the school workspace. Complete a daily class register and review attendance history, shortages and family alerts.

Student attendance illustrated banner

Online guide · Guided demo

What you can do

01

Mark all present

02

Students of a section + their status for a date

03

Mark/replace attendance for a section + date

04

Tell absent students' guardians, once per student per day

05

Students below the required attendance percentage

06

Warn guardians of students below the required percentage

07

What has already been sent to families

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
attendance:viewattendance:createattendance:manage

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

How the workflow works

  1. 01

    Choose a permitted section and date

    A school account with the permissions shown below.

  2. 02

    Mark the roster and review the section completion summary

    Students of a section + their status for a date is part of the documented workflow.

  3. 03

    Save the register and inspect corrections/history

    Mark/replace attendance for a section + date is part of the documented workflow.

  4. 04

    Review shortages and recorded alerts before reminding families

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

Fields & controls

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

  • Class / section
  • Attendance date
  • Session
  • Correction reason
  • Notify absent students’ guardians in-app on save

Rules & current limits

  • Holiday and attendance policy affect denominators. Only permitted sections are visible; recording an absence is distinct from approving leave.

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

Administration · Screen guide

Audit trail

Use audit trail in the school workspace. Review the recorded actions taken on school records and trace related entities.

Audit trail illustrated banner

Online guide · Guided demo

What you can do

01

Activity filters

02

Actor and action

03

Entity references

04

Record detail

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Select an entity or activity filter

    A school account with the permissions shown below.

  2. 02

    Locate the relevant actor and time

    Actor and action is part of the documented workflow.

  3. 03

    Open the recorded change and its entity reference

    Entity references is part of the documented workflow.

  4. 04

    Compare the trail with the current record

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

Fields & controls

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

  • Entity
  • Action
  • From

Rules & current limits

  • The audit view records permitted activity; it is not an editor for rewriting historical actions.

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

School office · Screen guide

Branch & campus management

Use branch & campus management in the school workspace. See school-wide priorities and manage the campus context used by the ERP.

Branch & campus management illustrated banner

Online guide · Guided demo

What you can do

01

Make main

02

Per-branch student/staff counts and fee collection

03

Open another campus (counts against the plan)

04

Rename a campus, or make it the main one

05

Close a campus (refused while anyone is posted to it)

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
dashboard:viewsettings:createsettings:updatesettings:delete

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

How the workflow works

  1. 01

    Review the school dashboard and current session

    A school account with the permissions shown below.

  2. 02

    Open an outstanding action in the relevant module

    Per-branch student/staff counts and fee collection is part of the documented workflow.

  3. 03

    Inspect the campus counts and permitted branch settings

    Open another campus (counts against the plan) is part of the documented workflow.

  4. 04

    Review the consequences before closing a campus

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

Request fields to understand

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

FieldDeclared typeInput
codestringRequired by declaration
namestringRequired by declaration
addressLine1stringOptional
citystringOptional
phonestringOptional
isMainbooleanOptional

Rules & current limits

  • Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow.

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

School office · Screen guide

School calendar & holidays

Use school calendar & holidays in the school workspace. Publish the dates, events and holiday settings that support school planning and attendance.

School calendar & holidays illustrated banner

Online guide · Guided demo

What you can do

01

Today

02

( )

03

Remove

04

Feed

05

Working Days

06

Get Policy

07

Set Policy

08

List Holidays

09

Create Holiday

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
calendar:viewsettings:updatecalendar:createcalendar:updatecalendar:deletecommunication:manage

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

How the workflow works

  1. 01

    Review the selected calendar period

    A school account with the permissions shown below.

  2. 02

    Add or update a permitted holiday or event

    ( ) is part of the documented workflow.

  3. 03

    Check applicability to students and staff

    Remove is part of the documented workflow.

  4. 04

    Review working days and RSVP summaries

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

Fields & controls

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

  • guests

Rules & current limits

  • Declaring a holiday requires its own permission. The attendance and timetable workflows use their documented calendar rules.

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

Intelligence · Screen guide

Cashflow prediction

Use the cashflow prediction workspace to review its saved runs, context and available actions.

Cashflow prediction illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
scholarshipPctnumberOptional
monthsnumberOptional
collectionRatePctnumberOptional
labelstringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

School office · Screen guide

Certificates & verification

Use certificates & verification in the school workspace. Manage certificate templates, issue documents and provide token-based verification.

Certificates & verification illustrated banner

Online guide · Guided demo

What you can do

01

Revoke

02

List Templates

03

Create Template

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose or create a certificate template

    A school account with the permissions shown below.

  2. 02

    Select the eligible recipient and issue the document

    List Templates is part of the documented workflow.

  3. 03

    Review the generated certificate record

    Create Template is part of the documented workflow.

  4. 04

    Use the document verification token to check validity

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

Fields & controls

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

  • Name
  • Type
  • Student

Rules & current limits

  • Verification requires an actual generated token. Sample demo certificates are not school-issued documents.

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

Institutions · Screen guide

College administration

Use college administration in the school workspace. Manage department and semester structures, electives, internal marks, placements and research records.

College administration illustrated banner

Online guide · Guided demo

What you can do

01

Add

02

Remove

03

Offer

04

Enrol

05

Record

06

Log

07

Register

08

College overview stats

09

List all departments

10

Create a department

11

Update a department

12

Delete a department

13

List semesters (filter by departmentId)

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:createstudent:updatestudent:delete

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

How the workflow works

  1. 01

    Create the department and semester structure

    A school account with the permissions shown below.

  2. 02

    Offer electives with the required limits

    Remove is part of the documented workflow.

  3. 03

    Record eligible enrollments and internal marks

    Offer is part of the documented workflow.

  4. 04

    Maintain placement and research records

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
codestringRequired by declaration
hodStaffIdstringOptional
descriptionstringOptional
totalSeatsnumberOptional
departmentIdstringRequired by declaration
semesterNonumberRequired by declaration
typeSemesterTypeRequired by declaration
startDatestringOptional
endDatestringOptional
totalCreditsnumberOptional
subjectIdstringRequired by declaration
semesterIdstringRequired by declaration
maxStudentsnumberOptional
creditsnumberOptional
teacherStaffIdstringOptional
studentIdstringRequired by declaration
assignment1numberOptional
assignment2numberOptional
midSemnumberOptional
attendancenumberOptional
practicalnumberOptional
maxMarksnumberOptional
companyNamestringRequired by declaration

Rules & current limits

  • College workflows share the school account and permission context; college-specific setup must exist.

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

Community · Screen guide

Notices, announcements & messages

Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations.

Notices, announcements & messages illustrated banner

Online guide · Guided demo

What you can do

01

Notices

02

Create Notice

03

Events

04

Create Event

05

Complaints

06

Create Complaint

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose the notice, announcement or conversation workflow

    A school account with the permissions shown below.

  2. 02

    Select the permitted audience and prepare the content

    Create Notice is part of the documented workflow.

  3. 03

    Preview reachability before sending where available

    Events is part of the documented workflow.

  4. 04

    Review delivery reports, replies or complaint status

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

Fields & controls

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

  • Title
  • Message
  • Audience
  • Date
  • Venue
  • Subject
  • Details
  • Priority

Rules & current limits

  • External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it.

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

Student care · Screen guide

Discipline & behaviour

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

Discipline & behaviour illustrated banner

Online guide · Guided demo

What you can do

01

Schedule

02

Served

03

Waive

04

List

05

Watchlist

06

List Sanctions

07

Get Policy

08

Set Policy

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
discipline:viewdiscipline:managediscipline:updatediscipline:create

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

How the workflow works

  1. 01

    Locate the student within your permitted scope

    A school account with the permissions shown below.

  2. 02

    Record the incident and relevant context

    Served is part of the documented workflow.

  3. 03

    Review standing and any suggested threshold action

    Waive is part of the documented workflow.

  4. 04

    Schedule or close the appropriate sanction

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

Fields & controls

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

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

Rules & current limits

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

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

Intelligence · Screen guide

Enrolment & capacity forecast

Use the enrolment & capacity forecast workspace to review its saved runs, context and available actions.

Enrolment & capacity forecast illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
conversionPctnumberOptional
defaultSectionCapacitynumberOptional
studentsPerTeachernumberOptional
labelstringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Academics · Screen guide

Exam seating & invigilation

Use exam seating & invigilation in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards.

Exam seating & invigilation illustrated banner

Online guide · Guided demo

What you can do

01

Exam rooms

02

Room capacity

03

Candidate seating

04

Invigilator duties

05

Admit-card details

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create the required exam rooms

    A school account with the permissions shown below.

  2. 02

    Select the paper and allocate candidate seating

    Room capacity is part of the documented workflow.

  3. 03

    Assign the invigilators and review the seating chart

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
rowsnumberOptional
seatsPerRownumberOptional
blockedSeatsnumberOptional
buildingstringOptional
floorstringOptional
scheduleIdstringRequired by declaration
roomIdsstring[]Optional
replacebooleanOptional
roomIdstringRequired by declaration
staffIdstringRequired by declaration
rolestringOptional
examTypestringOptional
sessionIdstringOptional
termIdstringOptional
startDatestringOptional
endDatestringOptional
classIdstringRequired by declaration
sectionIdstringOptional
subjectIdstringRequired by declaration
examDatestringOptional
startTimestringOptional
endTimestringOptional
maxMarksnumberRequired by declaration

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Academics · Screen guide

Examinations & results

Use examinations & results in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards.

Examinations & results illustrated banner

Online guide · Guided demo

What you can do

01

Exam schedules

02

Marks entry and history

03

Completion status

04

Grade scales

05

Report cards

06

Publish and unpublish

07

Seating and invigilation

08

Adaptive exams

09

Mark rechecks

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
exam:viewexam:create

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

How the workflow works

  1. 01

    Create the exam and its subject schedules

    A school account with the permissions shown below.

  2. 02

    Review the candidates, seating and completion status

    Marks entry and history is part of the documented workflow.

  3. 03

    Record and verify marks, then generate report cards

    Completion status is part of the documented workflow.

  4. 04

    Publish approved results; use the correction workflow when required

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

Fields & controls

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

  • Exam name
  • Start date
  • End date
  • Type

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Academics · Screen guide

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.

Exam marks & report-card workspace illustrated banner

Online guide · Guided demo

What you can do

01

Save schedule

02

Marks

03

Edit

04

Delete

05

Save marks

06

Generate drafts

07

Publish to parents

08

Withdraw section results

09

List Schedules

10

Completion

11

Create Schedule

12

Update

13

Remove

14

Marks-entry roster for a schedule

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
exam:viewexam:updateexam:delete

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

How the workflow works

  1. 01

    Create the exam and its subject schedules

    A school account with the permissions shown below.

  2. 02

    Review the candidates, seating and completion status

    Marks is part of the documented workflow.

  3. 03

    Record and verify marks, then generate report cards

    Edit is part of the documented workflow.

  4. 04

    Publish approved results; use the correction workflow when required

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

Fields & controls

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

  • Class
  • Section
  • Subject
  • Subject paper
  • Correction reason (required when changing saved marks)
  • Correction reason
  • Report card section
  • Withdrawal reason
  • Report card

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Intelligence · Screen guide

Executive Copilot

Use the executive copilot workspace to review its saved runs, context and available actions.

Executive Copilot illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
questionstringRequired by declaration
boardstringOptional
purposestringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Finance · Screen guide

Fee structures & billing setup

Define fee types, installment amounts and eligible billing structures.

Fee structures & billing setup illustrated banner

Online guide · Guided demo

What you can do

01

Fee types

02

Structure editor

03

Installments

04

Billing preview

05

Invoice generation

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
fee:viewfee:createfee:manage

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

How the workflow works

  1. 01

    Review the academic scope and fee types

    A school account with the permissions shown below.

  2. 02

    Create a structure with installments

    Structure editor is part of the documented workflow.

  3. 03

    Preview eligible students and existing invoices

    Installments is part of the documented workflow.

  4. 04

    Generate the reviewed billing

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
codestringOptional
isRecurringbooleanOptional
isOptionalbooleanOptional
classIdstringOptional
studentIdstringOptional
sessionIdstringOptional
itemsFeeStructureItemDto[]Required by declaration
structureIdstringRequired by declaration
installmentNonumberOptional
sectionIdstringOptional
dueDatestringOptional
notesstringOptional

Rules & current limits

  • A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation.

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

Finance · Screen guide

Fee collections & dues

Use fee collections & dues in the school workspace. Configure charges, preview billing, issue invoices and record collections and adjustments.

Fee collections & dues illustrated banner

Online guide · Guided demo

What you can do

01

Adjust

02

Apply discount

03

Add late fee

04

Write off balance

05

Refund

06

Undo

07

Preview reminders

08

Add scheme

09

Collections Summary

10

Reconcile Collection

11

Fine

12

List Types

13

Create Type

14

Concession schemes the school offers

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create the required fee structure and installments

    A school account with the permissions shown below.

  2. 02

    Preview eligible students and existing invoices

    Apply discount is part of the documented workflow.

  3. 03

    Generate invoices and record a valid collection

    Add late fee is part of the documented workflow.

  4. 04

    Review the receipt, remaining balance and adjustment history

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

Fields & controls

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

  • 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

Rules & current limits

  • A collection record is distinct from online gateway settlement. Adjustment and refund actions require the appropriate permission and validation.

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

Intelligence · Screen guide

Operational forecasts

Run and inspect the available operational forecast records.

Operational forecasts illustrated banner

Online guide · Guided demo

What you can do

01

Forecast selection

02

Latest run

03

History and result

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Select the available forecast and context

    A school account with the permissions shown below.

  2. 02

    Review provider and data readiness

    Latest run is part of the documented workflow.

  3. 03

    Run and compare the returned result with actual records

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

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

School office · Screen guide

Campus gate passes

Use campus gate passes in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit.

Campus gate passes illustrated banner

Online guide · Guided demo

What you can do

01

Early-release requests

02

Decision and reason

03

Authorised pickup

04

Campus release

05

Return and cancel

06

Currently-out register

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:updatestudent:managestudent:create

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

How the workflow works

  1. 01

    Choose the student and request reason

    A school account with the permissions shown below.

  2. 02

    Review the pickup person and decide the request

    Decision and reason is part of the documented workflow.

  3. 03

    Record authorised release at the gate

    Authorised pickup is part of the documented workflow.

  4. 04

    Record return or inspect the currently-out register

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

Request fields to understand

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

FieldDeclared typeInput
studentIdstringRequired by declaration
reasonstringOptional
expectedOutAtstringOptional
expectedBackAtstringOptional
releaseToNamestringOptional
releaseToGuardianIdstringOptional
approvebooleanRequired by declaration
guardianIdstringOptional
releaseRelationstringOptional
overrideReasonstringOptional
notesstringOptional
firstNamestringRequired by declaration
middleNamestringOptional
lastNamestringOptional
admissionNostringRequired by declaration
rollNostringOptional
genderstringOptional
dateOfBirthstringOptional
bloodGroupstringOptional
sessionIdstringOptional
classIdstringOptional
sectionIdstringOptional
admissionDatestringOptional
phonestringOptional

Rules & current limits

  • Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record.

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

Student care · Screen guide

Health records & infirmary

Use health records & infirmary in the school workspace. Maintain school health information and record infirmary visits, medication entries and closures.

Health records & infirmary illustrated banner

Online guide · Guided demo

What you can do

01

Load

02

Give medicine

03

List

04

Get By Student

05

Upsert

06

List Visits

07

Students in the sick room unusually often

08

Alerts

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Find the permitted student health profile

    A school account with the permissions shown below.

  2. 02

    Review emergency and health information

    Give medicine is part of the documented workflow.

  3. 03

    Record the infirmary visit and permitted medication details

    List is part of the documented workflow.

  4. 04

    Close the visit and review repeated visits where relevant

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

Request fields to understand

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

FieldDeclared typeInput
bloodGroupstringOptional
allergiesstringOptional
chronicConditionsstringOptional
medicationsstringOptional
emergencyContactNamestringOptional
emergencyContactPhonestringOptional
heightCmnumberOptional
weightKgnumberOptional
lastCheckupDatestringOptional
vaccinationJsonRecord<string, unknown>Optional
notesstringOptional
studentIdstringRequired by declaration
complaintstringRequired by declaration
observationsstringOptional
temperatureCnumberOptional
outcome'OPEN' | 'RETURNED_TO_CLASS' | 'RESTING' | 'SENT_HOME' | 'REFERRED_HOSPITAL'Required by declaration
treatmentstringOptional
medicinestringRequired by declaration
visitIdstringOptional
dosestringOptional
routestringOptional
consentSourcestringOptional

Rules & current limits

  • Access is restricted by dedicated health permissions. Sample walkthrough information is fictional and is not medical advice.

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

Campus · Screen guide

Hostel, rooms & roll call

Use hostel, rooms & roll call in the school workspace. Manage residence capacity, room/bed allocations, visitor logs and nightly attendance.

Hostel, rooms & roll call illustrated banner

Online guide · Guided demo

What you can do

01

List Hostels

02

Create Hostel

03

List Rooms

04

Create Room

05

List Beds

06

Create Bed

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Set up the hostel, rooms and beds

    A school account with the permissions shown below.

  2. 02

    Allocate eligible residents to available accommodation

    Create Hostel is part of the documented workflow.

  3. 03

    Record and check out permitted visitors

    List Rooms is part of the documented workflow.

  4. 04

    Open the roll call, mark residents and close the register

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

Fields & controls

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

  • Name
  • Type
  • Capacity
  • Room

Rules & current limits

  • Capacity and allocation state must be reviewed before assignment. Family notification delivery depends on the available channel.

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

Administration · Screen guide

Notifications & integrations

Use notifications & integrations in the school workspace. Review notifications, integration settings, webhook records and shared AI request state.

Notifications & integrations illustrated banner

Online guide · Guided demo

What you can do

01

In-app notifications

02

Integration status

03

Integration configuration

04

Webhooks

05

AI requests

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
settings:viewsettings:create

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

How the workflow works

  1. 01

    Open the relevant integration or notification view

    A school account with the permissions shown below.

  2. 02

    Review status and permitted settings

    Integration status is part of the documented workflow.

  3. 03

    Configure a provider using approved credentials outside public documentation

    Integration configuration is part of the documented workflow.

  4. 04

    Use a controlled test and inspect the actual result

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

Fields & controls

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

  • Title

Rules & current limits

  • Saving settings is not proof of external delivery. No credential values are included in this documentation.

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

Campus · Screen guide

Inventory & purchases

Use inventory & purchases in the school workspace. Manage supplies, procurement, stock movements and issued school property.

Inventory & purchases illustrated banner

Online guide · Guided demo

What you can do

01

Remove line

02

Add order line

03

Add item

04

Record stock movement

05

Add vendor

06

New purchase order

07

Issue an asset

08

Export this view CSV

09

Workspace

Access & 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.
Required permission keys
inventory:view

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

How the workflow works

  1. 01

    Create an item and supplier with the relevant stock unit

    A school account with the permissions shown below.

  2. 02

    Prepare and submit a purchase order for review

    Add order line is part of the documented workflow.

  3. 03

    Receive accepted quantities and inspect stock movements

    Add item is part of the documented workflow.

  4. 04

    Issue or return property and review outstanding balances

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

Fields & controls

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

  • Order item
  • | Ordered , received
  • Vendor filter

Rules & current limits

  • Purchase totals exclude tax/freight and supplier accounting. Valuation uses reference prices, not FIFO or weighted-average accounting.

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

Intelligence · Screen guide

Hostel & inventory forecast

Use the hostel & inventory forecast workspace to review its saved runs, context and available actions.

Hostel & inventory forecast illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
lookbackDaysnumberOptional
horizonDaysnumberOptional
occupancyBoostPctnumberOptional
categorystringOptional
labelstringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Intelligence · Screen guide

Early learning gaps

Use the early learning gaps workspace to review its saved runs, context and available actions.

Early learning gaps illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewlms:view

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
sectionIdstringOptional
weeksnumberOptional
status'ACKNOWLEDGED' | 'IN_PROGRESS' | 'RESOLVED' | 'DISMISSED' | 'OPEN'Required by declaration
notestringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Finance · Screen guide

General ledger

Use general ledger in the school workspace. Maintain account records and post balanced double-entry journals with auditable reversals.

General ledger illustrated banner

Online guide · Guided demo

What you can do

01

Create a standard chart

02

Add line

03

Reverse

04

List Accounts

05

Create Account

06

Create a standard chart of accounts, skipping what exists

07

List Journals

08

Post a balanced double-entry transaction

09

Post the mirror image; the original stays on the record

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
fee:viewfee:manage

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

How the workflow works

  1. 01

    Review or seed the chart of accounts

    A school account with the permissions shown below.

  2. 02

    Prepare matching debit and credit lines

    Add line is part of the documented workflow.

  3. 03

    Post the balanced journal and inspect its record

    Reverse is part of the documented workflow.

  4. 04

    Use a reversal to correct an entry without erasing the original

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
codestringOptional
typestringRequired by declaration
parentIdstringOptional
isPostablebooleanOptional
linesJournalLineDto[]Required by declaration
entryDatestringOptional
narrationstringOptional
sourcestringOptional
sourceRefstringOptional

Rules & current limits

  • Debits and credits must balance. Ledger recording is not a bank settlement or a statutory filing.

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

Intelligence · Screen guide

AI lesson planner

Use the ai lesson planner workspace to review its saved runs, context and available actions.

AI lesson planner illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
classIdstringRequired by declaration
subjectIdstringRequired by declaration
topicstringOptional
weekOfstringOptional
sectionIdstringOptional
regeneratebooleanOptional
objectivesstring[]Optional
activitiesstring[]Optional
worksheetstringOptional
exitTicketstringOptional
notesstringOptional
homeworkstringOptional
assessmentTipstringOptional
summarystringOptional
status'DRAFT' | 'PUBLISHED' | 'ARCHIVED'Required by declaration

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Campus · Screen guide

Library & circulation

Use library & circulation in the school workspace. Maintain titles and copies, lend books, manage reservations and handle fines.

Library & circulation illustrated banner

Online guide · Guided demo

What you can do

01

Add book

02

Add copy

03

Issue a book

04

Reserve a title

05

Edit policy

06

Edit book

07

Archive book

08

Edit copy

09

Workspace

Access & 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.
Required permission keys
library:view

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

How the workflow works

  1. 01

    Create a title and its physical copies

    A school account with the permissions shown below.

  2. 02

    Check borrower eligibility and issue an available copy

    Add copy is part of the documented workflow.

  3. 03

    Return or renew the loan and review reservations

    Issue a book is part of the documented workflow.

  4. 04

    Review overdue items and any permitted fine action

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

Rules & current limits

  • Availability, borrower policy and reservation rules affect issue/renewal. A fine record is distinct from a fee gateway payment.

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

Academics · Screen guide

Live classes & recordings

Use live classes & recordings in the school workspace. Schedule live lessons, manage their lifecycle and maintain recordings where configured.

Live classes & recordings illustrated banner

Online guide · Guided demo

What you can do

01

List

02

Create

03

Cancel

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
live-class:viewlive-class:createlive-class:update

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

How the workflow works

  1. 01

    Create the class for the intended learners

    A school account with the permissions shown below.

  2. 02

    Review the scheduled time and class details

    Create is part of the documented workflow.

  3. 03

    Start the class and use the available joining experience

    Cancel is part of the documented workflow.

  4. 04

    End the session and review an available recording

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
classIdstringRequired by declaration
sectionIdstringOptional
subjectIdstringOptional
scheduledAtstringRequired by declaration
durationMinnumberOptional

Rules & current limits

  • Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity.

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

Academics · Screen guide

Live-class workspace

Use live-class workspace in the school workspace. Schedule live lessons, manage their lifecycle and maintain recordings where configured.

Live-class workspace illustrated banner

Online guide · Guided demo

What you can do

01

Get

02

Update

03

Remove

04

Start

05

End

06

Finalize Recording

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
live-class:viewlive-class:updatelive-class:delete

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

How the workflow works

  1. 01

    Create the class for the intended learners

    A school account with the permissions shown below.

  2. 02

    Review the scheduled time and class details

    Update is part of the documented workflow.

  3. 03

    Start the class and use the available joining experience

    Remove is part of the documented workflow.

  4. 04

    End the session and review an available recording

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

Request fields to understand

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

FieldDeclared typeInput
titlestringOptional
scheduledAtstringOptional
durationMinnumberOptional

Rules & current limits

  • Camera/microphone, media delivery and recordings depend on browser permissions and service configuration; a schedule alone does not prove media connectivity.

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

Academics · Screen guide

Courses & lessons

Use courses & lessons in the school workspace. Build a course structure and let learners open lessons and record progress.

Courses & lessons illustrated banner

Online guide · Guided demo

What you can do

01

Course catalogue

02

Modules

03

Lessons

04

Video assets

05

Publishing

06

Learner progress

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
lms:viewlms:create

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

How the workflow works

  1. 01

    Create a course and its details

    A school account with the permissions shown below.

  2. 02

    Add modules and lessons in the intended order

    Modules is part of the documented workflow.

  3. 03

    Attach supported learning media and review visibility

    Lessons is part of the documented workflow.

  4. 04

    Open the learner course view and track lesson progress

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

Fields & controls

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

  • Course title
  • Description

Rules & 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.

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

Academics · Screen guide

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.

Course modules & lesson editor illustrated banner

Online guide · Guided demo

What you can do

01

Add module

02

Add lesson

03

Get Course

04

Update Course

05

Remove Course

06

Add Module

07

Remove Module

08

Add Lesson

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
lms:viewlms:updatelms:delete

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

How the workflow works

  1. 01

    Create a course and its details

    A school account with the permissions shown below.

  2. 02

    Add modules and lessons in the intended order

    Add lesson is part of the documented workflow.

  3. 03

    Attach supported learning media and review visibility

    Get Course is part of the documented workflow.

  4. 04

    Open the learner course view and track lesson progress

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

Request fields to understand

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

FieldDeclared typeInput
isPublishedbooleanOptional
titlestringRequired by declaration
sortOrdernumberOptional
contentTypestringRequired by declaration
videoUrlstringOptional
bodystringOptional
durationMinnumberOptional

Rules & 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.

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

Academics · Screen guide

Mark rechecks

Use mark rechecks in the school workspace. Plan examinations and seating, record marks, review rechecks and publish report cards.

Mark rechecks illustrated banner

Online guide · Guided demo

What you can do

01

Published-mark query

02

Review acknowledgement

03

Uphold/revise/reject decision

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
exam:viewexam:manage

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

How the workflow works

  1. 01

    Locate the published mark query

    A school account with the permissions shown below.

  2. 02

    Acknowledge review of the paper

    Review acknowledgement is part of the documented workflow.

  3. 03

    Record the permitted decision and review its result

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

Request fields to understand

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

FieldDeclared typeInput
examScheduleIdstringRequired by declaration
studentIdstringRequired by declaration
reasonstringRequired by declaration
outcome'UPHELD' | 'REVISED' | 'REJECTED'Required by declaration
revisedMarksnumberOptional
notesstringOptional

Rules & current limits

  • Published results are distinct from draft marks. Adaptive question attempts and paper rechecks have separate workflows.

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

Community · Screen guide

Notices, announcements & messages

Use notices, announcements & messages in the school workspace. Coordinate school notices, events, complaints, audience-based announcements and direct conversations.

Notices, announcements & messages illustrated banner

Online guide · Guided demo

What you can do

01

New

02

withdraw

03

Addressable contacts for the signed-in user

04

My conversations, most recent first

05

Get Thread

06

Start a conversation (or add to the existing one)

07

Send

08

Mark Read

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Choose the notice, announcement or conversation workflow

    A school account with the permissions shown below.

  2. 02

    Select the permitted audience and prepare the content

    withdraw is part of the documented workflow.

  3. 03

    Preview reachability before sending where available

    Addressable contacts for the signed-in user is part of the documented workflow.

  4. 04

    Review delivery reports, replies or complaint status

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

Request fields to understand

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

FieldDeclared typeInput
toUserIdstringRequired by declaration
bodystringRequired by declaration
subjectstringOptional
studentIdstringOptional
mutedbooleanRequired by declaration

Rules & current limits

  • External SMS, email and WhatsApp delivery requires configured providers. A saved record is not evidence that every recipient received it.

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

Intelligence · Screen guide

Multilingual explanations

Use the multilingual explanations workspace to review its saved runs, context and available actions.

Multilingual explanations illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
conceptstringOptional
levelstringOptional
languagesstring[]Optional
subjectIdstring | nullOptional
classIdstring | nullOptional
audience'STUDENT' | 'PARENT' | 'BOTH'Optional
publishbooleanOptional
titlestringOptional
bodystringOptional
parentTipstringOptional
status'DRAFT' | 'PUBLISHED' | 'PRIVATE' | 'ARCHIVED'Required by declaration

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Family portal · Screen guide

My department team

Use my department team in the school workspace. Let families, learners and staff see only their linked children or personal records.

My department team illustrated banner

Online guide · Guided demo

What you can do

01

Linked children

02

Attendance and fees

03

Published results

04

Homework and courses

05

Timetable

06

Library

07

PTM

08

Transport

09

Personal documents

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Sign in with the assigned department context

    A school account with the permissions shown below.

  2. 02

    Review your department and team

    Attendance and fees is part of the documented workflow.

  3. 03

    Use the displayed information within your own scope

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

Rules & current limits

  • Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls.

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

Family portal · Screen guide

My payslips

Use my payslips in the school workspace. Let families, learners and staff see only their linked children or personal records.

My payslips illustrated banner

Online guide · Guided demo

What you can do

01

Own salary slips

02

Period selection

03

Slip detail

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Sign in with a linked staff account

    A school account with the permissions shown below.

  2. 02

    Select a salary slip for the intended period

    Period selection is part of the documented workflow.

  3. 03

    Review your own available salary breakdown

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

Rules & current limits

  • Child ownership is resolved on the server. Family views omit staff-only notes, rosters and administrative controls.

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

School office · Screen guide

School dashboard

Use school dashboard in the school workspace. See school-wide priorities and manage the campus context used by the ERP.

School dashboard illustrated banner

Online guide · Guided demo

What you can do

01

School Admin dashboard KPIs (today + footprint)

02

Daily Action Center: everything pending today, scoped to the caller

03

Current school, branches and active session

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the school dashboard and current session

    A school account with the permissions shown below.

  2. 02

    Open an outstanding action in the relevant module

    Daily Action Center: everything pending today, scoped to the caller is part of the documented workflow.

  3. 03

    Inspect the campus counts and permitted branch settings

    Current school, branches and active session is part of the documented workflow.

  4. 04

    Review the consequences before closing a campus

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

Rules & current limits

  • Closing a populated campus is refused. The dashboard aggregates scoped records rather than replacing each module workflow.

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

Finance · Screen guide

Online payments & reconciliation

Use online payments & reconciliation in the school workspace. Create gateway orders, verify callbacks and investigate payments that remain pending.

Online payments & reconciliation illustrated banner

Online guide · Guided demo

What you can do

01

Payment orders

02

Callback verification

03

Pending payment review

04

Reconciliation

05

Gateway connection check

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
fee:viewfee:create

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

How the workflow works

  1. 01

    Review the invoice and provider readiness

    A school account with the permissions shown below.

  2. 02

    Create an order through the permitted checkout workflow

    Callback verification is part of the documented workflow.

  3. 03

    Verify the gateway response before treating the invoice as paid

    Pending payment review is part of the documented workflow.

  4. 04

    Investigate a pending payment through reconciliation

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

Fields & controls

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

  • Invoice ID
  • Amount (blank = full balance)

Rules & current limits

  • External collection requires approved gateway credentials and verified callbacks. The public guided demo does not charge money.

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

People · Screen guide

Payroll & salary structures

Use payroll & salary structures in the school workspace. Prepare salary structures, process payroll, review approvals and maintain salary slips.

Payroll & salary structures illustrated banner

Online guide · Guided demo

What you can do

01

Salary structures

02

Payroll processing

03

Approval

04

Mark paid

05

Salary slips

06

PDF generation

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create the applicable salary structure

    A school account with the permissions shown below.

  2. 02

    Process payroll for the selected period

    Payroll processing is part of the documented workflow.

  3. 03

    Review calculations and approve the run

    Approval is part of the documented workflow.

  4. 04

    Record payment status and review salary slips

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

Fields & controls

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

  • Name

Rules & current limits

  • Marking payroll paid records an administrative state; this feature does not by itself transfer money to a bank.

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

Platform · Screen guide

School plan & usage

Review your school’s plan, module access and quota usage.

School plan & usage illustrated banner

Online guide · Guided demo

What you can do

01

Current plan

02

Usage limits

03

Enabled modules

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the school plan view

    A school account with the permissions shown below.

  2. 02

    Review current quota consumption

    Usage limits is part of the documented workflow.

  3. 03

    Contact the platform administrator for a plan change when needed

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

Rules & current limits

  • Platform access is distinct from a school role. Online SaaS invoice collection and invitation delivery require configured providers.

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

School office · Screen guide

Year-end rollover

Use year-end rollover in the school workspace. Preview new-session student placement and apply or revert a recorded promotion batch.

Year-end rollover illustrated banner

Online guide · Guided demo

What you can do

01

Copy classes &amp; sections across

02

Undo

03

Dry-run a rollover — writes nothing

04

Copy classes/sections/subjects into the new session

05

Apply the rollover (transactional)

06

Revert

07

Batches

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
promotion:viewpromotion:createpromotion:managepromotion:delete

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

How the workflow works

  1. 01

    Choose the source and target academic sessions

    A school account with the permissions shown below.

  2. 02

    Clone or prepare the target class structure

    Undo is part of the documented workflow.

  3. 03

    Review the dry-run placement and exceptions

    Dry-run a rollover — writes nothing is part of the documented workflow.

  4. 04

    Commit only the reviewed batch and keep its reversal reference

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

Fields & controls

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

  • From (closing)
  • To (new year)
  • Min attendance %
  • Min average %
  • Hold students with dues

Rules & current limits

  • Preview writes nothing; commit changes enrollment. Locked sessions and school ownership checks still apply.

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

Community · Screen guide

Parent–teacher meetings

Use parent–teacher meetings in the school workspace. Publish meeting slots, book families, record discussion outcomes and manage follow-up tasks.

Parent–teacher meetings illustrated banner

Online guide · Guided demo

What you can do

01

Save meeting notes

02

Mark

03

Reschedule meeting

04

Add follow-up

05

New meeting slot

06

Save meeting slot

07

Edit slot

08

Book family

09

Read

Access & 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.
Required permission keys
communication:view

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

How the workflow works

  1. 01

    Create or choose the permitted teacher meeting slot

    A school account with the permissions shown below.

  2. 02

    Book the linked child and verify availability

    Mark is part of the documented workflow.

  3. 03

    Record the meeting outcome with the correct note visibility

    Reschedule meeting is part of the documented workflow.

  4. 04

    Assign and complete any follow-up action

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

Fields & controls

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

  • 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

Rules & current limits

  • Private staff notes and family-visible notes differ. Reminder actions do not guarantee external SMS, email or push delivery.

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

Finance · Screen guide

School reports

Use school reports in the school workspace. Review fee summaries, student distribution and examination summaries from permitted school data.

School reports illustrated banner

Online guide · Guided demo

What you can do

01

Exam Summary

02

Fee Summary

03

Students By Class

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose the report and reporting context

    A school account with the permissions shown below.

  2. 02

    Inspect the totals and available filters

    Fee Summary is part of the documented workflow.

  3. 03

    Compare the summary with the underlying records

    Students By Class is part of the documented workflow.

  4. 04

    Use the available export or print action when present

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

Rules & current limits

  • A summary is only as current as the entered records. Each report uses its implemented date and scope rules.

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

Administration · Screen guide

Roles & permissions

Use roles & permissions in the school workspace. Control which school users can view, create, edit, export and manage records.

Roles & permissions illustrated banner

Online guide · Guided demo

What you can do

01

Role catalogue

02

Permission catalogue

03

Role grants

04

User assignment

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
role:viewrole:create

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

How the workflow works

  1. 01

    Open a role and inspect its existing permissions

    A school account with the permissions shown below.

  2. 02

    Choose only the required permission keys

    Permission catalogue is part of the documented workflow.

  3. 03

    Save the role and assign eligible users

    Role grants is part of the documented workflow.

  4. 04

    Sign in as the affected role to review access

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

Request fields to understand

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

FieldDeclared typeInput
namestringRequired by declaration
keystringRequired by declaration
descriptionstringOptional

Rules & current limits

  • A role name alone does not grant platform administration. School scope and explicit guards still apply.

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

Administration · Screen guide

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.

Role permissions & user assignments illustrated banner

Online guide · Guided demo

What you can do

01

Permission Catalog

02

Get

03

Update

04

Remove

05

Set Permissions

06

Assignable Users

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
role:viewrole:updaterole:deleterole:manage

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

How the workflow works

  1. 01

    Open a role and inspect its existing permissions

    A school account with the permissions shown below.

  2. 02

    Choose only the required permission keys

    Get is part of the documented workflow.

  3. 03

    Save the role and assign eligible users

    Update is part of the documented workflow.

  4. 04

    Sign in as the affected role to review access

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
descriptionstringOptional
permissionKeysstring[]Required by declaration
userIdstringRequired by declaration

Rules & current limits

  • A role name alone does not grant platform administration. School scope and explicit guards still apply.

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

People · Screen guide

Staff directory & lifecycle

Use staff directory & lifecycle in the school workspace. Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement.

Staff directory & lifecycle illustrated banner

Online guide · Guided demo

What you can do

01

Offboard

02

Reinstate

03

Download Template

04

Export to Excel

05

List

06

List Former

07

Add a staff member

08

What still depends on this person

09

Mark a staff member as having left

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Find or create the staff profile

    A school account with the permissions shown below.

  2. 02

    Review employment details and linked responsibilities

    Reinstate is part of the documented workflow.

  3. 03

    Inspect clearance before offboarding

    Download Template is part of the documented workflow.

  4. 04

    Use reinstatement when returning a former staff member

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

Request fields to understand

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

FieldDeclared typeInput
employeeCodestringRequired by declaration
firstNamestringRequired by declaration
lastNamestringOptional
genderstringOptional
dateOfBirthstringOptional
emailstringOptional
phonestringOptional
branchIdstringOptional
departmentIdstringOptional
designationIdstringOptional
reportsToIdstringOptional
joiningDatestringOptional
contractTypestringOptional
qualificationsunknownOptional
exitStatus'RESIGNED' | 'TERMINATED' | 'RETIRED'Optional
exitDatestringOptional
reasonstringOptional
forcebooleanOptional

Rules & current limits

  • Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action.

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

People · Screen guide

Staff profile & clearance

Use staff profile & clearance in the school workspace. Maintain staff profiles, inspect connected responsibilities and record departure or reinstatement.

Staff profile & clearance illustrated banner

Online guide · Guided demo

What you can do

01

Directory

02

Staff creation

03

Profile 360

04

Clearance

05

Offboarding

06

Reinstatement

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Find or create the staff profile

    A school account with the permissions shown below.

  2. 02

    Review employment details and linked responsibilities

    Staff creation is part of the documented workflow.

  3. 03

    Inspect clearance before offboarding

    Profile 360 is part of the documented workflow.

  4. 04

    Use reinstatement when returning a former staff member

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

Rules & current limits

  • Offboarding is separate from deleting historical school activity. Permission and dependency checks govern each action.

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

People · Screen guide

Staff attendance

Use staff attendance in the school workspace. Record staff check-in/out and maintain an administrative daily and monthly register.

Staff attendance illustrated banner

Online guide · Guided demo

What you can do

01

Check in

02

Check out

03

Mark all present

04

The caller's own attendance history and check-in state

05

All staff with their status for a date

06

Mark/correct staff attendance for a date

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Check the current personal attendance state

    A school account with the permissions shown below.

  2. 02

    Clock in or out through the self-service action

    Check out is part of the documented workflow.

  3. 03

    Use the authorized daily roster to correct records

    Mark all present is part of the documented workflow.

  4. 04

    Review the monthly register and holiday policy

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

Fields & controls

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

  • Date

Rules & current limits

  • Self-service acts on the caller’s staff profile. Administrative corrections need separate access.

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

People · Screen guide

Staff leave requests

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

Staff leave requests illustrated banner

Online guide · Guided demo

What you can do

01

Approve

02

Decline

03

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

04

Self-service: my own leave history

05

Admin: pending leave requests awaiting a decision

06

Admin: approve or reject a leave request

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Choose staff leave or student absence reporting

    A school account with the permissions shown below.

  2. 02

    Enter the applicable dates and reason

    Decline is part of the documented workflow.

  3. 03

    Submit or review through the permitted role

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

  4. 04

    Check the final decision and attendance impact

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

Fields & controls

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

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

Rules & current limits

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

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

Intelligence · Screen guide

Staff workload

Use the staff workload workspace to review its saved runs, context and available actions.

Staff workload illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
overloadThresholdnumberOptional
mediumThresholdnumberOptional
underutilizedRationumberOptional
labelstringOptional
absentStaffIdstringRequired by declaration
datestringOptional
applybooleanOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

School office · Screen guide

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.

Student exit & transfer certificates illustrated banner

Online guide · Guided demo

What you can do

01

Clearance review

02

Outstanding dependency checks

03

Exit register

04

Transfer-certificate number

05

TC generation

06

Readmission

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:createstudent-exit:viewstudent-exit:createstudent-exit:manage

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

How the workflow works

  1. 01

    Locate the student and review clearance

    A school account with the permissions shown below.

  2. 02

    Resolve blockers before recording the exit

    Outstanding dependency checks is part of the documented workflow.

  3. 03

    Review the allocated TC number and generate the permitted document

    Exit register is part of the documented workflow.

  4. 04

    Use readmission only for an approved reversal

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

Request fields to understand

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

FieldDeclared typeInput
firstNamestringRequired by declaration
middleNamestringOptional
lastNamestringOptional
admissionNostringRequired by declaration
rollNostringOptional
genderstringOptional
dateOfBirthstringOptional
bloodGroupstringOptional
sessionIdstringOptional
classIdstringOptional
sectionIdstringOptional
admissionDatestringOptional
phonestringOptional
emailstringOptional
statusstringRequired by declaration
exitDatestringOptional
reasonstringOptional
remarkstringOptional
issueTcbooleanOptional
forcebooleanOptional

Rules & current limits

  • Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record.

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

People · Screen guide

Student absence review

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

Student absence review illustrated banner

Online guide · Guided demo

What you can do

01

Approve

02

Decline

03

Withdraw

04

Report a planned or past absence for a student

05

List

06

Approve an absence, marking those days excused

07

Cancel

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
attendance:viewattendance:manage

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

How the workflow works

  1. 01

    Choose staff leave or student absence reporting

    A school account with the permissions shown below.

  2. 02

    Enter the applicable dates and reason

    Decline is part of the documented workflow.

  3. 03

    Submit or review through the permitted role

    Withdraw is part of the documented workflow.

  4. 04

    Check the final decision and attendance impact

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

Request fields to understand

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

FieldDeclared typeInput
studentIdstringRequired by declaration
fromDatestringRequired by declaration
toDatestringOptional
reasonstringOptional
leaveTypestringOptional
attachmentUrlstringOptional
approvebooleanRequired by declaration

Rules & current limits

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

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

School office · Screen guide

Student directory

Use student directory in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit.

Student directory illustrated banner

Online guide · Guided demo

What you can do

01

Download Template

02

Export to Excel

03

List

04

Create

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:create

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

How the workflow works

  1. 01

    Create or open the student profile

    A school account with the permissions shown below.

  2. 02

    Review guardian contacts and required documents

    Export to Excel is part of the documented workflow.

  3. 03

    Use the gate-pass workflow for an authorized early release

    List is part of the documented workflow.

  4. 04

    Use clearance and exit workflows for withdrawal or transfer

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

Fields & controls

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

  • Admission No
  • First name
  • Last name
  • Gender
  • Section

Rules & current limits

  • Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record.

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

School office · Screen guide

Student profile & guardians

Use student profile & guardians in the school workspace. Maintain student profiles, guardians and documents, and manage campus release or school exit.

Student profile & guardians illustrated banner

Online guide · Guided demo

What you can do

01

Verify

02

Send back

03

Remove

04

List

05

Upload a document for a student

06

Mark a document as checked against the original

07

Send a document back with a reason

08

Get Profile360

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:updatestudent:managestudent:delete

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

How the workflow works

  1. 01

    Create or open the student profile

    A school account with the permissions shown below.

  2. 02

    Review guardian contacts and required documents

    Send back is part of the documented workflow.

  3. 03

    Use the gate-pass workflow for an authorized early release

    Remove is part of the documented workflow.

  4. 04

    Use clearance and exit workflows for withdrawal or transfer

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

Request fields to understand

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

FieldDeclared typeInput
typestringRequired by declaration
titlestringOptional
expiresAtstringOptional
reasonstringRequired by declaration

Rules & current limits

  • Campus release is distinct from withdrawal from the school rolls. Transfer certificates require a valid exited record.

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

Academics · Screen guide

Teacher cover

Use teacher cover in the school workspace. Build recurring class schedules and arrange dated teacher cover with clash checks.

Teacher cover illustrated banner

Online guide · Guided demo

What you can do

01

Assign

02

Withdraw

03

A day's timetable with substitutions applied

04

List Substitutions

05

Who could cover an absent teacher (suggestions only)

06

Record cover for all of an absent teacher's periods on a date

07

Assign one substitute to one period on one date

08

Remove Substitution

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
timetable:viewtimetable:createtimetable:delete

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

How the workflow works

  1. 01

    Select the section, teacher and date

    A school account with the permissions shown below.

  2. 02

    Create a period with its subject, time and room

    Withdraw is part of the documented workflow.

  3. 03

    Resolve overlap warnings before saving

    A day's timetable with substitutions applied is part of the documented workflow.

  4. 04

    Arrange dated cover and review the daily plan

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

Request fields to understand

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

FieldDeclared typeInput
absentStaffIdstringRequired by declaration
datestringRequired by declaration
applybooleanOptional
reasonstringOptional
autoGeneratedbooleanOptional
periodIdstringRequired by declaration
substituteStaffIdstringRequired by declaration

Rules & current limits

  • Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view.

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

Finance · Screen guide

Tally export

Use tally export in the school workspace. Prepare accounting vouchers for the configured Tally integration.

Tally export illustrated banner

Online guide · Guided demo

What you can do

01

Download XML

02

Test Connection

03

Export Vouchers

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
settings:viewfee:export

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

How the workflow works

  1. 01

    Review the accounting data and integration settings

    A school account with the permissions shown below.

  2. 02

    Check the configured connection in a controlled environment

    Test Connection is part of the documented workflow.

  3. 03

    Export the selected voucher records

    Export Vouchers is part of the documented workflow.

  4. 04

    Reconcile the receiving system with the exported result

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

Fields & controls

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

  • From Date
  • To Date

Rules & current limits

  • An export endpoint does not prove that a live Tally instance is connected or that vouchers were imported successfully.

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

People · Screen guide

Staff tasks

Use staff tasks in the school workspace. Assign work to school staff and let each user complete their own task list.

Staff tasks illustrated banner

Online guide · Guided demo

What you can do

01

Mark done

02

List

03

Create

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Create a task with the intended staff assignment

    A school account with the permissions shown below.

  2. 02

    Review its due date and current state

    List is part of the documented workflow.

  3. 03

    The assigned user opens their own task queue

    Create is part of the documented workflow.

  4. 04

    Complete the task and review the updated record

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

Request fields to understand

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

FieldDeclared typeInput
titlestringRequired by declaration
descriptionstringOptional
assignedToIdstringRequired by declaration
dueDatestringOptional
prioritystringOptional
categorystringOptional
checklistChecklistItemDto[]Optional

Rules & current limits

  • School staff tasks are separate from the platform marketing Demo & Follow-up Workspace.

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

Academics · Screen guide

Timetable & teacher cover

Use timetable & teacher cover in the school workspace. Build recurring class schedules and arrange dated teacher cover with clash checks.

Timetable & teacher cover illustrated banner

Online guide · Guided demo

What you can do

01

Add period

02

Save period

03

Save cover

04

Edit period

05

Delete period

06

period

07

Daily schedule

08

Weekly timetable

09

Read

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Select the section, teacher and date

    A school account with the permissions shown below.

  2. 02

    Create a period with its subject, time and room

    Save period is part of the documented workflow.

  3. 03

    Resolve overlap warnings before saving

    Save cover is part of the documented workflow.

  4. 04

    Arrange dated cover and review the daily plan

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

Fields & controls

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

  • Schedule date
  • Class / section
  • Teacher view
  • Period section
  • Weekday
  • Period number
  • Subject
  • Period teacher
  • Period type
  • Substitute teacher
  • Cover reason
  • Cover status

Rules & current limits

  • Workspace checks include section, teacher and room overlaps. Weekly templates retain the recurring teacher; dated cover appears in the daily view.

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

Campus · Screen guide

Transport operations

Use transport operations in the school workspace. Manage buses, routes, stops and student allocations, then run daily boarding registers.

Transport operations illustrated banner

Online guide · Guided demo

What you can do

01

Save

02

Notify families

03

Complete trip

04

Start trip

05

Add bus

06

Edit bus

07

Remove bus

08

Add route

09

Read

10

List Fuel Logs

11

Create Fuel Log

12

Fleet Locations

Access & 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.
Required permission keys
transport:viewtransport:create

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

How the workflow works

  1. 01

    Set up the bus, route and ordered stops

    A school account with the permissions shown below.

  2. 02

    Allocate students within the directional seat capacity

    Notify families is part of the documented workflow.

  3. 03

    Start today’s trip and record boarding/drop-off

    Complete trip is part of the documented workflow.

  4. 04

    Complete the run and review family-visible updates

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

Fields & controls

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

  • Active
  • Correction reason
  • Trip closing notes
  • Trip date
  • Trip route
  • Trip direction
  • Filter route
  • Bus
  • Fill-up date
  • Litres
  • Amount
  • Odometer

Rules & 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.

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

Intelligence · Screen guide

Transport ETA

Use the transport eta workspace to review its saved runs, context and available actions.

Transport ETA illustrated banner

Online guide · Guided demo

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

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

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

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

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

Request fields to understand

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

FieldDeclared typeInput
vehicleIdstringOptional
routeIdstringOptional
scope'VEHICLE' | 'FLEET'Optional
lateThresholdMinnumberOptional
stalePingMinnumberOptional
labelstringOptional

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

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

Institutions · Screen guide

Tuition batches & demos

Use tuition batches & demos in the school workspace. Manage tuition subjects, teaching batches, student enrollment and prospective demo classes.

Tuition batches & demos illustrated banner

Online guide · Guided demo

What you can do

01

Create

02

Delete

03

Enrol

04

Book

05

Convert

06

File

07

Tuition center overview stats

08

List subjects available for batches

09

List students (for enrollment)

10

List all batches

11

Create a new batch

12

Update a batch

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
student:viewstudent:createstudent:updatestudent:delete

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

How the workflow works

  1. 01

    Create the subject and teaching batch

    A school account with the permissions shown below.

  2. 02

    Enroll the eligible student with the applicable terms

    Delete is part of the documented workflow.

  3. 03

    Schedule and review prospective demo classes

    Enrol is part of the documented workflow.

  4. 04

    Maintain progress reports and enrollment state

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

Request fields to understand

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

FieldDeclared typeInput
namestringOptional
subjectIdstringRequired by declaration
teacherStaffIdstringOptional
typeBatchTypeOptional
startDatestringRequired by declaration
endDatestringOptional
maxStudentsnumberOptional
monthlyFeenumberOptional
schedulestringOptional
roomNostringOptional
statusBatchStatusOptional
batchIdstringRequired by declaration
studentIdstringRequired by declaration
enrolledAtstringOptional
discountAmountnumberOptional
notesstringOptional
prospectNamestringRequired by declaration
prospectPhonestringRequired by declaration
prospectEmailstringOptional
scheduledAtstringRequired by declaration
periodstringOptional
marksObtainednumberOptional
maxMarksnumberOptional
gradestringOptional

Rules & current limits

  • Tuition prospect demos are distinct from the platform’s AVKUL ERP product demos.

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

Websites · Screen guide

School website CMS

Use school website cms in the school workspace. Manage school themes, content pages and published website information from the ERP.

School website CMS illustrated banner

Online guide · Guided demo

What you can do

01

Edit Content

02

Activate theme

03

Remove

04

List Themes

05

Create Theme

06

Update Theme

07

Activate Theme

08

Remove Theme

09

List Pages

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
website:viewwebsite:createwebsite:updatewebsite:delete

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

How the workflow works

  1. 01

    Review the school website theme and branding

    A school account with the permissions shown below.

  2. 02

    Create or edit the intended content page

    Activate theme is part of the documented workflow.

  3. 03

    Preview and check the content and contact information

    Remove is part of the documented workflow.

  4. 04

    Publish the page and review the public school URL

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

Fields & controls

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

  • Name
  • Title
  • Type

Rules & current limits

  • School website content is separate from the platform marketing Landing Page CMS. Publish controls use school ownership and permissions.

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

People · Screen guide

Approval workflows

Use approval workflows in the school workspace. Configure approval chains and let the responsible approver act on the current step.

Approval workflows illustrated banner

Online guide · Guided demo

What you can do

01

Approve

02

Reject

03

Remove

04

+ Add step

05

Approvals waiting on me right now

06

Approve or reject my current step

07

List

08

Create

09

Update

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
settings:viewsettings:createsettings:updatesettings:delete

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

How the workflow works

  1. 01

    Create a workflow definition and its ordered steps

    A school account with the permissions shown below.

  2. 02

    Review the workflow linked to the business record

    Reject is part of the documented workflow.

  3. 03

    The current approver opens their pending queue

    Remove is part of the documented workflow.

  4. 04

    Record the decision and inspect the next step

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

Request fields to understand

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

FieldDeclared typeInput
decision'APPROVED' | 'REJECTED'Required by declaration
remarkstringOptional
namestringOptional
entityTypestringRequired by declaration
descriptionstringOptional
stepsWorkflowStepDto[]Optional
isActivebooleanOptional

Rules & current limits

  • Approval is limited to the current eligible approver; it is separate from directly editing the source business record.

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

Administration · Screen guide

ERP sign-in

Sign in to the ERP using your assigned account. The public guided demo runs separately with fictional data.

ERP sign-in illustrated banner

Online guide · Guided demo

What you can do

01

Assigned identifier

02

Password

03

School code where required

04

Role-based workspace

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the ERP sign-in page

    A school account with the permissions shown below.

  2. 02

    Enter the assigned identifier, password and school code when required

    Password is part of the documented workflow.

  3. 03

    Open the workspace available to your role

    School code where required is part of the documented workflow.

  4. 04

    Log out when finished

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

Rules & current limits

  • Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited.

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

Administration · Screen guide

Choose your ERP workspace

Navigate between the platform console, school office and family portal using the signed-in role.

Choose your ERP workspace illustrated banner

Online guide · Guided demo

What you can do

01

Platform workspace

02

School workspace

03

Family portal

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Sign in with the assigned account

    A school account with the permissions shown below.

  2. 02

    Open the workspace available to your role

    School workspace is part of the documented workflow.

  3. 03

    Use the navigation to open a permitted module

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

Rules & current limits

  • Public guided demos do not issue ERP credentials. Impersonation is restricted to platform administrators and is audited.

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

School office · Screen guide

Public certificate verification

Check a school-issued certificate using its verification link or token.

Public certificate verification illustrated banner

Online guide · Guided demo

What you can do

01

Token verification

02

Certificate validity

03

Revoked or unavailable feedback

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.

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

How the workflow works

  1. 01

    Open the verification link printed on the issued document

    A school account with the permissions shown below.

  2. 02

    Review the returned certificate status

    Certificate validity is part of the documented workflow.

  3. 03

    Ask the issuing school about an invalid or revoked document

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

Rules & current limits

  • Verification requires an actual generated token. Sample demo certificates are not school-issued documents.

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

Intelligence · AI tool

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.

Auto Report Card Remarks illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
exam:update

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

How the workflow works

  1. 01

    Open School AI Tools and select “Auto Report Card Remarks”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Attendance Anomaly Detection illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
attendance:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Attendance Anomaly Detection”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available section id fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Section Id

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Fee Defaulter Prediction illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
fee:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Fee Defaulter Prediction”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Question Paper Generator illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
exam:create

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Question Paper Generator”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available subject, topic, count, difficulty fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Subject
  • Topic
  • Count
  • Difficulty

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Discipline Pattern Detection illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Discipline Pattern Detection”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Parent Chatbot illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Parent Chatbot”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, question fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Question

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Study Buddy illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
lms:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Study Buddy”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available lesson id, question fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Lesson Id
  • Question

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Career/Stream Counselor illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Career/Stream Counselor”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Timetable Optimizer illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
timetable:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Timetable Optimizer”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available timetable id fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Timetable Id

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Smart Inventory Reorder illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
inventory:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Smart Inventory Reorder”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Notice/Circular Writer illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
communication:create

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Notice/Circular Writer”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available bullet points, language fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Bullet Points
  • Language

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Alumni Mentorship Matching illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Alumni Mentorship Matching”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, interest area fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Interest Area

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Voice-to-Attendance illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
attendance:create

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

How the workflow works

  1. 01

    Open School AI Tools and select “Voice-to-Attendance”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available section id, transcript fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Section Id
  • Transcript

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Photo-based Visitor Verification illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
hostel:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Photo-based Visitor Verification”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available image url, claimed name, visitor log id, reference image url fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Image Url
  • Claimed Name
  • Visitor Log Id
  • Reference Image Url

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Repeat Visitor Pattern Detection illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
hostel:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Repeat Visitor Pattern Detection”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available days fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Days

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Biometric Face Match illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
hostel:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Biometric Face Match”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available source image url, target image url fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Source Image Url
  • Target Image Url

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Predictive Dropout Risk illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Predictive Dropout Risk”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Personalized Learning Path illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
lms:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Personalized Learning Path”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, days, regenerate fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Days
  • Regenerate

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Early Learning Gap Detection illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:viewlms:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Early Learning Gap Detection”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available section id, weeks fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Section Id
  • Weeks

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Adaptive Online Exams illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
exam:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Adaptive Online Exams”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, subject id, answers json fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Subject Id
  • Answers Json

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Lesson Planner illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
timetable:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Lesson Planner”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available class id, subject id, topic, week of, regenerate fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Class Id
  • Subject Id
  • Topic
  • Week Of
  • Regenerate

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Multilingual Explain illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
lms:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Multilingual Explain”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available concept, level, languages, publish fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Concept
  • Level
  • Languages
  • Publish

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Enrolment & Capacity Forecast illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:manage

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

How the workflow works

  1. 01

    Open School AI Tools and select “Enrolment & Capacity Forecast”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available conversion pct, default section capacity, students per teacher, label fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Conversion Pct
  • Default Section Capacity
  • Students Per Teacher
  • Label

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Cashflow Prediction illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
fee:manage

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

How the workflow works

  1. 01

    Open School AI Tools and select “Cashflow Prediction”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available scholarship pct, months, collection rate pct, label fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Scholarship Pct
  • Months
  • Collection Rate Pct
  • Label

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Staff Workload Optimizer illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
timetable:viewattendance:update

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

How the workflow works

  1. 01

    Open School AI Tools and select “Staff Workload Optimizer”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available overload threshold, medium threshold, underutilized ratio, label fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Overload Threshold
  • Medium Threshold
  • Underutilized Ratio
  • Label

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Transport ETA + Route AI illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
transport:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Transport ETA + Route AI”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available scope, vehicle id, route id, late threshold min, label fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Scope
  • Vehicle Id
  • Route Id
  • Late Threshold Min
  • Label

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Hostel/Inventory Demand Forecast illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
inventory:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Hostel/Inventory Demand Forecast”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available lookback days, horizon days, occupancy boost pct, category, label fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Lookback Days
  • Horizon Days
  • Occupancy Boost Pct
  • Category
  • Label

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Parent Copilot (WhatsApp) illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Parent Copilot (WhatsApp)”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, question, channel fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Question
  • Channel

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

WhatsApp Copilot Simulator illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “WhatsApp Copilot Simulator”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available from, text, dry run fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • From
  • Text
  • Dry Run

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Voice School Assistant illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Voice School Assistant”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, transcript fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Transcript

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Progress Story for Parents illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Progress Story for Parents”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, language fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Language

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Career Twin illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Career Twin”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, interests, psychometric json fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Interests
  • Psychometric Json

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Alumni Opportunity Matcher illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Alumni Opportunity Matcher”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available student id, opportunity type, interest area fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Student Id
  • Opportunity Type
  • Interest Area

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Campus Safety AI illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
hostel:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Campus Safety AI”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available vehicle id, days fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Vehicle Id
  • Days

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Wellbeing / Sentiment Radar illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
health:manage

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

How the workflow works

  1. 01

    Open School AI Tools and select “Wellbeing / Sentiment Radar”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

AI Audit Trail illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “AI Audit Trail”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available decision, request id, note, corrected text, feature fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Decision
  • Request Id
  • Note
  • Corrected Text
  • Feature

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Fairness Monitor illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
student:manage

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

How the workflow works

  1. 01

    Open School AI Tools and select “Fairness Monitor”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Data Minimization Mode illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:viewsettings:update

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

How the workflow works

  1. 01

    Open School AI Tools and select “Data Minimization Mode”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available save, biometric enabled, face match enabled, biometric retention days, parent opt out default fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Save
  • Biometric Enabled
  • Face Match Enabled
  • Biometric Retention Days
  • Parent Opt Out Default

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Auto Grading + Rubric Feedback illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
exam:update

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

How the workflow works

  1. 01

    Open School AI Tools and select “Auto Grading + Rubric Feedback”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available assignment id, student id, submission text, publish fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Assignment Id
  • Student Id
  • Submission Text
  • Publish

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Classroom Insight Board illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
attendance:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Classroom Insight Board”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available section id fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Section Id

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Substitution Brain illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
timetable:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Substitution Brain”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available absent staff id, date fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Absent Staff Id
  • Date

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Question Bank Intelligence illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
exam:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Question Bank Intelligence”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available subject id, paper size fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Subject Id
  • Paper Size

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Meeting Notes → Actions illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
communication:create

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

How the workflow works

  1. 01

    Open School AI Tools and select “Meeting Notes → Actions”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available transcript, meeting type fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Transcript
  • Meeting Type

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

School Twin Benchmarking illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “School Twin Benchmarking”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Policy Copilot illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Policy Copilot”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available question, board fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Question
  • Board

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Auto Accreditation Pack illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Auto Accreditation Pack”

    An authorised school account and the permissions for this tool.

  2. 02

    Enter the available purpose fields

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Fields & controls

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

  • Purpose

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Intelligence · AI tool

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.

Branch Performance Copilot illustrated banner

Online guide · Guided demo

What you can do

01

Tool-specific input

02

Available result review

03

Provider-dependent output

04

Human review

Access & 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.
Required permission keys
dashboard:view

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

How the workflow works

  1. 01

    Open School AI Tools and select “Branch Performance Copilot”

    An authorised school account and the permissions for this tool.

  2. 02

    Review the available school context for this tool

    Available result review is part of the documented workflow.

  3. 03

    Run the tool and check the provider/sample-output banner

    Provider-dependent output is part of the documented workflow.

  4. 04

    Inspect the result and confirm important details against school records

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

Rules & 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.

Individual tool checked in current source. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Homepage

Home at D&D International School — knowledge, character and community.

School website: Homepage illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

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

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

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

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: About our school

About our school at D&D International School — knowledge, character and community.

School website: About our school illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

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

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

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

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Vision & mission

Vision & mission at D&D International School — knowledge, character and community.

School website: Vision & mission illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

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

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Principal’s message

Principal’s message at D&D International School — knowledge, character and community.

School website: Principal’s message illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Academics

Academics at D&D International School — knowledge, character and community.

School website: Academics illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Curriculum & learning

Curriculum & learning at D&D International School — knowledge, character and community.

School website: Curriculum & learning illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Campus & facilities

Campus & facilities at D&D International School — knowledge, character and community.

School website: Campus & facilities illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Campus life

Campus life at D&D International School — knowledge, character and community.

School website: Campus life illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Events & celebrations

Events & celebrations at D&D International School — knowledge, character and community.

School website: Events & celebrations illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: School journal

School journal at D&D International School — knowledge, character and community.

School website: School journal illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Admissions

Admissions at D&D International School — knowledge, character and community.

School website: Admissions illustrated banner

Online guide · Guided demo

What you can do

01

Published school information

02

Consented enquiry form

03

Receipt reference

04

ERP admissions connection

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the public school page

    No ERP account is required to read the public page.

  2. 02

    Review school information and complete the enquiry fields

    Consented enquiry form is part of the documented workflow.

  3. 03

    Give consent and submit the request

    Receipt reference is part of the documented workflow.

  4. 04

    Keep the receipt reference; school staff manage the enquiry in ERP

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Guardian/contact name
  • Contact details
  • Enquiry message
  • Consent

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Fees & scholarships

Fees & scholarships at D&D International School — knowledge, character and community.

School website: Fees & scholarships illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: School transport

School transport at D&D International School — knowledge, character and community.

School website: School transport illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Parent resources

Parent resources at D&D International School — knowledge, character and community.

School website: Parent resources illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: School calendar

School calendar at D&D International School — knowledge, character and community.

School website: School calendar illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Frequently asked questions

Frequently asked questions at D&D International School — knowledge, character and community.

School website: Frequently asked questions illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Careers

Careers at D&D International School — knowledge, character and community.

School website: Careers illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Contact & visits

Contact & visits at D&D International School — knowledge, character and community.

School website: Contact & visits illustrated banner

Online guide · Guided demo

What you can do

01

Published school information

02

Consented enquiry form

03

Receipt reference

04

ERP admissions connection

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the public school page

    No ERP account is required to read the public page.

  2. 02

    Review school information and complete the enquiry fields

    Consented enquiry form is part of the documented workflow.

  3. 03

    Give consent and submit the request

    Receipt reference is part of the documented workflow.

  4. 04

    Keep the receipt reference; school staff manage the enquiry in ERP

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Guardian/contact name
  • Contact details
  • Enquiry message
  • Consent

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Website guide

School website: Privacy & website information

Privacy & website information at D&D International School — knowledge, character and community.

School website: Privacy & website information illustrated banner

Online guide · Guided demo

What you can do

01

Published page content

02

School navigation

03

Responsive display

04

Contact and admissions links

Access & setup

Intended access: Public reader.

  • No ERP account is required to read the public page.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the published page

    No ERP account is required to read the public page.

  2. 02

    Read the available school content

    School navigation is part of the documented workflow.

  3. 03

    Use the school navigation or contact link for the next step

    Review the result in the connected record or workspace before moving on.

Rules & 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.

Published page metadata checked live on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

School office · Access guide

Applicant self-service portal

Use a privately issued application link to save a draft, upload documents and request a campus visit.

Applicant self-service portal illustrated banner

Online guide · Guided demo

What you can do

01

Seven-day capability link

02

Draft save and resume

03

PDF/image documents up to 10 MB

04

Review feedback and resubmission

05

Visit preferences

06

Application submission

Access & setup

Intended access: Assigned account with the required permissions.

  • Use the official link and the applicable access context.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the private link issued by the school

    Use the official link and the applicable access context.

  2. 02

    Save guardian/application details and supported documents

    Draft save and resume is part of the documented workflow.

  3. 03

    Review feedback and resubmit a rejected document if needed

    PDF/image documents up to 10 MB is part of the documented workflow.

  4. 04

    Submit when the required documents are received

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Application details
  • Guardian details
  • Required documents
  • Visit preferences

Rules & 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.

Implementation checked against the delivered release guide. Guide availability confirms documentation publication, not certification of every external service or device flow.

Family portal · Access guide

Parent account invitation

Accept the school’s private post-admission invitation and choose a parent account password.

Parent account invitation illustrated banner

Online guide · Guided demo

What you can do

01

24-hour invitation

02

Single-use acceptance

03

Guardian-chosen password

04

Parent-only account

Access & setup

Intended access: Assigned account with the required permissions.

  • Use the official link and the applicable access context.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Open the private invitation from the school after admission

    Use the official link and the applicable access context.

  2. 02

    Choose and confirm the required password

    Single-use acceptance is part of the documented workflow.

  3. 03

    Accept the invitation once

    Guardian-chosen password is part of the documented workflow.

  4. 04

    Sign in with the assigned guardian identifier and school code

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Password
  • Password confirmation

Rules & current limits

  • Existing accounts are not reset through invitations.
  • Invitations are not automatically delivered by SMS/email and are never included in public documentation.

Implementation checked against the delivered release guide. Guide availability confirms documentation publication, not certification of every external service or device flow.

Mobile · Access guide

AVKUL ERP Android app

Install the published Android app and use the same assigned school account on mobile.

AVKUL ERP Android app illustrated banner

Online guide · Guided demo

What you can do

01

Signed Android APK

02

Role-based mobile workspaces

03

Shared school account

04

52 source screens

05

Logout clears account cache

Access & setup

Intended access: Assigned account with the required permissions.

  • Use the official link and the applicable access context.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Download the AVKUL ERP Android APK from the official link

    Use the official link and the applicable access context.

  2. 02

    Install on a compatible Android device when permitted by your device policy

    Role-based mobile workspaces is part of the documented workflow.

  3. 03

    Sign in with the assigned account and school code

    Shared school account is part of the documented workflow.

  4. 04

    Use the modules available to your role and log out when finished

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Identifier
  • Password
  • School code

Rules & 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.

Implementation checked against the delivered release guide. Guide availability confirms documentation publication, not certification of every external service or device flow.

Websites · Access guide

AVKUL ERP marketing website

Explore platform capabilities and request a product walkthrough from the public AVKUL ERP homepage.

AVKUL ERP marketing website illustrated banner

Online guide · Guided demo

What you can do

01

Platform overview

02

Stakeholder views

03

Questions and answers

04

Walkthrough enquiry

05

Roadmap

06

Privacy choices

Access & setup

Intended access: Platform administrator.

  • Use the official link and the applicable access context.

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Explore the public platform sections

    Use the official link and the applicable access context.

  2. 02

    Open a documentation guide or guided demo

    Stakeholder views is part of the documented workflow.

  3. 03

    Use Request a walkthrough for a personalised product conversation

    Review the result in the connected record or workspace before moving on.

Fields & controls

The screen exposes the following context or input controls. Required fields are validated by the live application.

  • Name
  • School
  • Email
  • Phone
  • Student range
  • Consent

Rules & current limits

  • A walkthrough enquiry does not create an ERP login.
  • Analytics collection follows browser privacy preferences and configured collection rules.

Implementation checked against the delivered release guide. Guide availability confirms documentation publication, not certification of every external service or device flow.