> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zionapp.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Admissions overview
> How prospective families become enrolled students, from application to conversion
Admissions turns applications into enrolled students. It is a six-stage pipeline that administrators work from a kanban board, with applicants entering either through a public application form or through manual staff entry.
Admissions is limited to administrators. Supervisors, monitors, parents, and students do not have access to this feature.
## The pipeline
Every application moves through fixed stages, always in this order:
| Stage | Meaning |
| ------------ | ------------------------------------------ |
| Applied | Application submitted, not yet reviewed |
| Under Review | Staff are evaluating the applicant |
| Accepted | Approved for enrollment, not yet converted |
| Waitlisted | Held for a future opening |
| Rejected | Not proceeding |
| Enrolled | Converted into a student record |
Waitlisted and Rejected are terminal off-ramps. Enrolled is reached only through the one-click convert action described in [Managing applications](/features/admissions/managing-applications), never by dragging a card into that column on the board.
## Two ways applications enter the pipeline
A prospective family fills out the form at `/apply/[your-org-slug]` without needing an account. They provide applicant details (name required, date of birth and desired grade or centre optional) and guardian details (name and email required, phone optional), and can attach up to 10 documents. The application enters the pipeline at Applied with its source recorded as online.
An administrator clicks Add applicant on the board and fills the same form fields on behalf of a walk-in visitor or phone enquiry. The application enters the pipeline at Applied with its source recorded as staff-entered.
## Sharing the public application form
Each school has its own application link, built from its organization slug: `/apply/[your-org-slug]`. Share this link on your website, in enrollment emails, or on printed materials so families can apply without contacting the office first.
Your organization slug is the identifier Clerk assigned your school. Confirm it with your administrator team if you are unsure which slug your organization uses.
Combine your app's domain with `/apply/` and your slug, for example `https://yourapp.com/apply/your-school-slug`.
Post the link wherever prospective families will see it. No login is required to submit the form.
After submitting, the family sees an in-form thank-you message with no personal data echoed back, and a matching standalone confirmation page is available at `/apply/[your-org-slug]/confirmation`.
The form determines which school an application belongs to strictly from the slug in the URL. Sharing the wrong link sends an application to the wrong school.
## Where to find it
Administrators reach the admissions board from the sidebar under People & Centres > Admissions (`/admin/admissions`). A link to funnel analytics is available from the board's header.
## Subscription requirement
Viewing the board and opening an applicant's detail drawer does not require an active subscription. Writing to admissions (adding an applicant, moving a stage, uploading a document, converting to student) and viewing funnel analytics both require an active subscription. Without one, these actions are blocked.
Work the kanban board, review applicants, and convert accepted applications to students.
See stage counts and conversion rates across the admissions pipeline.
See what happens to a student record created by admissions conversion.
Confirm which roles can access which features.