/dash/targets). A one-off Search goes stale. A Target keeps finding people.
Two kinds, matching the toggles in the app:
Confirm who to keep
Nothing is monitored until you confirm. The review screen is Not live yet.
Buttons in the app: Accept / Decline, or Add them / Leave out. Then Start monitoring this search (or company), or Keep all N and start monitoring.
Live filters on a Target:
Counts read N monitored · M waiting.
If find-people fails, Retry re-queues the job (
POST /targets/:id/retry). Delete this target removes people who are only on that Target; people also on another Target or List stay.
Toggles that skip the queue:
- People search: Add new matches automatically
- Company: Add new hires and alumni automatically
auto_admit. Use it when the query is tight. Do not turn it on for a broad company network.
Empty Targets: No targets yet. New people search / New company start a Target. Start people search / Start company search opens a confirm dialog: This may take up to 24h, plus how many people to find (capped at remaining monitoring capacity). The Target then shows Loading, a countdown, and a note that you can close the page. Status badges: Live, Needs attention, Loading, Couldn’t finish.
Recruiter flow
- Search (or Companies → open a company).
- Targets → People search → Start people search, or Company → Start company search.
- Confirm the search. This may take up to 24h. Set how many people to find (at most your remaining capacity), then start it.
- The Target shows Loading and a countdown. Grab a coffee — email and Slack notify you when it’s ready.
- Review Pending Approval → Accept.
- Start monitoring. Badge goes Live. Counts read N monitored · M waiting.
Integrator names
Same object. Different words:app_query is the Target mapper’s camelCase object, not the echoed snake_case graph-search object. Target discovery uses a different schema and is not an exact replay of the graph search. See Search query compatibility. Create returns 202 if a find-people job was queued.
Accept everyone currently pending: