> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.confirm.global/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.confirm.global/_mcp/server.

# Blocklist

The **Candidate Blocklist** (**Settings → Blocklist**, Admins only) is a list of emails, phone numbers, names, and email domains that are checked every time a candidate applies. When an application matches an active entry, the application is rejected automatically and an alert is raised.

There are two ways to add someone: from this page, or while rejecting a candidate.

## Adding an entry from Settings

#### Open the add dialog

Go to **Settings → Blocklist** and click **Add Entry**.

#### Choose a block type

Pick how the entry should match incoming applications:

| Block type             | Matches                                                                                         |
| ---------------------- | ----------------------------------------------------------------------------------------------- |
| **Email Address**      | One exact email address                                                                         |
| **Phone Number**       | One phone number                                                                                |
| **Name (Exact Match)** | The candidate's name exactly (not case-sensitive)                                               |
| **Name (Fuzzy Match)** | Close variations of a name                                                                      |
| **Email Domain**       | Every email address at a domain. Enter the domain only, such as `example.com`, without the `@`. |

#### Enter the value and context

Enter the **Value to Block**. Optionally add a **Reason** so your team knows why the entry exists, and an **Expiration Date**. Leave the date empty to block permanently, or set one for a temporary block.

#### Save

Click **Add to Blocklist**. The entry applies to the next application. If the value is already on the list, the dialog tells you.

## Blocking while you reject a candidate

The reject dialog on a candidate (and the bulk reject dialog on the candidate list) includes an **Also add to blocklist** switch. It's off by default. Turning it on blocks future applications matching the candidate's email or phone and stops all further messages to them.

Anyone who can reject candidates can use this switch; you don't need to be an Admin. If the rejection succeeds but the blocklist add fails, the dialog stays open and says so, and you can add the entry manually from **Settings → Blocklist**.

## Managing entries

The **Blocked Entries** card lists each entry's value, type, reason, expiration, and when it was added. Search by value with **Search by value...**, filter by block type, and page through long lists. **Refresh** reloads the list.

* **Expired entries** are no longer enforced but stay visible for your records.
* **Removing an entry** (the row action, after confirming) allows future applications from that value again. It doesn't undo past rejections.

## How automatic rejection works

When a candidate applies through any source, their email, phone, and name are checked against the active entries. On a match, the application is rejected automatically and an alert is raised so your team can see what was blocked.

> **Note**
>
> Adding a Settings entry acts on new applications only. Candidates already in your pipeline aren't affected; reject them from the candidate list or profile (and use **Also add to blocklist** there if you want them blocked too).