Restricting job visibility by team
Last updated: August 17, 2026
By default, who can see a job depends on the person's role and whether they are on its hiring team. Marking a job confidential removes the org-wide fallback, so only the hiring team and people with confidential access can see the job, its candidates and its interviews.
Who can do this: Anyone who can create or edit the job — Super Admin, Admin, Recruiter, and any custom role with Create jobs or Manage all jobs.
Where to find it: Jobs → your job → More → Mark as confidential
Who can see which jobs by default
Job visibility comes from the permissions on a person's role, set under Settings → Organization → Roles and permissions.
Permission | What it lets someone see |
|---|---|
Manage all jobs | Every job that is not confidential, with full access. |
View all jobs | Every job that is not confidential, read-only. Cannot see offer information. |
Create jobs | Any job they created themselves, including confidential ones. |
Can be added to the hiring team | Any job they are on the hiring team of, including confidential ones. |
Manage all confidential jobs | Every job in the ATS, confidential or not. |
Applied to the roles Kula creates for every organisation:
Role | Which jobs they see |
|---|---|
Super Admin | All jobs, including every confidential job. |
Admin | All non-confidential jobs. Confidential jobs only if they created one or are on its hiring team. |
Recruiter | Jobs they created, and jobs they are on the hiring team of. |
Hiring Manager | Only jobs they are on the hiring team of. |
Organization Member | No jobs. |
External Collaborator | Only jobs they are on the hiring team of. |
Admins do not see confidential jobs by default. Only the Super Admin role carries Manage all confidential jobs. If you need someone else to see every confidential job, add that permission to their role — see [Roles and permissions]