GoHighLevel Multiple Locations: What Actually Changes

GoHighLevel Multiple Locations: One Sub-Account per Site

A GoHighLevel sub-account is the building block behind every location a business runs. Open the agency view, create one, and that site gets its own contacts, pipelines, calendars and phone number, separate from every other location.

Getting GoHighLevel multiple locations right starts with accepting that structure instead of fighting it. Account-level users are restricted to the sub-accounts they're assigned, with no visibility into the wider agency dashboard, and that's deliberate: a manager at one branch has no business seeing the books of another.

HighLevel prices this by sub-account ceiling, not location count, though the two track closely once a client opens a second site.

Three locations fit on Starter. A fourth usually pushes agencies onto Unlimited.

AI features price per sub-account too, per HighLevel's own pricing page: Growth runs $50 a month per location, Unlimited runs $97, and a five-location client pays that five times over.

Giving One Person Access to Several Locations Without Agency Keys

Plenty of clients want a regional manager who sees three branches and nothing else. That's what account-level roles are for.

HighLevel's own walkthrough on setting this up boils down to a short sequence inside the agency view.

1. Switch to Agency view and open Settings, then the Team tab.
2. Add the user and set their type to Account, never Agency.
3. Search for each sub-account they should manage and add it to their profile.
4. Toggle the specific permissions for that role, then save. An invitation email goes out automatically.

Getting the user type wrong at step two is the most common way this goes sideways. Set it to Agency by habit, and that manager suddenly sees every client on the account.

Our breakdown of GoHighLevel's permission roles covers the finer distinctions between Account and Agency users.

On mobile, a team member can opt into Multi-Location Incoming Calls, which rings their phone for any of up to ten assigned locations at once.

Each call carries a badge showing which site it came from, so the person answering can switch into the right workspace mid-conversation, per HighLevel's mobile documentation.

Where the Location Model Still Breaks Down

This structure holds up well right until a client wants their locations to feel like one business instead of several separate logins.

HighLevel's own product-feedback forum carries a request from an agency managing a dental clinic with three offices, asking for a shared client database across locations instead of three disconnected ones.

Branches can't pool contacts or pull one performance report across sites without jumping between sub-accounts one at a time.

Booking carried a similar problem. Teams running several locations duplicated calendars and staff profiles for every site.

In one feature request, a plastic surgery clinic described five locations turning into what they called "an absolute mess" of repeated names. HighLevel marked that fix complete in Services v2, in June 2025, with one calendar now carrying a location selector instead of a duplicate per site.

None of this is a reason to avoid sub-accounts. A snapshot built once and pushed into every new location keeps workflows, pipelines and funnels consistent across a growing client base, which beats rebuilding each site's automation from scratch.

Agencies packaging a multi-location rollout as a recurring product often lean on that same snapshot inside a SaaS Mode plan, billing each client monthly instead of re-quoting the build every time a branch opens.

Solid GHL setup work and a clean sub-account structure from the start make that scaling step far less painful later.

Decide the shared-data question before the second location goes live, not after the first support ticket about a missing contact.

Cover photo by Laura Tancredi on Pexels