How to Remove a Candidate from a LinkedIn Recruiter Project or Pipeline

To remove a candidate from a LinkedIn Recruiter project, open the project, select the candidate and use the available More, Project or pipeline action to remove them from the project. Depending on your Recruiter version and permissions, LinkedIn may instead let you archive the candidate or move them to a different pipeline stage.

Removing a candidate from your project does not delete the person's LinkedIn profile or remove them from LinkedIn.

How to remove one candidate from a Recruiter project

1. Sign in to LinkedIn Recruiter.
2. Open Projects.
3. Select the relevant project.
4. Open the project's talent pool or pipeline.
5. Find and select the candidate.
6. Open the More or project-action menu.
7. Choose Remove from project, Unsave, Archive or the equivalent action shown.
8. Confirm the change.

LinkedIn Recruiter interfaces can differ between Recruiter, Recruiter Lite and contract configurations. Read the confirmation message before proceeding.

How to remove several candidates

If bulk actions are available:

1. Open the project.
2. Select the checkboxes beside the candidates.
3. Open the bulk-action menu.
4. Choose the remove, archive or project-management option.
5. Confirm the selected candidates and project.

Review the selection carefully. A filter or Select all control can include more candidates than are visible on the first screen.

Remove vs archive vs change pipeline stage

These actions serve different purposes:

Remove from project

The candidate is no longer associated with that project. They may still appear in Recruiter search results or other projects.

Archive

The candidate is retained as a record but moved out of the active workflow. This is useful when you want to preserve notes and history.

Change pipeline stage

The candidate remains in the project but moves to a status such as Contacted, Replied, Interview, Offer or Not a fit. Stage names can be customised by the organisation.

Choose the least destructive action that meets your workflow needs.

Does removing a candidate delete notes and messages?

It may affect how easily project-specific information can be accessed, but it should not be assumed to delete all Recruiter activity. Notes, InMail history, shared records and candidate information may remain under your organisation's LinkedIn Recruiter account and retention settings.

Before removal:

• Review important notes
• Confirm whether the candidate exists in another project
• Check shared team activity
• Preserve legitimate recruitment records according to company policy
• Avoid copying unnecessary personal data outside approved systems

Will the candidate be notified?

Removing or archiving someone inside an internal Recruiter project does not normally send the candidate a notification saying that they were removed from your pipeline.

The person may still receive separate messages or notices generated by actions such as InMail, connection invitations or job applications.

Can you remove a candidate from all projects?

A candidate can be saved in more than one Recruiter project. Removing them from one project may not remove them from others.

To check:

1. Open the candidate's Recruiter profile.
2. Review project associations.
3. Remove or archive the candidate in each relevant project.
4. Confirm whether shared team projects require different permissions.

Do not remove a candidate from unrelated projects owned by another hiring team without authorisation.

What if the remove option is missing?

Common reasons include:

• You do not have permission to edit the project
• The project is archived
• You are using Recruiter Lite rather than full Recruiter
• The candidate is part of a different project
• Your organisation uses a connected applicant tracking system
• LinkedIn renamed the action
• The record must be moved to an archive or disposition stage instead

Ask the project owner or Recruiter administrator to confirm your access.

How ATS integrations can affect candidate removal

LinkedIn Recruiter may be connected to an applicant tracking system. In that case, changing a candidate in Recruiter may not delete or update the matching ATS record automatically.

Check:

• Which system is the source of truth
• Whether stages are synchronised
• Whether removal in Recruiter affects the ATS
• Whether the candidate submitted an application
• Company retention and deletion rules

A sourced candidate and an applicant may have different legal and operational records.

How to delete a LinkedIn Recruiter project instead

Removing a candidate is different from deleting or archiving the whole project. If the entire hiring project is no longer needed, review how to delete a project in LinkedIn Recruiter.

Before deleting a project, confirm that:

• No active vacancy depends on it
• Candidate records have been handled correctly
• Team members no longer need the project
• ATS links will not be disrupted
• Retention requirements are satisfied

How saved searches differ from saved candidates

A saved search stores search criteria and may generate alerts. A saved candidate is a person added to a project or workflow. Removing a candidate does not delete the search that originally found them.

To clean up search criteria, use how to delete saved searches in LinkedIn Recruiter.

For a broader explanation, see LinkedIn Recruiter search history vs saved searches.

Candidate data and privacy responsibilities

Recruiters should process candidate data only for legitimate recruitment purposes and under applicable company policies and privacy law.

Good practice includes:

• Limiting access to authorised hiring staff
• Recording accurate disposition reasons
• Avoiding sensitive notes that are not job-related
• Following retention schedules
• Responding properly to access or deletion requests
• Securing exported candidate data
• Removing stale records when permitted and required

Removing someone from a project is a workflow action, not necessarily a complete personal-data deletion.

Troubleshooting a candidate who reappears

A candidate may appear again because:

• They remain in another project
• A saved search finds them again
• An ATS integration restores the association
• Another team member adds them back
• The candidate applied to the role
• The project view is cached

Refresh the project, check integrations and review team activity before repeating the removal.

Frequently asked questions

Can I undo removing a candidate?

Search for the candidate again and add them back to the project if your permissions and retention rules allow it.

Does removing a candidate delete InMail?

Not necessarily. Messaging history and project membership are separate.

Can I delete a candidate's LinkedIn profile?

No. Recruiter users cannot delete another member's LinkedIn account or profile.

Should I remove or mark a candidate as Not a fit?

Use a disposition stage when your organisation needs an auditable recruitment record. Remove the candidate when they were added in error or no longer belong in that project, subject to policy.

Is a candidate notified when their pipeline stage changes?

Internal stage changes do not normally notify the candidate unless a connected workflow triggers a separate communication.

Final answer

Open the LinkedIn Recruiter project, select the candidate and use the project or pipeline menu to remove, archive or move them. This changes your internal workflow only; it does not delete the candidate's LinkedIn profile or every recruitment record.