docs(audiences): add FAQ for moving audience segments between workspaces

[george-dilthey]

What changed

Added a new FAQ entry "Can I move an audience segment to a different workspace?" to docs/audiences.md, placed immediately after the existing "How do I export my audience data to CSV?" FAQ. The new entry explains that direct workspace-to-workspace transfer is not supported and describes the CSV export → import workaround.

Why

Intercom conversation #215475660456807: Andrea Liu from Xero (Enterprise customer) asked support whether it was possible to move an audience from one workspace to another. Fin could not resolve the question — it was escalated to and answered by human support agents Bo Morin and Jessica Fan. The docs had no entry for this question, which is why Fin couldn't answer.

Support's answer: Moving audiences between workspaces is not directly supported. The workaround is to export the audience segment as a CSV (via the "Add to workbook" export path already documented in the FAQ) and import the CSV into the target workspace via Add data → Add Source → CSV.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475660456807
• Slack trigger thread (ent-xero-clay channel): https://clay-hq.slack.com/archives/C08KSA4G7FE/p1787779974073379
• Human support reply (Bo Morin): https://clay-hq.slack.com/archives/C08KSA4G7FE/p1787786387331549
• Jessica Fan clarification on export steps: https://clay-hq.slack.com/archives/C08KSA4G7FE/p1787834208688179
• Verifier code evidence:
  • No cross-workspace transfer endpoint: clay-base/apps/api/v3/audiences/audiences.router.ts (workspace-scoped routes only)
  • Export scoped to current workspace: clay-base/apps/frontend/src/components/Audiences/Send/ExportAction.tsx
  • 50,000 row cap on "Add to workbook" confirmed: clay-base/apps/api/v3/audiences/exportToWorkbook.service.ts:23 (MAX_ROWS = 50_000)
  • CSV import path confirmed: clay-base/apps/frontend/src/components/Audiences/AddData/CsvSourceSetup.tsx

Uncertainties

None. Both the "no cross-workspace transfer" claim and the CSV export → import workaround are PASS-verified by the verifier sub-agent against the codebase. The 50,000-row limit on the "Add to workbook" path (referenced in the new FAQ entry) was already correctly documented in the preceding FAQ and is confirmed by code.

Related observations

• A support agent (Jessica Fan) informally told the customer "No limit!" on rows when asked about export limits. This referred to a different export path (bulk enrichment → archive → CSV, described in the Slack thread at https://clay-hq.slack.com/archives/C08KSA4G7FE/p1784144257542569), which is distinct from the "Add to workbook" path and is not currently documented in the FAQ. The "Add to workbook" path's 50,000-row cap is correctly stated in the existing FAQ and the new entry references it. The alternative bulk enrichment export path is complex (requires running enrichments) and is not in scope for this PR.
• The internal Linear request FED-2333 for admins to move assets between workspaces was mentioned by support agents in internal notes. Not referenced in the customer-facing doc (correctly — internal roadmap items should not appear in customer docs).
• Many other PRs are currently open against docs/audiences.md (PRs docs(audiences): document Salesforce one-connection limit and Incomplete status #2184, docs(audiences): document signal date limitation and add FAQ #2195, docs(audiences): explain that archived source tables remain in Origin source filter #2202, docs(audiences): explain signal vs bulk-enrichment relationship and fix auto-enrich timing #2203, docs(audiences): cover archived workbook behavior in Origin source filter FAQ #2204, docs(audiences): explain why Audiences fields have values when CRM fields are blank #2210, docs(audiences): explain Clay-prefixed auto-populated fields and fix export credits FAQ #2215, docs(audiences): clarify Find People destination when using Audience as Target companies #2224, docs(audiences): add concrete use-case guidance to Audiences vs. Tables FAQ #2225, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2231, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2232, 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). None of them add a FAQ about moving audience segments between workspaces — this change is materially new and non-overlapping.

Closes DOC-2134

[linear-code]

DOC-2134