MODULE GUIDE · 11 OCT 2026

Parent–teacher meetings

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

Try guided demo →Download guide ↓

OVERVIEW

What you can do

Teacher slots

Family bookings

Reschedule and cancel

Meeting notes

Family-visible follow-ups

In-app reminders

BEFORE YOU BEGIN

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.

STEP BY STEP

How the workflow works

01
Create or choose the permitted teacher meeting slot
An assigned school account with the required permissions.
02
Book the linked child and verify availability
Family bookings is part of the documented workflow.
03
Record the meeting outcome with the correct note visibility
Reschedule and cancel is part of the documented workflow.
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.

Field	Declared type	Input
`id`	string	Optional
`staffId`	string	Required by declaration
`date`	string	Required by declaration
`startTime`	string	Required by declaration
`endTime`	string	Required by declaration
`capacity`	number	Optional
`location`	string	Optional
`isActive`	boolean	Optional
`version`	string	Optional
`slotId`	string	Required by declaration
`studentId`	string	Required by declaration
`notes`	string	Optional
`status`	string	Required by declaration
`reason`	string	Optional
`privateNotes`	string	Optional
`feedback`	string	Optional
`bookingId`	string	Required by declaration
`title`	string	Required by declaration
`owner`	"SCHOOL" \| "FAMILY"	Required by declaration
`dueDate`	string	Optional
`force`	boolean	Optional
`parentId`	string	Optional

CURRENT BEHAVIOUR

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.

LEARN BY DOING

Try parent–teacher meetings

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

Launch guided demo →

FOR IMPLEMENTERS

API & permissions reference

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

15 source-declared operations

GET/api/v1/ptm/workspace

Read

communication:view

POST/api/v1/ptm/workspace/slots

Slot

communication:create

Declared request fields: id (optional), staffId (required), date (required), startTime (required), endTime (required), capacity (required), location (optional), isActive (optional), version (optional).

POST/api/v1/ptm/workspace/slots/:id/delete

Remove

communication:delete

Declared request fields: version (required).

POST/api/v1/ptm/workspace/bookings

Book

communication:create

Declared request fields: slotId (required), studentId (optional), notes (optional), version (optional).

POST/api/v1/ptm/workspace/bookings/:id/change

Change

communication:update

Declared request fields: version (required), slotId (optional), status (optional), reason (optional), privateNotes (optional), feedback (optional), studentId (optional).

POST/api/v1/ptm/workspace/bookings/:id/notes

Notes

communication:update

Declared request fields: version (required), slotId (optional), status (optional), reason (optional), privateNotes (optional), feedback (optional), studentId (optional).

POST/api/v1/ptm/workspace/follow-ups

Task

communication:update

Declared request fields: bookingId (required), id (optional), title (required), owner (required), dueDate (optional), status (required), version (optional).

POST/api/v1/ptm/workspace/remind

Remind

communication:create

Declared request fields: slotId (required).

GET/api/v1/ptm/slots

List Slots

communication:view

POST/api/v1/ptm/slots

Create Slot

communication:create

Declared request fields: staffId (required), date (required), startTime (required), endTime (required), capacity (optional).

PATCH/api/v1/ptm/slots/:id

Update Slot

communication:update

Declared request fields: version (optional).

DELETE/api/v1/ptm/slots/:id

Remove Slot

communication:delete

Declared request fields: version (optional), force (optional).

GET/api/v1/ptm/bookings

List Bookings

communication:view

POST/api/v1/ptm/bookings

Create Booking

communication:create

Declared request fields: version (optional), slotId (required), studentId (required), parentId (optional), notes (optional).

PATCH/api/v1/ptm/bookings/:id/status

Update Booking Status

communication:update

Declared request fields: version (optional), reason (optional), status (required).

Open the actual application

ERP links use your assigned account. Record-specific pages start from the list so you can choose a real record.

/en/school/ptmOpen ↗

Parent–teacher meetings

What you can do

Teacher slots

Family bookings

Reschedule and cancel

Meeting notes

Family-visible follow-ups

In-app reminders

Access & setup

How the workflow works

Create or choose the permitted teacher meeting slot

Book the linked child and verify availability

Record the meeting outcome with the correct note visibility

Assign and complete any follow-up action

Request fields to understand

Rules & current limits

Try parent–teacher meetings

API & permissions reference

Open the actual application

Keep exploring