docs(audiences): add Find people from this list section for Companies Audiences

[george-dilthey]

What changed

Added a new ## Finding people from a Companies Audience section to docs/audiences.md, positioned between "Creating an audience" and "Enriching and monitoring." The section explains the Find people from this list option in the ⋮ three-dot menu on a Companies Audience segment — the direct path to run a people search scoped strictly to companies in an audience, without needing a separate company table.

Why

Intercom conversation #215475102001801 — a WeTransact Enterprise customer asked: "how can I use the Find People tool to just find people from companies that I've filtered into the company audience?" Fin escalated to a human after giving incorrect guidance (it kept describing a company-table path). Human agent Bo correctly answered with the Audience ⋮ menu → Find people from this list workflow, but that workflow was not documented anywhere in the docs.

audiences.md had no mention of "Find people from this list." find-people-overview.md has no reference to Audiences as a starting point. finding-companies-and-people-in-clay.md describes "Find People at These Companies" only from a company table path (Tools → Import tab → Find People at These Companies). The Audience-native entry point was a complete gap.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/apps/w28k1kwz/inbox/inbox/all/conversations/215475102001801
• Code evidence (PASS): clay-base/apps/frontend/src/state/Audiences/useAudienceSegmentDropdownOptions.tsx:225-227 — 'Find people from this list' added unconditionally when segment.entityType === AudienceEntityType.Account; handler at line 113 calls createCPJSource with company_audience_segment_id: segment.id scoping the search strictly to the audience.
• Code evidence (liveness): clay-base/apps/frontend/src/components/Audiences/AudiencesHeader.tsx:232 — the three-dot header button renders this option; AudiencesSidebar/AudiencesSegmentItem.tsx:229 — sidebar kebab also renders it. No feature flag gates either path.
• Slack context (verifier): #team-audiences thread (Rachel Gurman, 2026-04-21) explicitly references "3 dots at the top > find people from this list" with feedback that discoverability is low — confirming this is live but poorly surfaced.

Uncertainties

None for the content itself. Feature label, access path, and scoping behavior all confirmed against code. GA to all customers with no gating.

Note: pre_pr_check returned ok: false solely because 12 other open PRs exist on audiences.md (all on unrelated topics — Salesforce export, signals, Databricks, deduplication, etc.). None of those PRs address "Find people from this list." This PR is proceeding per the "materially new" path described in the docsbot guidelines.

Related observations

• finding-companies-and-people-in-clay.md describes only the company-table path for Find People at These Companies (Tools → Import tab) — a cross-reference pointing Audience users to this new section could improve discoverability further, but is out of scope for this trigger.
• Existing open PRs on audiences.md that reviewer should reconcile at merge time: docs(audiences): add FAQ for why users only see Sync to ad platforms in Send menu #1623 (Send menu), docs(audiences): add Export sync toggle prerequisite for Salesforce write-back #1615 (Salesforce export sync), docs(audiences): document signal detection-layer model and Data Hub vs. table scope #1605 (signals), docs(audiences): document archived record behavior on source re-sync #1587 (archived records re-sync), docs(audiences): add read-only Salesforce field types and cross-object enrichment FAQ #1585 (SFDC read-only fields), docs(audiences): add errored-row run-condition fix, delete-row note, and field-deletion FAQ #1582 (errored enrichment rows), docs(audiences): document Intelligence tab on company records (beta) #1569 (Intelligence tab), docs(audiences): document nested sub-field mapping in bulk enrichments #1558 (sub-field mapping), docs(audiences): add CSV export workaround via Add to workbook #1550 (CSV export), docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547 (Companies deduplication), docs(audiences): document Salesforce custom object export limitation and workaround #1528 (signal export to SFDC), docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507 (Snowflake/BigQuery field mapping), docs(audiences): add Databricks as beta import source #1485 (Databricks import).

Closes DOC-1237

[linear-code]

DOC-1237