Academics

Online Admissions

Publish provider-owned offerings, collect applicant details and documents, review submissions, accept provider applicants, and convert Campus-backed accepted applicants into students.

How online admissions works

Online Admissions lets an active education provider publish selected offerings on a provider-neutral public admissions portal. Campus-backed offerings still require an approved organization with public admissions enabled. Applicants do not create an account. They submit contact and application details, complete human verification, and upload the documents configured in the published admission form version.

Application lifecycle

Configure Admissions Setup
Publish or open offering
Applicant submits
Review application
Request updates or decide
Accept provider applicant or convert Campus student

Application email is not automatically the login email

The application email is used for status and document-update messages. During final student admission, the organization reviews the prefilled form and chooses the student login email.

Enable public admissions

  1. 1For Campus-backed offerings, open Settings and enable Online Admissions for the organization.
  2. 2Review the submission and status email templates used for applicant updates.
  3. 3Open Admissions Setup and select the offering.
  4. 4Configure public summary, delivery, dates, locations, fees, funding, eligibility, and a published admission form.
  5. 5Confirm readiness, then publish or open the offering.
  6. 6Review `/admissions` and the provider page before sharing a public link.
  • Provider is active.
  • Campus organization is approved and public admissions are enabled when the offering is Campus-backed.
  • Program and optional Campus department are active and visible for admissions.
  • Offering is open and inside its configured opening and closing dates.
  • Campus curriculum and academic cycle are active and complete when the offering is Campus-backed.
  • Fees and eligibility are disclosed, even when the amount is zero or admission is open.
  • Applicant email delivery and document storage are configured.

Configure required documents

Each published admission form version owns its document checklist. Every requirement has a student-facing label and can include a description, required flag, accepted file types, size limit, expiry-date rule, file-count limit, and display order.

  • Use labels applicants can recognize, such as Previous transcript or Identity document.
  • Mark only genuinely mandatory files as required.
  • Keep accepted file types and size limits practical for mobile applicants.
  • Publish a new form version when the checklist changes. Existing submissions keep their original document snapshot.

Provider-neutral public API

New public admissions clients should use the versioned `/v1/public/admissions` routes. These routes are offering-first and do not require an organization slug. Legacy organization routes remain available for Campus provider pages.

  • `GET /v1/public/admissions/offerings` lists open offerings with provider, program, delivery, location, deadline, fees, funding, eligibility, and form metadata.
  • `GET /v1/public/admissions/offerings/:id` returns the full applicant-safe offering detail and published application form.
  • `GET /v1/public/admissions/providers/:slug` returns one provider and its open offerings.
  • `POST /v1/public/admissions/offerings/:id/submissions` accepts no-login applicant answers, Cap verification, and required documents.
  • `GET|POST /v1/public/admissions/submissions/update/:token[/documents]` supports secure document update links sent by email.

Applicant submission and updates

  1. 1Open the public Admissions page and choose an organization.
  2. 2Choose one available program offering.
  3. 3Complete the student information form and attach each required document.
  4. 4Complete the Cap human-verification control and submit once.
  5. 5Keep the application reference shown after submission and watch the submitted email address for updates.
  6. 6When the organization requests missing documents, use the expiring email link to review the checklist and upload replacements.

No applicant account is required

Public application and document-update links do not create a student login. Update links are private, expire, and stop working after final admission.

Review and decide applications

Open Online Admissions to search by applicant or reference and filter by status, department, program, offering, academic cycle, submission date, or missing required documents. Org Admin sees the organization; Sub Admin and Manager results follow department scope.

StatusMeaning
SubmittedA new application is waiting for review.
Under reviewStaff are checking details and documents.
Needs updateThe applicant has been asked for missing or corrected information.
AcceptedThe application can proceed to student admission.
AdmittedA student record was created and linked.
RejectedThe decision is retained in the rejected view with its history.
WithdrawnThe application is retained but no longer active.

Read and write permissions differ

Org Admin, scoped Sub Admin, and scoped Manager can review visible applications. Status decisions and student conversion are limited to Org Admin and Sub Admin.

Convert an accepted applicant to a student

  1. 1Accept the reviewed application.
  2. 2Choose Admit student to open the existing student admission form with applicant data prefilled.
  3. 3Review and correct identity, contact, academic, and enrollment fields.
  4. 4Choose the final student login email; it may differ from the application email.
  5. 5Create the student and confirm the selected program and curriculum match the offering.
  6. 6EduVerse links the student and marks the application Admitted in one operation.

Keep rejected records

Rejecting an application moves it to the rejected status view. It does not delete the submission, documents, or decision history.