Candidates

Everything about the people in your task: how candidates are added (manually, by import, or via self-registration), how they are organized into groups and folders, and how invitations go out.

Updated 2026/07/17

The Candidates page lists every person registered to the task — whoever you added, imported, or accepted through self-registration. Each row is a candidate with their profile data, group and folder placement, invitation state, and progress through the task's steps. From here you add people, organize them, send invitations, and optionally upload a reference photo per candidate for stronger identity verification; their test results live under Test Sessions.

The panels below cover the four core workflows — adding candidates, organizing them with groups and folders, sending invitations, and uploading a reference photo.

Groups, folders, and labels assigned here do double duty later: they scope the Exam Monitor's audience, filter session lists and post-proctoring batches, and segment analytics. Organizing candidates before the exam pays off in every tool you use after it.
Why organization matters

Candidates enter the task through three routes, used alone or combined:

Add manually — create candidates one at a time with their name, email, and profile fields. Right for small rosters and late additions.
Bulk import — upload the whole roster at once, mapping columns to identity fields, classification parameters, and custom properties. The import previews before committing, so mapping mistakes are caught before they become candidates.
Self-registration — with an open access method, candidates create themselves by filling the access form; they appear in the list as they register.

However they enter, all candidates land in the same list with the same profile model — assign groups, folders, and classification values at add/import time so downstream tools (audiences, filters, analytics) are ready from day one. Adding a candidate does not notify them; invitations are a separate, deliberate action.

Groups, folders, and labels organize the candidate list — and the organization pays off everywhere downstream:

Groups — the primary segmentation (exam hall, cohort, shift). Groups scope the Exam Monitor's audience, filter session lists, and define analytics comparison groups.
Folders — hierarchical containers for administrative structure when one flat list gets unwieldy.
Labels — free-form markers a candidate can carry several of (“needs-follow-up”, “retake-approved”) for cross-cutting states.

Assign membership at import time or from the candidate list afterwards. One practical rule: if you'll ever want to monitor or compare a subset separately, make it a group before the exam — the live monitor and analytics segment by what existed when sessions ran.

Invitations deliver each candidate their personal way into the assessment — an email carrying the task link and their unique access credentials.

Send in bulk — select candidates (or the whole roster) and invite them in one action; each receives their own individualized message.
Send individually — invite or re-invite a single candidate, e.g. a late addition or someone whose email bounced.
Templates apply — the invitation renders from the task's email templates (Task Settings → Communication), personalized with the candidate's data.
Track and resend — every sent invitation is logged in Sent Mails per candidate; resend any message from the log when an inbox loses it.

Invite with margin before the exam window: candidates need time to find the email, check their device, and ask questions — and you need time to spot the bounces.

Upload a trusted reference photo per candidate to strengthen identity verification — AI Detections then compares the candidate's exam ID photo against it automatically, with no extra step configuration.