- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Scoring
- Question Types
- Question Authoring
- Browsing Questions
- Content Blocks
- Media Library
- Metadata Rules & Schema
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
- Data Operations
- Analytics Overview
- Test Analytics
- Question Analytics
- Per-Question Analytics
- Results Explorer
- Segment Analysis
Delete Candidates
Permanently deleting a candidate erases the person from the task — their record, invitations, chat history and reference photo — together with every test session they took. Candidates with a session in progress are never deleted; end the session first.
When a person must disappear from a task entirely — a privacy or erasure request, test candidates created by mistake, an imported list that has to be redone — deleting their sessions is not enough: their name, contact details, invitations and conversations would remain. Deleting the candidate removes all of it in one operation.
What is deleted
- The candidate record — name, email, form answers, metadata, access codes and credentials.
- Invitations and emails — the invitation and notification emails sent to the candidate.
- Assessment page and chat history — the candidate's assessment page record and any live chat conversations.
- The reference photo, if one was uploaded.
- Their place in the candidate list — unique values such as an email or ID are freed, so the same person can be added again later as a new candidate.
- Every test session the candidate had — each one deleted exactly as described in Delete Test Sessions.
The candidate's invitation links stop working immediately. Credits used by their sessions are not returned.
Remove vs Delete permanently
The Candidates table offers two different actions:
| Remove candidates | Delete permanently | |
|---|---|---|
| Who it applies to | Only candidates who have not logged in yet | Any candidate without a session in progress |
| What happens | The candidate leaves the list but is kept on record (soft-deleted) | The candidate and all their data are erased |
| Test sessions | None to affect | Deleted with the candidate |
| Reversible | No | No |
Removed candidates still count as Soft-deleted in the Data Operations tab until they are deleted permanently.
Deleting selected candidates
In the Candidates table, select up to 100 candidates and choose Delete permanently. If any selected candidate has a test session in progress, that candidate is rejected and stays in the list — the rest are deleted.
Deleting all candidates of a task
The task's Data Operations tab shows the task's candidates as Total, Active and Soft-deleted, and offers two buttons:
- Delete all candidates — deletes every candidate of the task, active and soft-deleted, with all of their test sessions.
- Delete soft-deleted candidates — deletes only the candidates who were already removed from the list but are still kept on record. Active candidates are not affected.
Candidates with a test session in progress are skipped and counted as skipped (test session in progress) on the run in the Operations list. Once their session ends, run the operation again to delete them.
The deletion log
Each deleted candidate gets its own plain-text log in the Operations list, listing the records and files removed for the candidate — useful as proof when answering an erasure request. Each of their test sessions is logged separately, as described in Delete Test Sessions. See also Tracking & Recovering Operations.
The in-progress rule protects candidates, not data: nobody loses an attempt they are still working on. If a candidate keeps being skipped, check the Test Sessions table for a session still marked as started and end it — then delete the candidate again.