Skip to main content
All CollectionsUser access
What candidate data can be accessed by whom?
What candidate data can be accessed by whom?

What data in the candidate card belongs to the candidate and what belongs to a job

Ester avatar
Written by Ester
Updated over 2 months ago

To be able to view candidates' data, a user must be granted access to do so. A user can access a candidate via a Team or a job's Hiring team. The purpose of this article is to explain which data in the candidate card you will see depending on which access you have.

The data in a candidate card is split up into two parts: data that belongs to the candidate or a specific job.

Candidate data - Data that belongs to the candidate

This data is accessible by any user invited to a Team or Hiring team the candidate belongs to.

So this data can be seen by all users with access to the candidate:

  • Comments (Written outside job context)

  • Connect questions

  • Custom fields*

  • Reviews

  • Resume (CV)

  • Documents uploaded from Connect

  • Share links

  • Locations

  • Messages (Sent outside job context)

  • Todos (Created outside the job context)

  • Limited information on the job applications the candidate belongs to, which includes:

    • Job’s title

    • Job’s recruiter

    • Job status (published/unpublished)

    • The application’s status (active/rejected)

    • Which stage type the candidate belong to in the process

* Note that only Recruitment leads, Recruitment admins, and company admins will see Private custom fields.

Job data - Data that belongs to a job

The job's data is accessible by any user invited to a specific recruitment process/job. You know you have access to this data if you see the job listed under the tab Jobs.

This means this data can be seen by any user with access to the specific job:

  • Comments (Written within job context)

  • Recruiter uploaded documents

  • Candidate uploaded documents from applications (other documents than CV)

  • Questions/Answers for the job

  • Messages

  • Todos

  • References

  • Referrals

  • Calendar invites

  • NPS responses

  • Partner assessments/events

  • Interviews

Note! Some data exists both as job data and candidate data. What decides access is whether it's created in a job context or not.

What is job context?

If an action is performed in a job context, it is done in relation to a specific job. Practically, this means the action is performed on the candidate with the job in question picked in the job application switcher:

Did this answer your question?