Skip to main content
DeanDesk handles admissions through the Onboarding Policy Manager, where you configure every aspect of your school’s application and enrollment process. Applicants complete a guided set of steps — profile, forms, fees, program selection — and submit for review. Your admissions team then manages applications through a queue with customizable statuses and role-based access.

How admissions works in DeanDesk

The admissions process has three parts:
  1. Configuration — Admins set up requirements in the Onboarding Policy Manager (registration rules, required forms, fees, statuses, and reviewer permissions).
  2. Application — Applicants sign up at your school’s portal and work through a step-by-step dashboard to complete all requirements and submit their application.
  3. Review — Your admissions team reviews submitted applications in the Admissions Queue, updates statuses, and approves or rejects applicants.

Configure admissions with the Onboarding Policy Manager

The Onboarding Policy Manager is located at Admin Dashboard → Onboarding Policy Manager. It contains five tabs that control your entire admissions flow.

Tab 1: Registration Settings

This tab controls who can apply, what information is required, and how applications are processed.
SettingWhat it does
Self RegistrationEnable or disable public sign-ups at your school’s portal
Initial RoleThe role assigned to new sign-ups (e.g. applicant, student, or public)
Require Full ProfileApplicants must complete all profile fields before submitting
Require Profile PictureApplicants must upload a profile photo
Require Payment SetupApplicants must add a payment method (via Stripe) during onboarding
Auto-Accept OnboardingAutomatically approve applicants who complete all requirements — no admin review needed
Parents Enroll ChildrenEnable the parent-child flow where parents create applications on behalf of their children
Require Child RegistrationParents must register at least one child before submitting
Allow Adult EnrollmentParents can also enroll themselves in programs (in addition to their children)
Credit Card Transaction FeeAdd an optional surcharge (percentage and/or flat amount) on card payments

Tab 2: Required Forms

This is where you attach forms to your admissions process. Forms are created in the Form Manager page and then selected here in the Onboarding Policy Manager.
1

Create your forms in the Form Manager

Go to Admin Dashboard → Form Manager and create the forms you need (e.g. “Parent Questionnaire”, “Health & Emergency Contact”, “Student Essay”). Each form can include multiple question types: multiple choice, short answer, long answer, and file upload.
2

Assign forms in the Onboarding Policy Manager

Go to Admin Dashboard → Onboarding Policy Manager → Required Forms tab. You will see three form categories:
  • Required Forms (Adult) — Forms that adult applicants must complete before submitting.
  • Optional Forms — Forms shown to applicants but not required for submission.
  • Child Application Forms — Forms that must be completed for each child application (when parent-child enrollment is enabled).
Use the autocomplete to search and select forms from your Form Manager. You can add multiple forms to each category.
You can update which forms are required at any time. New applicants will see the updated form requirements. Existing applicants who have already submitted are not affected.

Tab 3: Application Statuses

Application statuses define the stages of your review pipeline. DeanDesk includes four locked system statuses:
StatusPurpose
DraftApplication has not been submitted yet
Under ReviewApplication has been submitted and is awaiting review
ApprovedApplicant has been accepted
RejectedApplicant has been denied
You can create custom intermediate statuses to match your school’s workflow (e.g. “Interview Scheduled”, “Waitlisted”, “Scholarship Review”). For each status you can configure:
  • Title and description
  • Color for visual identification in the queue
  • Email template that is automatically sent to the applicant when their status changes (supports placeholders: {{firstName}}, {{lastName}}, {{email}}, {{statusTitle}}, {{statusDescription}})
Drag and drop statuses to reorder them and reflect your review workflow sequence.

Tab 4: Permissions & Committees

Control who on your team can access and manage applications.
RoleAccess level
Admissions HeadA single designated user with full access to all applications and the ability to make final decisions (approve/reject)
Full Process TeachersTeachers who can view and manage applications across all stages
Stage-Assigned TeachersTeachers assigned to specific review stages — they only see applications in their assigned stage, can leave notes and recommendations, but cannot approve or reject
1

Set the Admissions Head

Select a user to serve as the admissions head. This person has full oversight of the pipeline.
2

Add Full Process Teachers (optional)

Select teachers who should have visibility into all applications at every stage.
3

Assign teachers to stages (optional)

For each custom status (e.g. “Interview Scheduled”), assign specific teachers. Those teachers will only see applications that are currently in their assigned stage.

Tab 5: Application Rollout

This tab is for schools migrating from the legacy admissions mode to the cycle-based admissions system. The cycle-based system supports multiple admissions rounds, application tracks, and per-track requirement overrides. See Admission Cycles below for details.

Application fees

You can require applicants to pay fees before submitting their application. Fees are configured in the Onboarding Policy Manager under Registration Settings.
1

Enable application fees

Toggle on application fees and configure one or more fee line items. For each fee, set a name, amount, and description. You can also enable fees separately for child applications.
2

Mark fees as waivable (optional)

If a fee is marked as waivable, applicants can request a fee waiver during the application process. Waiver requests appear in the admin queue for approval or rejection.
3

Connect Stripe

Application fees are processed through Stripe. Make sure your Stripe account is connected under Admin Dashboard → Stripe Configuration before enabling fees.
Fee waivers are managed at Admin Dashboard → Admissions. When a waiver is approved, the applicant’s fee requirement is marked as resolved and they can proceed with submission.

