Skip to main content

Opt-In Consent Link

Collect candidate consent for interview recordings using BrightHire's opt-in consent link.

Written by Jennifer Steinker

Overview

BrightHire can provide a candidate opt-in consent link that allows candidates to give explicit consent before any interview recording takes place. You can use the same consent link in two different ways, depending on whether the candidate exists in your ATS and how your jobs are configured.


Locate you Opt-In link

Navigate to this BrightHire Settings Page (Compliance > Settings)

Copy your link


Two ways to use the candidate opt-in consent link

BrightHire supports two ways to use the candidate opt-in consent link. The right option depends on whether the candidate exists in your ATS and how recording consent is configured for the job.

Option 1: Link-Driven Consent

Use this option when you want the consent link itself to place a candidate into the opt-in workflow. This is the only option available for candidates who are not managed through your ATS.

How it works

  1. Add the candidate opt-in consent link to a calendar event that BrightHire can access through calendar sync or email import (using [email protected]).

  2. When BrightHire detects the /candidate-opt-in/ URL on the event, the candidate's recording status is set to Awaiting Candidate Consent.

  3. BrightHire will not record the interview until the candidate provides consent through the link.

Where to view consent status

You can view the candidate's consent status in:

  • The scheduled interview card (BrightHire Home > Upcoming Interviews)

  • The candidate page

When to use this option

Use Link-Driven Consent for:

  • Candidates who are not in your ATS

  • Interviews scheduled directly through [email protected]

  • Workflows where the consent link should determine whether recording can occur

Important: For non-ATS candidates, adding the consent link to the calendar event is the only way to place them into the opt-in workflow.

Option 2: ATS-Managed Consent

Use this option when recording consent is already controlled by your ATS and you want candidates to be able to provide or update their consent preference.

How it works

  1. Recording consent is enabled at the job level in your ATS (for example, through the opt-in setting on a Greenhouse job).

  2. Because the job is configured for opt-in recording, candidates are automatically placed into the opt-in workflow.

  3. The consent link can be shared with candidates so they can provide or update their consent decision.

Requirements

Where to share the link

You can include the consent link in:

  • Calendar invitations

  • Scheduling emails

  • Confirmation emails

  • Other candidate communications

Because the job already places candidates into the opt-in workflow, interviews will not be recorded unless the candidate provides consent, regardless of where the link is shared.


How candidates use the link

  1. The candidate opens the consent link and enters their email address.

  2. They receive a verification email containing a verification code.

  3. After verifying their identity, they are shown a consent page displaying any upcoming interviews associated with their email address.

  4. They can choose to consent to recording or decline consent.

Candidates can return to the link at any time to update their preference. BrightHire always uses the candidate's most recent consent decision.


Frequently Asked Questions

Q. Where is candidate consent stored?

  • If consent is collected via the BrightHire consent link (or BrightHire-managed opt-in), the consent decision is stored in BrightHire.

  • If your ATS collects consent as part of the application flow, the consent decision is stored in your ATS.

Q. Where can my team see a candidate's consent status?

You can view a candidate's consent status on:

If BrightHire is waiting on a response because the consent link was detected on an imported invite, you'll see Awaiting Candidate Consent.

Q. Is there an opt-in / opt-out tag?

No. Consent appears as a status on the interview and candidate page, not as a tag.

Q. Does this work with any ATS?

Yes. You can simply add the opt out link in email or calendar templates for any ATS.

Q. Do we need calendar sync for this to work?

No. It works as long as BrightHire imports the interview, either through:

For calendar sync, the event must also be eligible for import (for example, it contains "#brighthire", a keyword, or matches your "always record" settings).

Q. Can we use the link alongside ATS-based consent?

Yes. BrightHire uses the most recent consent decision.

Q. If we only email the link (no calendar invite), does it still work?

Yes. The candidate can still set or update their preference.

However, BrightHire will only show Awaiting Candidate Consent when the link is detected on an imported invite.

Q. If a candidate isn't in our ATS and we add the link to an imported invite, what happens?

BrightHire will not record unless the candidate explicitly opts in.

Q. Does consent apply to one interview or all interviews?

It applies to all upcoming scheduled interviews associated with that candidate email address.

Q. What if there are multiple calendar events for the same interview?

The link only needs to appear on one event. BrightHire will carry it across associated events.

Q. Can we pre-fill the candidate's email on the consent page?

Yes. Add [email protected] to the consent link.

Candidates can still edit the email address before submitting their decision.

Q. Is this enabled by default?

No. It requires the CandidateRecordingDecision:opt-in-link feature flag to be enabled for your organization.

Q. Do candidates in the opt-in link flow receive standard opt-out notification emails?

No. Those emails are suppressed for opt-in-link interviews to avoid confusing messaging.

Q. Are interviewers notified if a candidate opts out?

Yes - if a candidate opts out via the consent link, the scheduled interviewers are emailed that the interview will not be recorded. Learn more here


❓ Reach out to [email protected] with additional questions.

Did this answer your question?