Multi-Organization (Network) Support
Last updated: May 29, 2026
What this is
If your SmartRec setup is a network — multiple branches under one umbrella — the integration can sync all of them into a single HubSpot portal. This article explains how the integration keeps branch data distinguishable in HubSpot.
How records stay unique across branches
Most SmartRec IDs are formatted with an organization suffix — {id}_{orgId} — to prevent collisions when two branches reuse the same ID. This applies to:
Account IDs
Invoice Item IDs (donations, memberships, multipasses, registrations)
Donation IDs, Membership IDs, MultiPass IDs
Activity IDs, Activity Occurrence IDs
Registration IDs, Location IDs
The one exception: Person IDs. smartrec_person_id is stored without the organization suffix. This is intentional — a person can belong to multiple branches in a network, and you want their Contact record to consolidate those memberships, not split into one Contact per branch.
The smartrec_organization property
Every synced object carries a smartrec_organization property identifying which branch the record belongs to. The value comes from a per-branch configuration variable in the integration — it is not read from the SmartRec payload, so it's set by you during setup and stays consistent.
📸 Screenshot: Integration settings showing a list of branches with their smartrec_organization values.
Two different behaviors
Object type |
|
|---|---|
Contacts | Multi-select (checkbox). A person can be associated with multiple branches simultaneously. |
Everything else | Single-select. Each record belongs to one branch. |
New branch names are added automatically
When the integration sees a branch name it hasn't synced before, it adds it as a new option to the smartrec_organization property. You don't need to pre-create options.
Using smartrec_organization in HubSpot
This property is the single best filter for branch-scoped views in HubSpot. Some practical uses:
Lists: Build active lists of "Branch A members" or "Branch B membership purchasers."
Reports: Group revenue by branch.
Workflows: Trigger branch-specific email sequences.
Views: Save Deal board views filtered to one branch's pipeline.
Things to know
Person IDs are not branch-suffixed. If you're searching for a contact by
smartrec_person_id, don't append a branch suffix — it won't match.One HubSpot portal per integration install. A single integration install can serve a network, but you cannot mirror the same network to multiple HubSpot portals from one install.
Branch removal in SmartRec. Removing a branch from the integration's configuration does not delete its synced records from HubSpot. Records remain — they just stop receiving updates.