InsightHireHelp Center

Talent network

Consent-gated talent network at /dashboard/network, candidate pools, and release workflows — feature flag talent_network.

Feature flag: talent_network
Requires platform enablement and per-organization grant. The network browse page and reject-to-network flows are hidden without it.

The talent network is InsightHire's consent-gated pool of candidates who were released after a reject but remain open to future opportunities. It prioritizes talk-track and score evidence over resume dumps.

Key routes

SurfacePathFlag
Talent network browse/dashboard/networktalent_network
Candidate pools/dashboard/candidates/poolsNone (general CRM)
Pool detail/dashboard/candidates/pools/[id]None
Bulk pool manage/dashboard/candidates/pools/[id]/bulk-manageNone
Import to pool/dashboard/candidates/importNone
Review queue (release on reject)/dashboard/reviewRelease option needs talent_network

Talent network browse

Dashboard → Network (/dashboard/network) lists candidates available for rediscovery.

Eligibility criteria

A candidate appears in the network when all of the following are true:

  1. talent_network grant is active for your org
  2. Candidate opted in — open to opportunities consent flag
  3. Recruiter released to network on reject (or equivalent workflow)
  4. Platform consent rules satisfied (openToOpportunities + releasedToNetwork)

What recruiters see

Each network row shows:

FieldDescription
Display nameCandidate identifier
Current / prior roleLast known title
Prior orgPrevious employer context
SkillsTop skills from journey/resume evidence
ScorePrior composite/journey score when available

Matching is score-first and talk-first — the UI emphasizes evidence from async video and assessments, not bulk resume keyword search.

Empty state

When no candidates qualify, the page links to /dashboard/review with guidance:

Release a rejected application and ensure the candidate is open to opportunities.

Without the flag, the page shows a limited-rollout message with link back to /dashboard.

Release workflow

When rejecting from the position pipeline (/dashboard/positions/[id]):

  1. Open reject confirmation
  2. Check Release to talent network (visible with talent_network grant)
  3. Optionally check Mark open to opportunities for consent
  4. Confirm reject

Released candidates do not re-enter active pipelines automatically — recruiters browse /dashboard/network and invite manually to new positions.

Candidate pools (complementary CRM)

Candidate pools (/dashboard/candidates/pools) organize prospects for campaigns — separate from the consent-gated network but often used together for sourcing nurture.

Pool management

ActionPath
List pools/dashboard/candidates/pools
Create poolDialog on pools page
Pool detail/dashboard/candidates/pools/[id]
Manage members/dashboard/candidates/pools/[id]/manage
Bulk operations/dashboard/candidates/pools/[id]/bulk-manage
Import candidates/dashboard/candidates/import

Pools support:

  • Name, description, tags
  • Search/filter within list
  • Bulk add/remove members
  • Link from journey auto-enroll settings

Pools vs network

AspectCandidate poolsTalent network
AccessAll orgsFlag: talent_network
ConsentRecruiter-managed listsCandidate opt-in required
Typical sourceSourcing, imports, eventsRejected-but-strong candidates
Primary useCampaigns, journey auto-enrollRediscovery, silver medalists

Nurture workflows

InsightHire does not ship a dedicated "nurture email sequencer" page today. Practical nurture patterns using existing routes:

1. Pool-based campaigns

  1. Create pool — e.g. "Q3 Engineering silver medalists"
  2. Import or bulk-add candidates from prior reqs
  3. Invite to a lightweight journey or new position when ready

2. Network rediscovery

  1. Browse /dashboard/network weekly
  2. Filter mentally by score and skills (UI list is score-sorted)
  3. Invite strong matches to open positions via /dashboard/candidates/invite

3. Journey auto-enroll

On /dashboard/journeys/[id]/edit, enable auto-enroll from pools — candidates in selected pools enter the journey when triggered.

4. Reject with network release

Convert "not now" rejects into network candidates instead of losing relationship entirely.

Privacy and compliance

  • Network visibility requires explicit candidate consent
  • Released candidates were previously applicants — honor prior communication preferences
  • Do not export network lists outside InsightHire without legal review
  • Display names and evidence levels respect org data policies

Best practices

  • Release generously for near-misses — network ROI comes from silver medalists
  • Maintain clean pools — archive stale campaign pools separately from network
  • Re-score on re-invite — prior journey scores inform but do not replace fresh evidence for new roles
  • Coordinate with recruiters — network is org-wide; avoid duplicate outreach