Start from the Deliver tab
Invitations belong to a delivery, not to the assessment itself — and every assessment already has a delivery, created automatically with it. The Deliver tab opens directly onto that delivery's candidate list and invite form. The delivery's schedule, access rules, and security toggles live in the builder's Delivery & security panel, where you can adjust them at any time.
The assessment must be published before candidates can be invited: while it is a draft, the Deliver tab shows a publish notice in place of the invite form. You can configure the delivery in the meantime, then publish from the builder's checklist and send invitations.
The time window
Each delivery has a time window that defines when candidates can take the assessment. Set or change it in the builder's Delivery & security panel — it is enforced on the server, so a link outside the window will not start an attempt. The window applies to the delivery as a whole, so plan it around your hiring timeline and communicate the deadline clearly in your own messaging to candidates.
The reply-to address
Invitation emails use the reply-to email address configured in your organization settings, alongside your default language and timezone. When a candidate replies to an invitation, the reply goes to that address — so point it at an inbox your team actually monitors. If the setting is missing, the product default is used instead.
What happens when a candidate clicks the invitation
The invitation link takes the candidate toward the assessment, but no one starts cold. Before the attempt begins, every candidate passes a consent gate that states exactly what is monitored during the attempt — based on the security and proctoring toggles you chose for the delivery — and, when the delivery uses the camera, a preflight check verifies their setup.
This means monitoring is always disclosed up front, and setup problems are caught before the clock starts. If you want to see the attempt from the candidate's side before inviting anyone, use "Preview as candidate" from the assessment header.
Beyond email invitations
Email is the default path, not the only one. A delivery's Access & identity settings can open a public self-registration link, issue single-use invitation codes, or match candidates against a guest list by credentials such as an employee or student ID — useful for cohorts that don't start from a per-candidate email. Every access decision is made server-side, and each candidate still passes the same consent gate.
At a glance
- Invitations are sent by email from a delivery — every assessment already has one, so go straight to the Deliver tab.
- The assessment must be published before inviting — while it's a draft, a publish notice replaces the invite form.
- The delivery's time window controls when candidates can take the assessment; it is enforced on the server.
- Invitation emails use the reply-to address set in your organization settings.
- Besides email, a delivery's Access & identity settings can open self-registration, invitation codes, or credential-based access.