On this page
What HubSpot supports natively
Franchise setups combine general HubSpot features:
| Feature | What it gives a franchise | Requirement |
|---|---|---|
| Teams | Group users by location; team-only record access; team-based reports | Professional or Enterprise; nested teams need Enterprise |
| Asset access limits | Restrict some assets to specific users and teams | Varies by asset; Super Admins still see restricted assets |
| Brands | Separate domains, emails, forms and subscription types per brand in one account | Marketing Hub Enterprise plus one add-on per brand |
| Multi-account management | Connect separate location 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 |
How franchises should set up HubSpot
| Question | One shared portal | A portal per location |
|---|---|---|
| Who owns the customer? | Head office | The franchisee |
| Shared marketing database? | Yes | Each location has its own |
| Local autonomy over settings? | Limited | Full |
| Network-wide reporting | Native, in one account | Multi-account reports or a warehouse |
| Cost structure | One subscription, more seats | One subscription per location |
| Franchisee leaves | Remove users and reassign records | Hand over or close their portal |
Whichever you pick, follow the same order:
- Agree the shared definitions: lifecycle stages, enquiry types, pipeline stages and a stable location identifier.
- Decide what stays local: owners, opening hours, sender details, local offers.
- Build the baseline once and test it with one pilot location.
- Roll it out location by location, mapping owners and pipelines in each.
- Keep a change register so later updates don’t overwrite legitimate local changes.
How to model the franchisee businesses themselves is covered in how a franchise should structure company records, and the full design in the multi-location guide.
Where Jetstack AI fits
Jetstack AI builds the baseline once with Projects, currently in limited release: you describe the shared properties, pipelines and workflows in a brief, approve the plan and then the deployment, and get a receipt read back from HubSpot. Portal reuse then brings that baseline into each location’s portal, matching existing assets and remapping owners, pipelines and properties. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. Each deployment is a separate, reviewed copy; there is no automatic enforcement across the network. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. See Jetstack for franchises and property mapping.
Sources
- Create and manage teams (HubSpot Knowledge Base)
- Set up multi-account management (HubSpot Knowledge Base)
- Manage your brands with HubSpot Brands (HubSpot Knowledge Base)
- Property mapping during deployment (Jetstack AI documentation)
Checked November 5, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Multiple portals & franchises
One standard, adapted for each location.
Build the standard setup once, then adapt and deploy it to each location portal.
See the franchise workflow