For employers
How and when you see a candidate’s identity
A reveal is the moment CalHire tells you who an anonymous candidate is. It is the most consequential thing the platform does, so it carries the tightest rules.
When you can request one
Only at stages the platform allows, and all of them require the candidate to be shortlisted first — typically shortlist, interview scheduled, or interview completed. Your administrator configures which of those your organisation uses.
There is no earlier route. You cannot reveal a candidate you have merely browsed, and there is no support request that produces one.
Who can request one
Only team members holding the reveal permission, granted by your tenant administrator. It is enforced server-side: hiding the button is not the control, the policy is.
The candidate has to agree
Consent is per employer and per reveal. A candidate who agreed for another company has not agreed for you, and there is no shared pool of already-revealed candidates.
If they decline, the process continues with them anonymous. Declining a reveal is not a withdrawal from the role.
What gets recorded
Every reveal writes an immutable entry: which employer, which role, when, and the consent it rested on. The log is append-only.
That protects the candidate, and it protects you — an evidenced, consented disclosure is a defensible one.
What you may not do with it
A revealed identity is disclosed to your organisation, for this role. Passing it to another employer, another tenant or a third party falls outside what the candidate consented to and outside the terms.
Identity and ATS synchronisation only fire after a reveal, by design: before that point there is nothing to sync that would not defeat the purpose of the anonymity.
Right to work and nationality
Those questions are captured at reveal, not before. The ordering is deliberate — information that cannot lawfully influence a skills evaluation should not be sitting in front of you during one.