Problem

Org custom fields flagged background === true are internal sub-event taxonomy "moments" (discovery questions, objections, MEDDPICC signals) extracted purely for analysis. They are supposed to be hidden from users, but no frontend path filtered them out, so they leaked into every user-facing field surface.

An audit of apps/mail found the flag is background (not isBackground , that's an unrelated aop_agents concept), and that zero normal display paths excluded it. The only place touching the flag was IntelligenceFieldsEditor, which does the inverse (keeps only background fields , it's the taxonomy editor).

Leak sites fixed:

• CRM table columns (use-crm-configuration)
• Canvas columns + sort/filter defs (use-canvas-configuration)
• Sidebar columns + merged defs (use-sidebar-all-columns)
• Virtualized row cells (VirtualizedTableRow)
• Group-by picker (SidebarGroupByPicker)
• CRM field-mapping options (extractCustomFieldsFromAOPs)
• Conversation overview grid / showAllFields + configured lookups (ConversationOverviewCard, conversationFieldRenderers)
• Strategic overview sections (StrategicOverviewTab)
• Working-memory editable rows (workingMemoryCard)

Fix

Centralized in a single shared helper , getVisibleFieldDefinitions (in apps/mail/modules/crm/utils/background-fields.ts), mirroring the server's pickBackgroundFields. Every display consumer of aop.customFieldDefinitions now routes through it.

• The filter is applied at the display consumers, not at the aopSlice/useAOPs origin, because the taxonomy editor (IntelligenceFieldsEditor) and admin/field editors legitimately need to see background fields.
• Also declares background?: boolean on the frontend CustomFieldDefinition type, which previously omitted the flag even though it exists at runtime (via RouterOutputs).

Scope

Intentionally not touched: IntelligenceFieldsEditor (the dedicated taxonomy editor) and admin/field-config editors , power-user surfaces that should still see background fields.

Verification

• apps/mail typecheck: zero net-new errors vs. staging baseline (compared full sorted error sets; the only diffs in touched files are pre-existing errors whose line numbers shifted by the lines added).
• Thermo-review: APPROVED WITH NITS (one negligible double-getVisibleFieldDefinitions call in two memoized column hooks; consistency of the single helper preferred over an inline guard).

🤖 Generated with Claude Code

Greptile Summary

This PR centralizes filtering of background taxonomy fields and applies it across conversation, CRM, canvas, sidebar, mapping, and strategic-overview surfaces.

• Adds getVisibleFieldDefinitions and the frontend background field type
• Routes user-facing field-definition enumeration through the shared visibility helper
• Leaves the working-memory fallback path unfiltered while AOP metadata is unavailable

Confidence Score: 4/5

The working-memory visibility gap should be fixed before merging because internal background values remain reachable whenever AOP metadata is unavailable.

Most display consumers consistently filter field definitions, but WorkingMemoryCard deliberately falls back to the complete custom-field array during AOP loading or lookup failure and renders those entries as editable inputs.

Files Needing Attention: apps/mail/modules/conversations/components/workingMemoryCard.tsx

Important Files Changed