Learn how invite links, interview windows, access checks, and candidate support should work.
What recruiters should verify
Candidate access should feel simple. This page explains what recruiters should verify before sending access, what candidates should do first, and how to recover from common failures without creating duplicate workflow records.
- Send one clear portal route so the candidate is not guessing which page or token to use.
- Confirm the candidate is attached to the correct role and current stage before resending access.
- Use one named support path for candidate-facing access problems.
- Communicate stage expectations, review timing, and next-step ownership clearly.
What candidates should do first
Candidate access should feel simple. This page explains what recruiters should verify before sending access, what candidates should do first, and how to recover from common failures without creating duplicate workflow records.
- Open the portal from the original invite link first.
- Allow browser access to camera and microphone before starting a media-enabled interview.
- Use the same session path for re-entry when possible instead of requesting a new invite immediately.
- Keep a screenshot or exact error text if support escalation becomes necessary.
Recovery pattern
Candidate access should feel simple. This page explains what recruiters should verify before sending access, what candidates should do first, and how to recover from common failures without creating duplicate workflow records.
- If launch fails, validate the original invite route, token scope, and interview window before issuing a replacement.
- If a candidate is confused, send one reset message with stage name, next action, and support contact.
- If timing slips, tell the candidate what changed and when they should expect the next update.