---
title: "Review Applicants"
label: "Review applicants"
description: "Review native applications, download resumes, move candidates through the built-in ATS pipeline, and view or delete applications from your dashboard."
publishedAt: 2026-05-20
updatedAt: 2026-10-30
order: 8
status: "published"
faqs:
  - question: Can I see applications as the board operator?
    answer: "Yes. In your dashboard, open Jobs and choose View applications from a job's menu, or select its Applications count. You see every native application for that job, can open each one, and can delete an application when someone asks you to remove their data. Employers still run the hiring pipeline from the employer portal on your board."
  - question: Can I delete one application without deleting the job seeker's account?
    answer: "Yes. Deleting an application removes that application, its resume, employer notes, and activity history. The job seeker's profile and account stay in place. Owners and admins can delete applications; editors can view them."
  - question: Can I still send candidates to an external ATS?
    answer: "Yes. Use an external application URL when the employer wants candidates to apply through their own ATS, careers page, or form. Use native applications when the employer wants Cavuno to collect and track applicants."
  - question: Do applicants need an account before applying?
    answer: "No. Candidates can apply as guests. If they sign in later with the same email, Cavuno can attach the application to their candidate account."
  - question: Do employers get an email when someone applies?
    answer: "Yes. When a candidate submits a native application, signed in or as a guest, every approved member of the company that owns the job gets a New application email with a View applicant link. Jobs that use an external application URL send no email. Each employer can turn these emails off with the New applications toggle in their account settings on the board."
  - question: Can employers download resumes?
    answer: "Yes. When a candidate uploads a resume with a native application, employers can download it from the applicant review view."
---

Cavuno includes a built-in applicant tracking system for jobs that collect applications directly on your board. Employers can review applicants per job, download resumes, and move candidates through a hiring pipeline without leaving the board.

Native applications are optional. If an employer already uses a separate ATS, keep using an external application URL for that job.

## Before you begin

The job must use native applications, and the reviewer must have an approved membership for the company that owns the job. External application URLs do not send applicant records back to Cavuno.

## Quick apply

Jobs using Cavuno native applications support Quick apply. Candidates can apply directly on your board without completing a long external form, which keeps the application process fast and branded.

Quick apply does not apply to jobs that use an external application URL. Those jobs still send candidates to the employer’s ATS, careers page, or form.

## Choose native or external applications

Every job needs an application method:

- **Native applications:** candidates apply on your board, and applications appear in the employer’s applicant view
- **External applications:** candidates click through to the employer’s ATS, careers page, or application form

Use native applications when the employer wants Cavuno to collect applicant details and manage review. Use an external URL when the employer already has a required hiring workflow outside Cavuno.

## Open applicants for a job

1. Sign in as an employer
2. Open the employer jobs area
3. Find the job you want to review
4. Open the job’s applicants view

The applicants view shows the candidates who applied to that job. Each applicant keeps their application details tied to the specific listing, so employers can review candidates in the context of the role they applied for.

## New application emails

When a candidate submits a native application, signed in or as a guest, Cavuno emails every approved member of the company that owns the job. The subject is "New application for [job title]". The email names the candidate, includes their email address and cover letter when available, and links to the job's applicants view with **View applicant**.

No email is sent for jobs that use an external application URL, because the application happens outside Cavuno, or when the company has no approved members. Employers receive these emails by default. Each employer can turn them off with the **New applications** toggle under email notifications in their account settings on the board. On SDK boards, the same switch is the `applicationEmails` [notification preference](/docs/sdk/reference/me#notification-preferences).

## Review candidate details

Open an applicant to see their application and candidate information in one place. If the candidate uploaded a resume, use the resume download action in the applicant panel.

If the candidate applied as a guest and later signs in with the same email address, Cavuno can attach the application to their candidate account. Signed-in candidates use their account email during apply, which keeps application ownership clear.

## Move applicants through stages

Use the pipeline stages to track hiring progress for each job. Move applicants as their status changes, such as from a new application to review, interview, offer, or rejection.

Stages are job-specific review states. They are separate from the broader talent directory, which is for candidate discovery and profiles outside a single job application.

## Example review

For example, an employer can open a new applicant, review the attached resume, move the candidate to Interview, and return later to see that status for the same job. Moving the candidate does not change their public talent-directory profile.

## Read per-job stats

1. Sign in as an employer
2. Open the employer jobs area
3. Find a job in the list

Each row shows three stats: **Views**, **Apply clicks**, and **Applications**. Views count page loads on the job detail. Apply clicks count presses on the Apply button; on registration-wall boards, the press that triggers sign-up is not counted until the candidate signs in and continues to apply. Applications counts native applications submitted through your board; the value shows **—** for jobs that use an external application URL. Views and apply clicks rely on browser tracking, so they can be lower than Applications. See [Dashboard analytics](/docs/analytics/dashboard-analytics#per-job-performance).

## Review and delete applications as the operator

Board owners and team members can see every native application on the board from the dashboard, without signing in as an employer.

1. Open **Jobs** in your dashboard sidebar
2. Find the job and select its **Applications** count, or open the job's menu and choose **View applications**
3. Filter by stage if you need to, then select an applicant to open the application

The application shows the applicant's details, cover note, resume, employer notes, and activity. Use **View profile** to open a signed-in applicant's job seeker profile. Guest applicants are marked **Guest** and have no profile.

To handle a deletion request, open the application's menu and choose **Delete application**, then confirm. Cavuno permanently removes the application, its resume, employer notes, and activity history, and the job's application count updates. A signed-in applicant keeps their job seeker profile and account. To remove the whole account, delete the job seeker from **Job seekers** instead. Every deletion is recorded in the [audit log](/docs/team/audit-log).

Owners and admins can delete applications. Editors can view them. Agents and integrations can do the same through the API with `GET /v1/jobs/{id}/applications`, `GET /v1/applications/{id}`, and `DELETE /v1/applications/{id}`.

## Customize ATS copy

Board owners can customize applicant tracking labels and application copy by asking the AI website builder (Website builder in the sidebar). Use this when your board needs different wording for employers, candidates, or a specific niche.

Copy changes affect the board experience, not the underlying application records.

## Verify the workflow

Submit a native test application to a test job, then sign in as an approved employer for that company. Confirm the application appears on the correct job, its resume opens, and a stage change persists after refresh.

## If an application is missing

Confirm the job uses native applications rather than an external URL and that the reviewer is approved for the correct company. If the application count is **—**, the job uses an external destination and Cavuno cannot show applications completed there. See [Employer team access](/docs/managing-companies/employer-team-access) if the reviewer cannot access the company.

## Next steps

Customize the employer-facing labels in the [AI website builder](/docs/ai-website-builder), then document the review stages your employers should use consistently.
