AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Notices, announcements & messages

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

Try guided demo →Download guide ↓
Notices, announcements & messages — illustrated workflow banner

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.

Try notices, announcements & messages

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

Launch guided demo →

API & permissions reference

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

7 source-declared operations
GET/api/v1/communication/notices

Notices

communication:view
POST/api/v1/communication/notices

Create Notice

communication:create

Declared request fields: title (required), body (optional), audience (optional), isPinned (optional), classId (optional), sectionId (optional), expiresAt (optional).

GET/api/v1/communication/events

Events

communication:view
POST/api/v1/communication/events

Create Event

communication:create

Declared request fields: title (required), description (optional), startAt (required), endAt (optional), venue (optional), audience (optional), rsvpEnabled (optional), category (optional), isAllDay (optional), classId (optional), sectionId (optional).

GET/api/v1/communication/complaints

Complaints

communication:view
POST/api/v1/communication/complaints

Create Complaint

communication:create

Declared request fields: subject (required), description (optional), category (optional), priority (optional), studentId (optional).

PATCH/api/v1/communication/complaints/:id

Update Complaint

communication:update

Declared request fields: status (optional), resolution (optional).

Open the actual application

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

Keep exploring