What is a Project?

Last updated: September 7, 2026

A project is a shortlist of candidates you build up and share with colleagues for their opinion. It sits outside your job pipelines, so you can gather people for a role before anyone applies — and get a hiring manager's verdict without adding them to a job first.

Who can do this: Super Admin, Admin, Recruiter can create projects. Super Admin, Admin, Recruiter, Hiring Manager, Department head / Site lead and External Collaborator can be added to one. 

Where to find it: Projects in the left navigation

What you use a project for

A project holds candidates and a small team of people who can see them. The typical use is:

  1. Gather candidates you have sourced into one place.

  2. Share the project with a hiring manager or colleague.

  3. Send some or all of those candidates for review.

  4. Act on the verdicts — the ones marked Good Fit can be pushed straight into a job.

Because a project is not a job, nobody in it is an applicant yet. Nothing is visible on a job pipeline until a candidate is added to a job, and adding someone to a project does not add them to a job or a flow.

What each column on the Projects list means

Column

What it shows

Name

The project name, with the description underneath if one was set.

Candidates

How many candidates are currently in the project.

Talent Pool

The talent pool the project was linked to, or - if none.

Owner

The project's current owner. Every project has exactly one owner at a time.

Created

When the project was created.

Shared With

Avatars of everyone the project has been shared with, or - if it has not been shared.

The Reviews tab beside Projects is your own review queue. The number on it is how many candidates are waiting for you to review — see Reviewing candidates in a project.

Who can see a project

Projects are invite-only. Someone sees a project only if one of these is true:

  • They are the project owner.

  • They have been added to it as a viewer or an editor.

  • They are a Super Admin or Admin, who can see and manage every project in the organisation.

Sharing is covered in Sharing a project and sending candidates for review.

Good to know

  • Organisation Members cannot be added to a project at all. The role does not carry project access, so they will not appear in the viewer or editor dropdowns.

  • Every project must keep one owner. Kula blocks the change if you try to remove the last owner. Ownership starts with whoever created the project and can be transferred later.

  • Archiving is permanent and removes everyone's access. The confirmation dialog says the project "will be permanently blocked and everyone will lose access to it", and you must type ARCHIVE to confirm. There is no un-archive action.

  • Only the project owner, Super Admins and Admins can archive a project. Editors explicitly cannot — Kula states this on the Editor field itself.

  • There is no CSV export from a project. Candidates in a project cannot be exported to a file, and projects are not part of the organisation data export. Both are open requests.

Need help? If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.