Skip to content
Hiring teams7 min read

Who Should See Candidate Data?

When everyone on a hiring team sees everything, data spreads and scores converge. Scope ATS roles and interviewer access by stage.

By the HireRabbit.AI team · Published · Last updated

Three team members with different keys and shields, each unlocking only some locked candidate files
On this page
  1. Need-to-know access, defined for hiring
  2. What data protection rules say about access
  3. Why access design changes hiring decisions
  4. A role-by-stage visibility matrix
  5. Special cases that need their own rules
  6. What hiding information can and cannot do
  7. A setup checklist
  8. How this maps to HireRabbit.AI

In many applicant tracking system setups, anyone added to a hiring team can end up seeing almost everything: every resume, every score, every interviewer's notes, and sometimes salary expectations and interview recordings too.

That default is convenient, and it causes two problems. Candidate data reaches far more people than the work needs. And interviewers who can read each other's feedback before writing their own start to copy each other, so five opinions become one opinion repeated five times.

This guide sets out a need-to-know approach to ATS user permissions: the principle, what data protection rules say, a role-by-stage matrix, the special cases and a setup checklist.

Need-to-know access, defined for hiring

The NIST glossary, citing SP 800-53 Revision 5, defines least privilege as the principle that "each entity is granted the minimum system resources and authorizations that the entity needs to perform its function".

In hiring, what each person needs changes as the candidate moves. The recruiter needs the whole file at screening. A panel interviewer needs the resume and their own questions for one hour on one day. A coordinator needs a calendar and an email address, and nothing about how the candidate scored.

So the useful unit is not the person but the person at a stage: the role they hold, the stages they are assigned to, the fields their role can see, and how long the access lasts.

What data protection rules say about access

This section is general information, not legal advice. Check the rules that apply to you with employment counsel and your privacy lead.

The GDPR sets the baseline in the EU. Article 5(1)(c) says personal data must be "adequate, relevant and limited to what is necessary". Article 25(2) extends that default to "their accessibility": data must not be made accessible "to an indefinite number of natural persons" without the individual's intervention. An ATS where every new user inherits every candidate file is hard to square with that.

In California, the CCPA has covered job applicants since its employee exemption ended on January 1, 2023, as the state Attorney General announced on July 14, 2023. The California Privacy Protection Agency's cybersecurity audit regulations, as Greenberg Traurig summarizes them, list "least-privilege access controls, privileged-access management, and prompt access revocation" among required audit components. The first audit period starts on January 1, 2027, so confirm with counsel whether you are in scope.

Illinois has the most specific sharing rule. Under the Artificial Intelligence Video Interview Act (820 ILCS 42), an employer that uses AI to analyze applicants' video interviews may share those videos only with people whose expertise or technology is needed to evaluate the applicant. A recording any team member can open by default sits badly with that rule.

Need-to-know access supports all of these principles, but it does not satisfy any of these laws on its own. Each has requirements on notice, retention, security and individual rights that go well beyond who can see what.

Why access design changes hiring decisions

Security is the usual argument for tighter permissions, but for most hiring teams the stronger one is decision quality. What an interviewer sees before the interview shapes what they hear during it.

The clearest evidence comes from medical residency selection. In a two-year study in one residency program, published by Smilen, Funai and Bianco in 2001, interview scores and board exam scores correlated at r = 0.64 when interviewers could see the board scores. When the board scores were withheld, the correlation was r = -0.06, effectively none.

It was one program in one specialty, so treat it as a strong signal rather than a general law. The hiring equivalent today is the screening score: an interviewer who sees "82, strong match" before the first question is at risk of checking that number instead of forming a separate view.

The same effect shows up between people. In estimation experiments with 144 participants, published in PNAS in 2011, Lorenz and colleagues found that social influence narrowed the diversity of answers without improving the group's accuracy. It is the mechanism at work when a panelist reads the hiring manager's "strong yes" before writing their own notes.

Five compasses stand for five interviewers, and each needle points its own way until they all see the same note. Slide the note across the board and the nearby needles swing to point at it, much as interview and board scores correlated at r = 0.64 when the scores were visible and r = -0.06 when they were hidden.

In practice, "each interviewer sees their own round" means:

  • Before the interview: the resume, the competencies they own, their questions and the scorecard anchors.
  • Not before the interview: the screening score, the recruiter's notes, other rounds' feedback, compensation expectations.
  • After submitting their own scorecard: the rest of the panel's feedback, in time for the debrief.

