Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Applicants

Campus Management workspace to review applicant submissions across the Pending, In progress, and Accepted tabs, filter by status and program, and process decisions.

Applicants is the Campus Management workspace where admissions staff review submissions, change application status, send email, and run bulk actions. Open it from Campus Management → Applications (feature Application Management).

The page title in the app is Applications. Submissions are organized in tabs with badge counts. Configuration for programs and forms lives on sibling tabs (Forms, Analytics, Question catalog); day-to-day pipeline work happens on Pending, In progress, and Accepted.

Why it matters

Universities need a single source of truth for who applied, to which program and cohort, and where each file stands. The Applicants area provides filtering, sorting, and bulk actions so teams can work through high-volume intakes without losing track of individual cases.

Every status change, review completion, or manual email ties back to the submission record and, when configured, triggers email notifications. Decisions recorded here are what applicants see in My Submissions on the Apply portal.

Before you start

Requirement Detail
Feature Application Management enabled (application_management)
View list Permission to view application programs
Change status / bulk actions Permission to update application programs
Send email Permission to create emails (create:emails)
Delete submissions Permission to delete application programs (delete:application-programs)
Upstream setup At least one application program with a published form

Key concepts

Concept Description
Pending tab Default landing view — submissions that are not Accepted (and not Enrolled, which Application Management hides from these lists).
In progress tab Incomplete applications still in Pending status with no submission date — applicants started but have not submitted.
Accepted tab Submissions with status Accepted only — for tracking offers and onboarding before enrollment workflows take over.
Application status Pipeline position shown in the table selector: Draft, Pending, Submitted, Under Review, Needs Update, Conditionally Accepted, Accepted, Rejected, Withdrawn (and related values). Enrolled is not listed here.
Detail sheet Right-side panel with applicant info, form answers, field review, and status controls.
Bulk toolbar When rows are selected: Status selector plus More Options (⋯) for Send Reminder, Send Email, and Delete.

For the full status pipeline, see Move to next stage.

Open the applicants list

Go to Campus Management → Applications. Primary submission tabs:

Tab Shows
Pending Active pipeline submissions that are not yet Accepted (default landing tab)
In progress Started applications that have not been submitted yet
Accepted Submissions with status Accepted

Each tab shows a table with applicant name, email, program, cohort, status, submission date, and other columns configured for your institution. With no rows selected you may also see Export and Create Applicant when you have the matching permissions.

Filter applicants

Use the table filter bar:

  • Name and Email — text search
  • Application status — values available for the current tab (for example Submitted, Under Review, Needs Update on Pending)
  • Program — study program
  • Cohort — intake cohort
  • Term — academic term when configured

Filters combine with pagination and column sorting.

When to use which filter

Goal Suggested filters
Triage new submissions Pending tab + Application status = Submitted
Find files under evaluation Application status = Under Review
Follow incomplete applications In progress tab
Track a specific intake Cohort + Program
Monitor post-offer pipeline Accepted tab; filter by cohort

Typical workflow

  1. Triage — Filter Submitted on Pending; optionally bulk-move to Under Review (Bulk process applications).
  2. Review — Open each file in the detail sheet; use field-level review when enabled.
  3. Decide — Approve or reject, or set Needs Update and communicate if context is needed.
  4. Advance — Move to next stage through Conditionally Accepted → Accepted → Enrolled as conditions are met (enrollment may leave Application Management lists).
  5. Hand off — Confirm enrollment workflows (user account, cohort placement) per your institution's rules.

Best practices

  • Work from status, not memory — Set the correct application status so colleagues and applicants see accurate pipeline position.
  • Review before deciding — Open the detail sheet and complete field review before Complete review or final acceptance.
  • Use bulk actions carefully — Bulk status updates send review emails; confirm the target status for every selected row.
  • Separate manual email from decisions — Use Communicate with an applicant for informational messages; use status changes when the decision itself should be notified.
  • Coordinate with enrollment — Before bulk-accepting large cohorts, confirm cohort capacity and enrollment prerequisites.

Common pitfalls

  • Skipping status updates — Leaving submissions at Submitted when review has started makes reporting and applicant-facing status misleading.
  • Looking for Enrolled here — Enrolled submissions are hidden from Application Management tabs; use user management / cohort tools for enrolled students.
  • Assuming email always sends — Review emails are not sent for Draft or Pending status changes.
  • Missing permissions — Without update or email permissions, Status, Send Email, or Delete may be hidden even though you can view the list.

In this section

Last updated on

Was this page helpful?