The applicant experience

Applicants access your school’s portal (e.g. yourschool.deandesk.com), create an account, and are presented with a step-by-step onboarding dashboard. The steps shown depend on the policies you configured in the Onboarding Policy Manager.

Onboarding steps

The applicant dashboard walks applicants through the following steps (each step only appears if the corresponding policy is enabled):
1

Complete profile

The applicant fills out their personal information. If Require Full Profile is enabled, all profile fields must be completed. If Require Profile Picture is enabled, a photo must be uploaded.
2

Register children (if enabled)

If Parents Enroll Children is enabled, the parent creates one or more child applications. For each child, they provide the child’s name, date of birth, emergency contact, medical information, and complete any child-specific forms configured in the Onboarding Policy Manager.
3

Complete required forms

The applicant fills out all required forms and any optional forms they choose to complete. A progress indicator shows how many forms are done.
4

Add payment method (if required)

If Require Payment Setup is enabled, the applicant adds a credit or debit card via Stripe.
5

Select program enrollment (if required)

If Require Program Enrollment is enabled, the applicant selects the tuition or program products they are enrolling in. Payment can be collected now or deferred, depending on your policy settings.
6

Pay application fees (if enabled)

If application fees are configured, the applicant pays the required fees or submits a fee waiver request (for waivable fees).
7

Submit application

Once all required steps are complete, the applicant submits their application. The status changes from Draft to Under Review and your admissions team is notified.
If Auto-Accept Onboarding is enabled and the applicant has completed all requirements, the application is automatically approved without entering the review queue.

The Admissions Queue

The Admissions Queue is where your team reviews and manages submitted applications. Go to Admin Dashboard → Admissions.

Viewing applications

The queue displays all applications with:
  • Applicant name and contact information
  • Current status (color-coded to match your configured statuses)
  • Submission date
  • Assigned reviewer
  • Fee payment status
Use filters to narrow by status, reviewer, submission date, or search by applicant name.

Reviewing an application

1

Open the application

Click an applicant’s name to open their application details.
2

Review submitted information

View the applicant’s profile, all completed form submissions, child applications (if applicable), program selections, and fee payment status.
3

Leave a review note

Add internal notes with your assessment. Notes are timestamped and attributed to the reviewer. If you are a stage-assigned teacher, you can also include a recommended status (e.g. recommend approval).
4

Assign to a reviewer (optional)

Assign the application to a specific team member for review. You can also set a default assignee for incoming applications.
5

Update the status

Change the application status from the status dropdown. If the status has an email template configured, the applicant is notified automatically. You can add a custom message and file attachments to the notification email.

Approving an applicant

When you set an application’s status to Approved:
  1. The applicant receives the acceptance notification (if an email template is configured for the Approved status).
  2. For child applications, admins can convert the child record into a full student account, which creates a new user with the student role.
  3. The student can then be enrolled in courses either manually through User Management or automatically if program enrollment was completed during the application process.

Admission Cycles

For schools that run multiple admissions rounds, DeanDesk supports a cycle-based admissions system. This is an advanced feature that builds on top of the standard onboarding flow.

What cycles and tracks are

  • Admission Cycle — A single admissions round with its own open/close dates, policies, and statuses (e.g. “Fall 2026 Admissions”, “Spring 2026 Early Enrollment”).
  • Application Track — A pathway within a cycle with its own requirements, forms, and fees (e.g. “Elementary K-2”, “Online Certificate Program”, “In-Person Bootcamp”). Tracks let you customize the admissions experience for different applicant groups within the same cycle.

Creating a cycle

1

Create a new cycle

Go to Admin Dashboard → Admissions → Cycles and click New Cycle. Set the cycle name, open and close dates, and optionally link it to an academic year or term.
2

Configure cycle statuses (optional)

Each cycle can have its own set of application statuses, or it can inherit the school-wide statuses you configured in the Onboarding Policy Manager.
3

Set as active

Mark the cycle as the active cycle so that new applicants are directed to it.

Creating tracks within a cycle

1

Open the cycle

Navigate to the cycle you created and go to Tracks.
2

Add a track

Create a track with a name, description, and audience type (adult, child, family, or mixed). You can link the track to specific programs, courses, or products.
3

Override requirements (optional)

Each track can override the school-wide onboarding policies. For example, a track can require different forms, charge different fees, or use a different status workflow than the school default.

How cycle-based applications work for applicants

In cycle-based mode, applicants see a dashboard that lists all their applications. They can start a new application by selecting a cycle and optionally a track. Each application has its own set of requirements (based on the track’s overrides or the school defaults) and progresses independently through the review pipeline.
Applicants can have multiple active applications simultaneously — for example, applying to different tracks within the same cycle or applying across multiple cycles.

Parent and child applications

When Parents Enroll Children is enabled in the Onboarding Policy Manager, the admissions flow supports a two-layer application structure:
  1. Parent application — The parent completes their own profile, forms, and fees.
  2. Child applications — The parent creates one or more child applications within their own application. Each child has their own name, date of birth, medical information, and dedicated set of forms (configured as Child Application Forms in the Onboarding Policy Manager).
After a child application is approved, an admin can convert the child record into a full student account from the Admissions Queue. This creates a new user with the student role, linked to the parent.
If Require Child Registration is enabled, the parent must register and submit at least one child application before they can submit their own application.