On this page
What HubSpot supports natively for divisions
In one portal:
| Feature | Use for divisions | Requirement |
|---|---|---|
| Teams | One team per division; team-only record access; division reports | Professional or Enterprise |
| Nested teams | Division > region > team, with parents seeing everything below | Enterprise |
| Asset access limits | Keep some assets visible only to a division’s users and teams | Varies by asset; Super Admins still see them |
| Brands | Separate domains, emails, forms and subscription types per division | Marketing Hub Enterprise plus one add-on per brand |
Across several portals:
| Feature | Use for divisions | Requirement |
|---|---|---|
| Multi-account management | Connect division portals; mirror contacts and companies (read-only in the destination); copy automated emails, lists and forms; multi-account workflows and reports | Enterprise main account; up to 29 connected Professional or Enterprise accounts; same data location for reporting |
| Account switching | One login for every portal a user belongs to | The user is added to each portal |
One HubSpot portal or several: how to decide
| Question | One portal | Several portals |
|---|---|---|
| Do divisions sell to the same customers? | Yes | No |
| Do they share a sales or service team? | Yes | No |
| Same lifecycle stages and pipelines? | Mostly | Different |
| One revenue view needed daily? | Yes | Occasional, via multi-account reports |
| Might a division be sold or spun off? | Unlikely | Likely |
| Separate legal, consent or data-hosting needs? | No | Yes; get specialist advice |
If most answers fall in the first column, use one portal and design teams and permissions carefully. If several fall in the second, use separate portals and plan how you’ll keep shared definitions consistent.
Common mistakes
- Splitting early for tidiness, then needing cross-division reports every week.
- One portal without partitioning, so every user sees every division’s records and workflows.
- Assuming a location or division property controls access. It classifies records; permissions control access.
Where Jetstack AI fits
For one portal, Jetstack AI Projects, currently in limited release, builds the agreed division properties, pipelines and routing workflows from a brief, with the plan and the deployment approved separately and a receipt read back from HubSpot; teams and users stay a manual step. For separate division portals, build the shared setup once with a Project, then Jetstack’s Portal reuse deploys it to the destination portal you choose, matching assets that already exist and remapping references. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See Jetstack for in-house teams and how deployment works.
Sources
- Create and manage teams (HubSpot Knowledge Base)
- Limit access to your HubSpot assets (HubSpot Knowledge Base)
- Set up multi-account management (HubSpot Knowledge Base)
- Manage your brands with HubSpot Brands (HubSpot Knowledge Base)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Multiple portals & franchises
Run your own portal like a delivery team.
Audit your own portal, scope the change and ship it with approvals and a record of what changed.
See how in-house teams use Jetstack