---
title: Approve or reject
description: >-
  Record an admissions decision by setting application status, complete field
  review, and send the automatic review email to the applicant.
sidebar:
  order: 2
---

**Approving or rejecting** an application means setting a **decision status** on a submission — **Accepted**, **Conditionally accepted**, **Rejected**, **Needs update**, or another pipeline value — after review is complete. Fuxam sends a **review email** and in-app notification to the applicant for most decision statuses, summarizing the outcome and any field-level feedback.

This is the formal decision point in the admissions funnel. Everything upstream — [application forms](/docs/fuxam-web/apply/application-forms), portal submission, [review of the submission](/docs/fuxam-web/apply/applicants/review-an-application) — leads here. Everything downstream — [stage progression](/docs/fuxam-web/apply/applicants/move-to-next-stage), **Enrolled** status, [user provisioning](/docs/fuxam-web/base/user-management), [cohort placement](/docs/fuxam-web/cms/programs-and-planning/study-programs-cohorts) — depends on the status you set now.

## Why it matters

Applicants need timely, documented decisions. Status changes in Campus Management are the system of record: they update what applicants see in **My Submissions**, trigger [email notifications](/docs/fuxam-web/apply/apply-portal-settings/email-notifications), and may start enrollment workflows. A clear accept/reject/conditional decision closes the evaluation loop and lets admissions teams move to onboarding or free capacity for waitlisted candidates.

For staff, the status selector and the **Send Request Changes Email** action ensure feedback captured during field review reaches the applicant in one structured message rather than scattered manual emails.

## Key concepts

| Term | Meaning |
|---|---|
| **Decision status** | The application status you set to record outcome — e.g. **Accepted**, **Rejected**, **Conditionally accepted**. |
| **Review email** | Automated email sent when administrators set a decision status (not for **Draft** or **Pending**). |
| **Send Request Changes Email** | Item in the **⋯** menu of a submission that completes the field review and emails the applicant. No field marked for changes → status **Accepted**; at least one field marked for changes → **Needs Update**. |
| **Confirmation email** | Separate automatic receipt sent when the applicant first submits the form. |
| **Enrollment workflows** | Processes that may start when status reaches **Enrolled** — user account creation, study contract signing, system code assignment. |

## Confirmation email behavior

| Event | Email |
|---|---|
| Applicant submits form | Automatic **confirmation email** (receipt) |
| Administrator sets decision status | **Review email** with decision and feedback |
| Status set to Draft or Pending | No review email sent |

Review emails include the form title, program name, decision, and any field comments configured in the review workflow.

## How to set the status

1. In **Campus Management → Applications**, click the applicant's name to open the full submission page. For a quick look from the list, hover over the name and click **Preview** to open the detail sheet instead (see [Review an application](/docs/fuxam-web/apply/applicants/review-an-application)).

2. Open the status selector at the top right (labelled **Application Status** in the detail sheet) and choose the decision, for example **Accepted**, **Conditionally Accepted**, **Rejected** or **Needs Update**.

3. For **Accepted**, **Conditionally Accepted** or **Enrolled**, the **Preview Study Contract** dialog opens first. Check the summary, click **Preview contract** if you want to see the document, then click **Continue**. In the detail sheet you then confirm the study program and cohort (**Confirm and continue**) or answer **Add Study Programs or Cohorts?**.

4. On the full submission page, **Needs Update** and **Conditionally Accepted** ask **Send Request Changes Email?**. Click **Send** to notify the applicant, or **Don't Send** to change only the status.

Choose **Needs update** when the applicant can correct specific answers rather than when the application is finally declined — pair it with field comments from review.

## How to complete field review and notify

When using per-field review:

1. Mark each field with **Accept** or **Mark for Changes** and add a comment where the applicant has to fix something. The banner above the fields counts accepted, changes-requested and pending fields.

2. Open the **⋯** menu in the header and click **Send Request Changes Email**. The item appears once at least one field is reviewed and the applicant is not **Accepted** yet.

3. If at least one field is marked for changes, confirm **Send Request Changes Email?** with **Send**. The status changes to **Needs Update** and the applicant gets an email with your field comments.

4. If no field is marked for changes, the **Preview Study Contract** dialog opens first. Click **Continue**, then **Send**. The status changes to **Accepted** and the applicant is notified.

:::warning
Despite its name, **Send Request Changes Email** also accepts the applicant when no field is marked for changes. Check the banner before you click it. For a decision without field review, use the status selector instead.
:::

## Decision guidance

| Status | When to use |
|---|---|
| **Accepted** | Applicant meets all requirements; unconditional offer. |
| **Conditionally accepted** | Offer extended but documents, contract, or other conditions remain. |
| **Rejected** | Application does not meet requirements and cannot be remedied. |
| **Needs update** | Applicant can correct or supplement answers and resubmit. |
| **Enrolled** | Onboarding complete — applicant is placed in the cohort (see enrollment warning below). |

For the full pipeline and recommended order between statuses, see [Move to next stage](/docs/fuxam-web/apply/applicants/move-to-next-stage).

:::warning
Moving a submission to **Enrolled** may trigger enrollment workflows (user account creation, study contract signing, system code assignment). Confirm prerequisites such as signed study contracts when your institution requires them.
:::

## Best practices

- **Review before deciding** — Open and evaluate the [submission](/docs/fuxam-web/apply/applicants/review-an-application) before setting **Accepted** or **Rejected**.
- **Use conditional acceptance for fixable gaps** — **Conditionally accepted** keeps the pipeline open while tracking contract and document completion; use **Pending requirements** (when visible) for deadline tracking.
- **Batch with care** — [Bulk process applications](/docs/fuxam-web/apply/applicants/bulk-process-applications) sends review emails to every selected row; verify selection before confirming.
- **Align with email policy** — Understand which notifications are automatic in [Email notifications](/docs/fuxam-web/apply/apply-portal-settings/email-notifications) so applicants are not surprised by duplicate manual messages.

## Common pitfalls

- **Setting Enrolled too early** — Enrollment may create users and assign cohorts; confirm contracts and conditions first.
- **Expecting email for Draft or Pending** — Those statuses do not trigger review emails; applicants may still be editing.
- **Rejecting without comments** — When field review is used, comments help applicants understand the outcome even for rejections.

## FAQ

**What is the difference between Rejected and Needs update?**

**Needs update** invites the applicant to correct specific answers and resubmit. **Rejected** closes the application as declined. Use **Needs update** only when resubmission is allowed and meaningful.

**Can I change a decision after sending the review email?**

You can change the status again with the status selector on the submission page or in the detail sheet, which may send another review email (except for **Draft** or **Pending**). Consider [communicating](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant) context for sensitive reversals.

**Does acceptance automatically enroll the applicant?**

Not necessarily. Many institutions use **Accepted** or **Conditionally accepted** first, then move to **Enrolled** after onboarding steps. Acceptance dialogs may prompt for cohort assignment when configured.

## Related pages

**[Move to next stage](/docs/fuxam-web/apply/applicants/move-to-next-stage)**

Understand the full status pipeline and recommended progression.

**[Email notifications](/docs/fuxam-web/apply/apply-portal-settings/email-notifications)**

Notification types and preferences for applicants.

**[Bulk process applications](/docs/fuxam-web/apply/applicants/bulk-process-applications)**

Apply decisions to multiple submissions at once.

**[Review an application](/docs/fuxam-web/apply/applicants/review-an-application)**

Evaluate answers before finalizing a decision.
