AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Admissions & applicant journey

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

Try guided demo →Download guide ↓
Admissions & applicant journey — illustrated workflow banner

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.

Try admissions & applicant journey

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.

14 source-declared operations
GET/api/v1/admissions/work-queue

Queue

admission:view
GET/api/v1/admissions/enquiries/due

Leads due a follow-up, oldest overdue first

admission:view
GET/api/v1/admissions/enquiries/funnel

Pipeline by stage and by source, with conversion

admission:view
GET/api/v1/admissions/enquiries

List

admission:view
GET/api/v1/admissions/enquiries/:id/follow-ups

History

admission:view
POST/api/v1/admissions/enquiries/:id/follow-ups

Record a contact attempt and move the lead on

admission:update

Declared request fields: summary (required), channel (optional), outcome (optional), status (optional), followUpAt (optional), byStaffId (optional).

POST/api/v1/admissions/enquiries

Create

admission:create

Declared request fields: studentName (required), parentName (optional), phone (optional), email (optional), classApplying (optional), source (optional), notes (optional).

PATCH/api/v1/admissions/enquiries/:id

Update

admission:update

Declared request fields: status (optional).

DELETE/api/v1/admissions/enquiries/:id

Remove

admission:update
GET/api/v1/admissions/applications

List

admission:view
GET/api/v1/admissions/applications/funnel

Where applicants are, and how many converted

admission:view
POST/api/v1/admissions/applications

Open an application, optionally from an enquiry

admission:create

Declared request fields: studentName (required), enquiryId (optional), applicationNo (optional), classApplying (optional), applicationFee (optional), feePaid (optional), formData (optional).

POST/api/v1/admissions/applications/:id/advance

Move the application one legal step

admission:manage

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

GET/api/v1/admissions/applications/:id/journey

Get

admission:view

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