A role-by-stage visibility matrix

The table is a starting point for a company hiring with a recruiter, a hiring manager and a panel. Adjust it to your process, and set it up before the role opens.

RoleResumeContact detailsScore breakdownOthers' feedbackRecordingsEEO dataPay expectations
RecruiterYesYesYesYes (after own scorecard, if they interview)YesNoYes
Hiring managerYesYesAfter own scorecardAfter submittingYesNoYes
Interviewer (round 1)YesNoNoAfter submittingOwn round onlyNoNo
Interviewer (panel)YesNoNoAfter submittingOwn round onlyNoNo
CoordinatorNoYesNoNoNoNoNo
AdminOn request, loggedOn request, loggedOn request, loggedOn request, loggedOn request, loggedNoOn request, logged
Executive sponsorFinalists onlyNoFinalists onlyFinalists, after the panel submitsNoNoFinalists only
The cabinet holds one candidate file, a drawer for each column of the table, and the six badges in front are its roles, with the two interviewer rows as one badge. Point at a badge: drawers that role sees slide fully out, drawers it sees only with a condition open halfway, and the EEO drawer stays shut for every role.

The reasoning behind the main choices:

  • Hiring managers see feedback only after submitting their own. They are usually the most senior voice and the most likely to anchor others.
  • Interviewers see no contact details, score or compensation. None of it helps them assess the competencies they own.
  • Executive sponsors see finalists only, after the panel has submitted, so their view cannot anchor the panel.
  • Nobody on the hiring team sees demographic data. The person who runs the adverse impact analysis joins it to stage outcomes from a separate store.

Special cases that need their own rules

Internal applicants

An internal candidate's current manager may be on the hiring team, or close to someone who is. Haegele's working paper on talent hoarding reports that it "is self-reported by three-fourths of managers" and "deters internal job applications". Keep the current manager out of the requisition, and out of any notification, until the candidate agrees they can be told.

Confidential searches

For a confidential replacement or an unannounced senior search, make the role restricted from the start. Name the people who can see it, keep it off shared pipeline views and reports, and give it a neutral internal title. Check calendar invites and email subjects too, since a coordinator's invite can be where a confidential search leaks.

Agency recruiters

An agency recruiter should see the candidates they submitted and the stage each one is in, not other agencies' candidates or interviewer feedback. Their access should end when the contract does, which is easy to miss when a contract lapses rather than closes.

What hiding information can and cannot do

Restricting what people see has limits. Rinne's 2025 review for IZA World of Labor finds that anonymous applications "can prevent discrimination in the initial screening stage" but "may simply postpone discrimination to later in the hiring process".

The honest conclusion is that scoping access reduces anchoring and data exposure. It does not remove bias at later stages, where people meet the candidate. Pair it with a structured interview scorecard, so every candidate is assessed on the same criteria, and a regular adverse impact analysis, so you can see whether any stage is screening out a group.

A setup checklist

  1. Define roles before you open a role. Build them from permissions, not job titles, and write down what each can see and change.
  2. Scope access by stage. Assign interviewers to the stages they run, not the whole requisition.
  3. Hide feedback until submitted. Everyone, including the hiring manager, sees other feedback only after their own scorecard is in.
  4. Make access time-limited. Stage access ends when the stage closes, and requisition access when the role closes.
  5. Review access quarterly. Remove anyone who no longer needs it (the AI-era hiring playbook sets this inside a 90-day rollout).
  6. Offboard the same day. When someone leaves the company, a panel or an agency contract, their access ends that day.
  7. Keep a log of who viewed what. A record of views and changes, kept alongside your hiring audit trail, lets you answer a candidate, an auditor or your own security team.

Questions to ask an ATS vendor

Put these to every vendor, including the one you use today:

  • Can interviewer access be limited to a single stage of a single role?
  • Can feedback be hidden from each interviewer until they submit their own?
  • Does access expire automatically when a stage or role closes?
  • Is there an exportable log of who viewed each candidate record?

How this maps to HireRabbit.AI

HireRabbit.AI is built around stage-scoped interviewer access. Assign an interviewer to a stage and, unless their role grants wider access, they see only the candidates in that stage. Custom roles are built from a View, Create, Edit and Delete grid, and every move of a single candidate between stages carries a written reason.

The security page describes how access is scoped, and the product page walks through the hiring workflow.

Put this into practice.

Free during invite-only early access. All you need is a work email, and a person reviews every request.