ATS permissions: who should see which candidate records?

A small hiring team still needs deliberate access rules. An interviewer may need a resume and an interview brief, while salary discussions and unrelated applications belong with a smaller group.

Begin with what each person must do. Job titles alone are a poor shortcut for deciding what candidate information someone should see.

Map tasks to records

List the people involved in a typical vacancy and the actions they perform. Separate viewing information from editing it, moving an application, sending a message, downloading attachments, and exporting a database.

For a typical vacancy, you could start with this access plan:

Responsibility	Access to test
Recruiter	Applications for assigned hiring work and candidate communication
Hiring manager	Assigned vacancies, relevant applications, and feedback
Interviewer	Assigned interview material and their own feedback task
Administrator	Configuration and access management, with oversight of exports

The exact boundaries depend on your organization and tool. Document exceptions instead of expanding everyone's access to accommodate one unusual case.

Test with separate accounts

Create synthetic candidates and log in as each role. Check search results, direct links, attachments, email history, and exported files. Hiding a menu does not prove the underlying record is protected.

Try a candidate who applies to two vacancies owned by different teams. Ask whether access to one application exposes notes from the other. Also check what happens when someone becomes a temporary interviewer, changes teams, or leaves the company.

Treat exports and invitations as separate decisions

A person may need to review applications without needing a bulk download. Check whether the system allows those permissions to be separated and whether export activity is recorded.

Give someone responsibility for approving invitations and reviewing inactive accounts. Shared logins make it difficult to attribute messages or correct a mistake. Use individual accounts and the sign-in controls available in your organization.

Revisit access as hiring changes

Schedule a review when a vacancy closes or a team changes. Remove access that is no longer needed and check whether downloaded copies require separate handling under your records policy.

During vendor evaluation, request a live demonstration of these cases and a written description of any limitations. If a quoted plan cannot enforce the boundaries you need, include that limitation in the buying decision. A low seat price does not compensate for unsuitable access to candidate information.

Further reading

• Applicant tracking system guide: From A to Z - Workable
• What is an applicant tracking system (ATS)?

Related guides

• Test an ATS with realistic tasks
• Assign clear hiring responsibilities
• How to choose an ATS for your small business