docs(audiences): add FAQ for deleting custom fields from Audiences

[george-dilthey]

What changed

Added a new FAQ entry — "How do I delete a custom field from Audiences?" — to docs/audiences.md, inserted immediately after the existing "How do I create a custom Audience field" FAQ. The new FAQ explains that the Audiences column header only shows Hide (not "Delete column" like in regular tables), and that field deletion is done through Data Hub → Fields tab → click the field → Delete field.

Why

Intercom conversation #215475688380546 (Lee Napierkowski, Branch): the customer asked "how do I remove columns that I created?" in the Audiences (People/Companies) view. Fin gave instructions for regular Clay tables (click column header → Delete column), which don't apply in Audiences — the customer kept replying "I only see hide." The ticket escalated to a human. The customer eventually found the answer themselves but said "Fix your AI" — indicating the docs did not give Fin enough context to answer correctly.

The root cause: docs/audiences.md had a FAQ on creating custom Audience fields but no corresponding FAQ for deleting them. The table column FAQ (docs/table-columns-overview.md) describes the standard "click column header → Delete column" path that doesn't exist in Audiences.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475688380546
• Verifier confirmed (PASS): AudiencesHeaderCell.tsx:17 — type AudienceHeaderAction = 'hide' (only Hide is available in the Audiences column dropdown, no Delete); deletion lives in AudiencesDataHealthSidebar/AudiencesFieldSidebar/AudiencesFieldDeleteButton.tsx — the sidebar opened from Data Hub → Fields
• Verifier Slack context: #team-audiences thread (2026-07-28) and #proj-audiences-core-product thread (2026-07-30) both document the same UX confusion about Audiences column deletion not being accessible from the column header

Uncertainties

None. The code unambiguously shows: (1) column header in Audiences only has Hide, (2) Delete field lives in the Data Hub field sidebar.

Related observations

• There are many other open PRs on docs/audiences.md (PRs docs(audiences): replace non-existent Continue button with Upsert segment record instructions #2383, docs(audiences): add FAQ for moving audience segments between workspaces #2370, docs(audiences): document Salesforce export full-load behavior, API monitoring, and Last Enriched timestamp #2356, docs(audiences): document that Lookup in Audiences cannot scope to a segment, add workaround FAQ #2354, docs(audiences): document OR filter group with AND exclusion pattern #2349, docs(audiences): add archive cross-reference for Salesforce-deleted records #2348, docs(audiences): clarify legacy plan access and add why-not-visible FAQ #2345, docs(audiences): expand field mapping intent best practice to cover SFDC import sync path #2323, docs(audiences): add common HubSpot contact and company field examples #2321, docs(audiences): add FAQ for Salesforce duplicate company records #2305, docs(audiences): add FAQ for time-gated audience segment membership #2303, docs(audiences): document Salesforce SOQL import for Enterprise customers #2295, docs(audiences): restructure Clay table section and rename Upsert/Update Audiences Record actions #2291, docs(audiences): rewrite Clay table import section and fix Upsert action name #2288, docs(audiences): add FAQ for fixing existing duplicates, fix Import Record Matching scope #2280, docs(audiences): add CRM and warehouse sync cadence anchor sections #2272, docs(audiences): note that HubSpot sync time of day is not shown in the UI #2261, docs(clay-ads): add EEA consent, platform fields, delete-recreate behavior, match rate clarification #2251, docs(audiences): document Update segment record as admin-only and clarify permission error #2245, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2232, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2231, docs(audiences): add concrete use-case guidance to Audiences vs. Tables FAQ #2225, docs(audiences): clarify Find People destination when using Audience as Target companies #2224, docs(audiences): explain Clay-prefixed auto-populated fields and fix export credits FAQ #2215, docs(audiences): explain why Audiences fields have values when CRM fields are blank #2210, docs(audiences): cover archived workbook behavior in Origin source filter FAQ #2204, docs(audiences): explain signal vs bulk-enrichment relationship and fix auto-enrich timing #2203, docs(audiences): explain that archived source tables remain in Origin source filter #2202). None of them address the "How do I delete a custom field from Audiences?" topic — confirmed by inspecting each diff.
• The Roles and permissions table in audiences.md does not include a row for "Create/delete custom fields." The code shows ManageFields is granted to both WorkspaceAdmin and WorkspaceMember — there may be a doc gap there, but it is out of scope for this PR.

Closes DOC-2154

[linear-code]

DOC-2154