docs(audiences): note that company fields don't carry through Find People to People records

[george-dilthey]

What changed

Added a **Note:** to the "Finding people from a Companies Audience" section of docs/audiences.md explaining that company-level fields already enriched on Companies Audience records — such as competitive data, technographics, or other custom columns — do not automatically carry over to People records found through a Find People search. The note also documents the workaround: add a Lookup in Audiences column (Object type: Companies) in a bulk enrichment table on the People Audience, filtering by the person's company domain or LinkedIn URL.

Why

Intercom conversation #215475675086155 (IntelliTrans | Audiences - People not Mapping to Companies): A customer asked why company-level fields (competitive system data) from their Companies Audience weren't appearing on the People records sourced via "Find People from this list." Support agent Bo confirmed this is a current limitation — company-level enriched fields don't carry through — and that adding a manual lookup column is the correct workaround. The "Finding people from a Companies Audience" section in docs/audiences.md described how to use the feature but said nothing about this limitation, leaving Fin unable to answer this question.

The behavioral claim was verified by the Docsbot Verifier sub-agent: apps/api/v3/fpac/services/fpac-destination-writers.ts shows that AudiencesDraftDestinationWriter.writeResults() calls profileToImportRecord() which maps only person-level CPJ fields (name, first_name, last_name, url, location_name, etc.) — no company audience field values are included. The claim that company-level enriched fields don't auto-carry to People records is code-confirmed.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/apps/w28k1kwz/inbox/inbox/all/conversations/215475675086155

Uncertainties

FPAC liveness (Eppo flag Enable-FPAC default-off, dashboard-controlled): The verifier returned UNKNOWN on whether the Find People at Companies (FPAC) feature is live for all customers, in beta, or internal-only. The Eppo flag is default-false in code (libs/shared/src/EppoFeatureFlags.ts:568, apps/frontend/src/components/WorkspaceTopbar/WorkspaceTopbarNavigator.tsx:743, apps/api/v3/ai/endpoints/ai-generation.endpoints.ts:1310) and its targeting config lives in the Eppo dashboard, not the repo. No GA announcement was found in Slack.

However, I did NOT add beta framing to the new note for two reasons: (1) the existing "Finding people from a Companies Audience" section in docs/audiences.md already documents this feature without any beta framing (last synced 2026-08-20), and (2) the Intercom ticket shows a real customer actively using the feature on workspace 859875 — they successfully received People records from a Company Audience Find People search. Adding beta framing only to my note while the surrounding documentation has none would be inconsistent and confusing. A reviewer with Eppo dashboard access should confirm whether FPAC's targeting is broad enough that no beta flag is warranted for the existing section either.

Related observations

• The support agent noted this is a known gap flagged with the product team, with no ETA for a native fix. Per docs policy, the note describes current behavior neutrally and provides the workaround — no mention of bugs or upcoming fixes.
• Issue 2 in the conversation (null company field on People records caused by a bulk enrich overwrite) is a configuration issue specific to this customer, not a general product limitation. No doc change needed for that issue.
• There are many open PRs on docs/audiences.md (PRs docs(audiences): document Update segment record as admin-only and clarify permission error #2245, docs(clay-ads): add EEA consent, platform fields, delete-recreate behavior, match rate clarification #2251, docs(audiences): note that HubSpot sync time of day is not shown in the UI #2261, docs(audiences): add CRM and warehouse sync cadence anchor sections #2272, docs(audiences): add FAQ for fixing existing duplicates, fix Import Record Matching scope #2280, docs(audiences): rewrite Clay table import section and fix Upsert action name #2288, docs(audiences): restructure Clay table section and rename Upsert/Update Audiences Record actions #2291, docs(audiences): document Salesforce SOQL import for Enterprise customers #2295, docs(audiences): add FAQ for time-gated audience segment membership #2303, docs(audiences): add FAQ for Salesforce duplicate company records #2305, docs(audiences): add common HubSpot contact and company field examples #2321, docs(audiences): expand field mapping intent best practice to cover SFDC import sync path #2323, docs(audiences): clarify legacy plan access and add why-not-visible FAQ #2345, docs(audiences): add archive cross-reference for Salesforce-deleted records #2348, docs(audiences): document OR filter group with AND exclusion pattern #2349, docs(audiences): document that Lookup in Audiences cannot scope to a segment, add workaround FAQ #2354, docs(audiences): document Salesforce export full-load behavior, API monitoring, and Last Enriched timestamp #2356, docs(audiences): add FAQ for moving audience segments between workspaces #2370, docs(audiences): replace non-existent Continue button with Upsert segment record instructions #2383, docs(audiences): document ad sync beta availability and per-workspace connections #2395, docs(audiences): document enrichment workflow beta option #2415). None of them address the company-field-inheritance limitation documented in this PR — confirmed by reviewing each PR's diff.

Closes DOC-2207

[linear-code]

DOC-2207