Profile visibility for roles with recruiting permissions
Overview
This article explains the expected system behavior regarding visibility of candidate and employee profiles, especially when accessed via direct links. It also outlines the role-based permissions that control access and how access can be restricted through configuration.
Expected behavior
When a user (For example, Employee or Hiring Manager) attempts to access a profile, access is determined by:
-
Employee Profiles (Internal Candidates)
- Access is always allowed to other employees.
-
Candidate Profiles (External Candidates)
- Access is granted only if:
- An interview has been scheduled, or
- A feedback request has been sent to the user
In all other cases, access is denied unless the user has specific Recruiting Permissions.
- Access is granted only if:
This behavior applies even when profiles are accessed via direct URLs.
Behavior for other roles
Users with roles other than the employee role may still be able to access candidate profiles directly if they hold certain permissions.
Common permissions included in the Hiring Manager role (Example)
perm_view_my_pipelinesperm_manage_my_pipelines
These permissions fall under the broader category of recruiting permissions, which allow profile access regardless of interview/feedback status.
List of recruiting permissions
Access to candidate profiles is permitted if the user’s role includes any of the following permissions:
If a user has any of these permissions, they will be able to access candidate profiles directly.