A sourcer saves a promising engineer for a future role. Another recruiter sees the name in a list and assumes someone has already contacted them. A third person adds them to a live hiring process. The database now holds three different ideas of what the same list means. Before adding AI research, give the talent pool a clear purpose and keep membership separate from action.
Ashby Projects provide a place to organize talent you are not actively considering for a particular open role. This guide covers the native project workflow and a recommended design for adding AI assistance around it. The review queues and operational checks below are custom engineering recommendations, not a claim that Ashby provides a native AI project manager.
Start with one pool and a written admission rule
Navigate to Sourcing, then Projects. Create a project with a title and description that explain which people belong there. Complete required project custom fields if your organization has configured them, then create the project. Avoid names that make a future pool sound like an approved interview shortlist.
Write the admission rule in concrete terms. A hypothetical pool might cover engineers with public evidence of maintaining a relevant integration, without claiming that they are available or interested. Assign an operating owner and a review trigger in your team's process. Keep guesses about availability out of factual profile summaries.
Add candidates through the right surface
Ashby supports adding candidates through its Chrome extension, through More and Add to Project on a candidate profile, or in bulk from Candidate Search. For a bulk addition, filter the search, select the intended candidates, choose Add to Project, select the project and start the operation. Inspect the actual selection rather than trusting the search title.
Keep the candidate identity explicit when preparing a batch. A matching name is not enough to establish that two profiles represent the same person. For an AI proposal, include the existing candidate reference, the project and the evidence that satisfies the admission rule. Let uncertain matches wait for a recruiter instead of silently creating another profile.
Separate membership from consequential actions
| Action | Native purpose | Recommended review |
|---|---|---|
| Add to Another Project | Add selected people to another pool | Check the destination and its access |
| Consider for Job | Consider selected candidates for a role | Confirm the role and recruiting intent |
| Email or Enroll in Sequence | Begin the selected communication action | Review audience, message and prior contact |
| Remove from Project | Remove selected project memberships | Confirm that membership removal is intended |
| Archive | Archive selected candidates from a job consideration | Check the affected job consideration |
The bulk action wizard shows the selection criteria and matching record count. Review both before confirming. Ashby varies confirmation prompts by action and batch size, and destructive actions have additional confirmation. Do not turn those prompts into a substitute for deciding whether the selected people should receive the action.
Check confidential project and candidate access
Shared project visibility does not mean every user can view or add every candidate. Ashby's access guidance ties candidate access to jobs the user can access, with separate treatment for leads that have not been considered for a role. Test the workflow using the actual recruiter role that will operate it.
Confidential projects require Elevated Access and access to that project. A Member can work in the project but cannot manage its access permissions. An Admin can amend access permissions. Only the project creator can make a confidential project public again. An Organization Admin can separately receive permission to see and manage all confidential jobs and projects.
Do not generalize confidentiality to the person's entire record. The documented profile privacy case is a candidate linked only to a confidential project with no job considerations. Other project or job relationships matter. A custom AI research interface should not expose profiles or project membership to users who cannot see them in the intended workflow.
Keep project metadata separate from person evidence
Project custom fields describe the project and appear in its Settings. They can also be used as project columns or filters. They are not a replacement for checking the source of a claim about an individual candidate. Confirm current plan availability before designing a workflow that depends on confidential projects or project custom fields.
A research assistant should distinguish a dated observation from an inference. Store the source reference in the private review process and show the reviewer what supported the recommendation. Decide separately whether any summary belongs on the candidate profile. Our guide to Ashby candidate note visibility covers why a project-specific research task should not automatically become a broadly visible profile note.
Use AI to propose, then reconcile membership
Ashby's public candidate.addProject endpoint adds a candidate to a project and requires candidatesWrite permission. That capability alone does not establish a safe autonomous workflow. A custom integration should first produce a reviewable proposal and check that its intended access and destination are appropriate.
- Read the pool definition and the allowed candidate evidence.
- Propose candidate and project pairs with a short reason and unresolved questions.
- Have the designated reviewer approve the exact membership batch.
- Check current membership and candidate identity before applying approved changes.
- Record confirmed results separately from failed or uncertain operations.
- Reconcile uncertain outcomes before trying the same operation again.
These are recommended controls for a custom integration. They do not assert a vendor guarantee about duplicate handling, automatic review or API retries. Keep the first implementation limited to research and membership preparation before adding communication actions.
Do not mistake archive status or activity for enforcement
Archiving a project removes it from the choices for adding candidates in the Chrome extension. Candidates can still be added to an archived project manually inside Ashby. If your operating rule says a closed pool should receive no new members, enforce that rule in your review process and custom integration too.
Last Outbound Activity also has a specific scope. Outreach sent or logged directly in Ashby counts, including one-off emails and sequences. Synced emails sent outside Ashby do not count. A blank or old activity value is therefore not proof that nobody has contacted the person. Review the relevant communication history before starting a new conversation.
How Remqa approaches talent pool workflows
Remqa builds AI agents for recruiting teams around the decisions operators actually make. A useful starting scope is one pool, explicit admission evidence, a reviewer and a visible exception queue. Test membership, confidentiality and communication as separate paths before widening the workflow.
If project maintenance is consuming recruiter attention, use the recruiting hours workflow to identify the repeated work first. Bring one real pool and its current handoffs to a call. We can discuss where research assistance fits and which actions should remain under recruiter control.