> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/review-candidates/talent-pool.md).

# Talent Pool

Save promising candidates in your Talent Pool, review spontaneous applications, filter saved candidates and assign them to a job when a suitable role opens.

Your Talent Pool is a store of candidates for future hiring needs, including both active job seekers and passive candidates. It keeps track of candidates who show potential but may not be the right fit for your current vacancies. Instead of losing contact, you can save their profiles and revisit them later when a suitable role opens.

***

## Add candidates to your Talent Pool

There are two ways to add candidates to your Talent Pool in JOIN.

### From a candidate profile

1. Navigate to the `Candidates` tab
2. Click on a candidate to open their profile
3. In the left panel of the candidate’s profile, click `Add to Talent Pool`

This adds the candidate’s profile to the `Talent Pool` tab for future reference.

### From spontaneous applications

If you've activated the option to receive [spontaneous applications](https://help.join.com/review-candidates/spontaneous-applications.md) on your Career Page, JOIN automatically sends these applications to your `Talent Pool`. These are candidates who haven’t applied to a specific job but are interested in your company.

***

## Review spontaneous applications

Unreviewed spontaneous applications appear as a floating banner at the bottom of the `Talent Pool` tab. Click `Review` to open the screening view.

In the screening view, you see:

* Candidate’s `CV` and `Cover letter` (if provided)
* Contact information
* `Candidate location`
* Source: marked as `Spontaneous Application`
* Their motivation to join your company

From here, you can:

* Click `Accept` to permanently add them to your Talent Pool
* Click `Reject` to decline the application. This doesn't delete the candidate's data: only deleting the candidate removes their data from your account

Use the navigation arrows to move through the list without leaving the screening view.

***

## The Talent Pool tab

Click `Talent Pool` in the left sidebar menu to access all stored candidates.

### Applications table

Each row represents a candidate card with the following columns:

* `Name`: Click a candidate’s name to view their full profile.
* `Email`
* `Candidate location`
* `GDPR Status`: Shows consent status
* `CV`: Shows the attached CV of a particular candidate
* `Tags`: Add tags to a candidate's profile in your Talent Pool to make them easier to find.
* `Action`: Gives two options to take action on a candidate:
  * Assign candidate to a job using <i class="fa-square-plus">:square-plus:</i> icon
  * Remove candidate from Talent Pool using <i class="fa-trash-can">:trash-can:</i> icon.

{% hint style="info" %}
Only the Talent Pool profile is deleted. Any previous job applications by the candidate remain intact.
{% endhint %}

### View settings

Click the settings gear icon at the top right of the table to show or hide the following columns:

* `Email`, `Candidate location`, `GDPR Status`, `CV`, `Tags`

### Filters

Click the `Filters` button to narrow your search using:

* `Application Tags`
* `Candidate Country`

Use filters and view settings to find candidates for a specific role or location.

***

## Assign a candidate to a job

Use the `+` icon in the `Action` column to assign a Talent Pool candidate to a job. A pop-up window appears with your active job listings. Select the job and click `Assign`.

{% hint style="warning" %}
No automatic message is sent to the candidate. We recommend contacting them beforehand to confirm their interest.
{% endhint %}

### Example

You’ve saved several engineers in your Talent Pool. Once you publish a new `Backend Engineer` job, you can revisit your pool and assign suitable candidates to this job to start its pipeline.

***

## When to use your Talent Pool

**When a new role opens**\
Start with candidates you've already saved instead of sourcing new applicants from scratch.

> *Example: You've saved a software developer who wasn't the right fit before. When a similar role opens, you can contact them directly.*

**To revisit candidates you’ve already vetted**\
Keep the details of candidates who weren't a fit at the time, and find them again later.

> *Example: A marketing manager impressed you during a previous recruitment round. Months later, you open a new role in the same department, and a search in your Talent Pool brings them back to your attention.*

**To keep candidates your team has already evaluated**\
Candidates in your Talent Pool are often people your team has already assessed positively, and who have shown interest in your company or roles before.

**To keep candidates from other sources**\
Your Talent Pool isn’t limited to former applicants. It can also include interns, referrals, and candidates you met at events or sourced via LinkedIn outreach.

***

## FAQs

<details>

<summary>What’s the difference between a Talent Pool and job applications?</summary>

Talent Pool profiles are saved candidates not tied to a specific job. Job applications are submissions for a particular role. A candidate can exist in both.

</details>

<details>

<summary>Will candidates be notified when I add them to the Talent Pool?</summary>

No, candidates are not notified when they are added to the Talent Pool. We recommend reaching out directly if you plan to contact them in the future.

</details>

<details>

<summary>Can I assign a talent pool candidate to multiple jobs?</summary>

Yes, you can assign a Talent Pool candidate to multiple jobs if they’re suitable. Each assignment creates a separate application for that job. You can view all the assigned jobs in the right panel of the candidate's profile.

</details>

<details>

<summary>What happens if I reject a spontaneous application?</summary>

The application is declined, but the candidate’s profile and data aren't deleted. Only deleting the candidate removes their data from your account.

</details>

<details>

<summary>Can I edit candidate information in the Talent Pool?</summary>

Candidate profiles reflect the information that a candidate provided. You cannot manually edit their personal details, but you can add tags and notes for internal use.

</details>

<details>

<summary>Do I need to delete a candidate separately from the Talent Pool after deleting them from Candidates?</summary>

No. When a candidate is deleted from `Candidates`, they are automatically removed from the `Talent Pool` as well.\
So if a candidate was previously added from `Candidates` to `Talent Pool` via the Candidate profile, it means the candidate has been duplicated to `Talent Pool`. When the candidate is deleted from `Candidates` , the profile would also automatically be deleted in `Talent Pool`.

</details>

<details>

<summary>Can I manually import a candidate from an external source to the Talent Pool?</summary>

No, you cannot manually import a candidate externally to `Talent Pool`. To do this, you need to import the candidate to `Candidates` and assign them to a job first. Then you can add the candidate to `Talent Pool` through the candidate profile.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.join.com/review-candidates/talent-pool.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
