docs(audiences): document Intelligence tab on company records (beta)

[george-dilthey]

What changed

Extended the ### Claygent-managed columns section in docs/audiences.md to document the new Intelligence tab on company record detail panels in Audiences. When Claygent intelligence is enabled for a workspace, opening a company record in Audiences adds an Intelligence tab to the detail panel alongside Overview, Activity, People, and Deals. The tab has two sections: Active Claygents (Claygents configured for that specific company) and Claygent fields (field values written by a Claygent). Documented with explicit beta framing since the feature requires workspace-level enablement.

Why

Commit b6be041e4d194208dee79cf26b1e22ceb1310f40 in clay-run/clay-base (eb65070...b6be041) added AudiencesEntityDetailIntelligenceTab.tsx — a new tab in the account/company entity detail overlay — and a corresponding API endpoint (GET /workspaces/:workspaceId/audiences/accounts/:accountId/configured-claygents). The tab is gated by EppoFeatureFlags.EnableAudiencesAgentConfigs (Eppo flag enable-audiences-agent-configs, default false). The verifier confirmed this is a customer-facing opt-in flag (BETA), not internal-only. The existing docs/audiences.md had no documentation of the Intelligence tab or the account-level Claygent detail view.

Source link(s)

• Deploy: https://github.com/clay-run/clay-base/actions/runs/29396967161
• Diff: https://github.com/clay-run/clay-base/compare/eb650700ea5dfeb6c88a4658bbe4cd55ee7e2e58...b6be041e4d194208dee79cf26b1e22ceb1310f40
• Verifier: BETA verdict — EppoFeatureFlags.EnableAudiencesAgentConfigs at /workspace/clay-base/libs/shared/src/EppoFeatureFlags.ts:140; gating at /workspace/clay-base/apps/frontend/src/components/Audiences/AudiencesEntityDetail/AudiencesEntityDetailOverlay.tsx:33; tab config at /workspace/clay-base/apps/frontend/src/components/Audiences/AudiencesEntityDetail/audiencesEntityDetailTabs.ts:27-33
• Slack context (from verifier): #team-audiences thread (Jun 12, 2026) confirms enable-audiences-agent-configs is a customer-facing opt-in flag manually enabled per workspace

Uncertainties

None — code clearly shows the tab UI labels ("Active Claygents", "Claygent fields", "No intelligence yet"), tab order (appended after Deals), and that it is account-only (not contacts or custom entities). Liveness verified as BETA by verifier sub-agent.

Related observations

• The existing "Claygent-managed columns" paragraph refers to "Companies audience" for the column-header icon feature; the Intelligence tab also applies to Companies (AudienceEntityType.Account). Both live in the same section — no structural change needed.
• The same Eppo flag also gates account prioritization and the Slack audiences bot; those features are not documented in this PR as they were already live before this deploy.
• Several other open PRs also touch docs/audiences.md (PRs docs(audiences): add Databricks as beta import source #1485, docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507, docs(audiences): document Salesforce custom object export limitation and workaround #1528, docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547, docs(audiences): add CSV export workaround via Add to workbook #1550, docs(audiences): document nested sub-field mapping in bulk enrichments #1558) — none of them cover the Intelligence tab or the ### Claygent-managed columns section. This PR's addition is to that section only, which none of those PRs touch. Materiality confirmed: no existing PR or doc passage covers this new tab.

Confidence: high

Closes DOC-1169

[linear-code]

DOC-1169