Skip to content
Test Candidates

What your team can see

The visibility model in one sentence, what that means in practice, and how to handle a role that needs privacy.

Last updated 21 September 2026

Everyone on the team sees every assessment, candidate and result.

That is the whole model. It is stated on the team page, and it is worth understanding before you invite anyone, because there is no setting to soften it.

The team page, with the note that everyone on the team sees every assessment, candidate and result and that there are no seat limits.

What that includes

  • Every assessment, active and archived.
  • Every candidate, their name, email address and progress.
  • Every unlocked result and every full report.
  • Every decision recorded and every team note written.
  • Billing and usage, and the integrations page, including the API key.

What team visibility does not include

Your colleagues' notification preferences and their sign-in methods are personal to them. Nothing else is private.

Why visibility is built that way

Hiring is a team activity and the alternative is worse: per-assessment permissions that people forget to set, and a hiring manager who cannot see the shortlist because nobody ticked a box. The trade-off is that access is all-or-nothing, so membership is the control.

Handling a role that needs privacy

Two workable approaches.

Do not add the people who should not see it. Share what they need instead: a downloaded report for one candidate, or an exported comparison for a shortlist. Neither needs an account.

Use blind review for fairness rather than secrecy. The Hide name control on a report replaces the candidate's name throughout, so a panel can read the evidence before the person. It hides the name from the reader, not from the account.

Confidential candidates

If someone applies who must not be visible to colleagues on the account, Test Candidates is the wrong place to assess them. Run that one outside the tool.

When someone leaves

Remove them the same day. There is no partial revocation and no read-only mode, so an account they still have access to is an account with your full candidate list in it. See add and remove team members.

The API key is account-wide too

Anyone on the team can reveal and regenerate it, and it grants full access to the account. Treat team membership and API access as the same decision. See keep your API key safe.