Per-client configuration

Buying groups

Per-Opportunity Buying Groups lets each deal carry its own buying-group structure, and lets a single person hold seats on more than one group at once (the "CFO on every BG" case). Defaults to off for every tenant.

Per-Opportunity Buying Groups

Opt this tenant in to per-deal buying-group structure and the HubSpot Deals + Companies sync that drives it.

Per-Opportunity Buying Groups is disabled.

Flipping this on activates three things on the next connector sync: HubSpot Companies sync (writes to accounts with source='hubspot_companies'; HubSpot wins over the email-domain matcher on conflict), HubSpot Deals sync (populates the opportunities table), and a third writeback push that records each multi-BG seat as a HubSpot custom association.

HubSpot portal recipe

Walk your HubSpot admin through these steps so the buying-group association write lands. The platform's primary BG property write continues even when this isn't set up — see Decision 7's graceful fallback.

Open HubSpot Settings → Objects → Associations.
Create a new custom association labelled buying_group with one end on Contact and the other on a tenant-owned Buying group object.
Grant the Tidal Wave OAuth app the crm.objects.contacts.write and association-write scopes (these were requested during the initial install).
Trigger a sync. The platform's next writeback run records one association row per multi-BG seat; the checklist flips to "Setup complete" automatically.