GoHighLevel Sub Accounts: Features, Setup & Practical Guide

GoHighLevel Sub Accounts are separate business workspaces inside a HighLevel agency account. Each sub-account—also called a location—can maintain its own contacts, conversations, pipelines, workflows, calendars, websites, funnels, users, phone settings, integrations, payments, and other business configuration. For agencies, this structure makes it possible to manage multiple clients from one Agency View without placing every client's data inside the same CRM environment.

A practical Go High Level structure might look like Agency Account → Client A Sub-Account → Client B Sub-Account → Client C Sub-Account, with each client operating in an isolated workspace.

HighLevel also now distinguishes an Agency Sub-Account, which is a regular sub-account designated as the agency's own internal business workspace rather than a client's account. HighLevel states that all sub-accounts still function as locations; the designation simply identifies whether a location belongs to the agency itself or to a client.

This makes GHL Sub Accounts one of the most important concepts to understand before building an agency, multi-location operation, or SaaS business on HighLevel.

This guide explains how GoHighLevel Sub Accounts work, what belongs inside them, how to create and organize them, how users and permissions operate, how Snapshots can accelerate setup, how account transfers work, and how agencies can manage larger numbers of client locations efficiently.

For a dedicated resource focused specifically on this structure, see our complete GoHighLevel Sub Accounts guide.

Create a separate CRM workspace, add a pipeline, calendar, workflow, form, and users, then test how Agency View and sub-account management work together.

Start Your GoHighLevel 30-Day Free Trial →

A GoHighLevel Sub Account is an individual location-level workspace inside an agency account that contains the CRM, marketing, communication, automation, and business configuration for one business or operational unit.

In most agency setups, one sub-account represents one client.

For example:

Agency View

Client A — Dental Practice
Client B — HVAC Company
Client C — Marketing Consultant

Each client can have separate contacts, workflows, pipelines, calendars, conversations, forms, websites, users, and integrations.

This is significantly cleaner than storing every client inside one shared CRM.

HighLevel's current documentation continues to refer to sub-accounts as locations and distinguishes between client locations and an Agency Sub-Account used for the agency's own business.

The Go High Level Agency Account is the management layer above the individual sub-accounts.

Agency View is where agency-level operations are handled.

Sub-accounts are where individual businesses actually perform CRM and marketing work.

A simplified structure is:

Agency Level → Manage Clients and Agency Configuration

Sub-Account Level → Manage Contacts, Opportunities, Workflows, Calendars and Customer Activity

HighLevel's current role matrix confirms this separation. Agency-level permissions include capabilities such as creating or deleting sub-accounts, managing agency billing, SaaS Mode, snapshots, global integrations, and white-label configuration. Sub-account-level users instead work with areas such as opportunities, workflows, calendars, conversations, contacts, reputation management, and funnels.

A GHL Sub Account can contain most of the day-to-day CRM and marketing systems used by the business represented by that location.

Typical sub-account assets include contacts, opportunities and pipelines, workflows, campaigns, calendars, appointment settings, conversations, websites, funnels, forms, surveys, reputation tools, media, phone configuration, payment integrations, AI tools, and users.

HighLevel's September 2026 permissions documentation now exposes more than 80 controllable features at the sub-account level, allowing agencies to determine which parts of the platform each client can access.

This makes sub-accounts more than simple folders.

They are operational workspaces with their own business configuration.

The primary purpose of GoHighLevel Sub Accounts is separation.

Agencies need a way to manage multiple businesses without mixing their data.

Imagine an agency with twenty clients.

Without separate locations, the agency could end up with contacts, calendars, workflows, phone numbers, pipelines, and users from twenty companies inside one CRM.

That would be extremely difficult to maintain.

With sub-accounts, each client can operate separately while the agency remains in control from Agency View.

Agencies are one of the clearest use cases for the sub-account model.

A marketing agency may create one location for each client.

For example:

Agency

→ Roofing Client
→ Dental Client
→ Fitness Client
→ Restaurant Client
→ Real Estate Client

Each client gets an isolated environment.

The agency can switch between sub-accounts from its central account rather than maintaining completely separate HighLevel subscriptions for every client.

Sub-accounts are not limited to traditional agencies.

A business owner managing several separate companies may also use distinct locations.

For example:

Business Group

→ Company A
→ Company B
→ Company C

The separation can help prevent contacts, workflows, calendars, branding, and reporting from becoming mixed.

Whether that structure is appropriate depends on how independently the businesses operate.

Sub-accounts can also be useful for multi-location organizations when each branch needs its own CRM environment.

A dental group might maintain:

New York Office

Boston Office

Chicago Office

Each location could have separate calendars, phone numbers, employees, reviews, campaigns, and contacts.

The corporate or agency team can still oversee all locations from the higher account level.

An Agency Sub-Account is a HighLevel sub-account designated as the agency's own internal workspace rather than a client's business.

HighLevel introduced clearer handling for this distinction in 2026.

When creating an eligible sub-account, users may be asked whether the account is:

This is my client's account

or

This is my own account

The second option identifies the location as the agency's own operational workspace.

For a basic agency, the Agency Sub-Account can be used to run the agency's own CRM and marketing.

For higher plans, it can also play a role in SaaS subscriptions, payment-provider configuration, and rebilling.

HighLevel states that on supported $297 and $497 configurations, the Agency Sub-Account can act as an operational hub for SaaS plans, subscriptions, and rebilling.

This makes it important to distinguish the agency's internal location from client locations.

The underlying HighLevel location architecture is similar, but the intended purpose differs.

A client sub-account represents a customer's business.

An Agency Sub-Account represents the agency's own business.

For a small agency, that might look like:

Agency Account

→ Agency's Own Sub-Account
→ Client 1
→ Client 2
→ Client 3

This structure lets the agency use HighLevel for its own lead generation while also managing client systems.

The number of client sub-accounts available depends on the HighLevel subscription tier.

HighLevel currently lists Starter at $97/month with 3 sub-accounts, while Unlimited at $297/month provides unlimited sub-accounts. Higher agency plans build on the Unlimited structure.

This distinction is one of the biggest reasons growing agencies move beyond Starter.

An agency with one or two clients may operate comfortably within Starter.

An agency planning to manage ten, fifty, or more client locations needs a structure without the three-sub-account ceiling.

Creating a GoHighLevel Sub Account normally begins from Agency View rather than from inside another client account.

The agency creates the location and provides the information required for the business being represented.

Depending on the plan and current interface, HighLevel may ask whether the new location belongs to the agency or a client.

After creation, the agency can enter the sub-account and configure the CRM.

Before creating a location, prepare the business identity and intended setup.

That may include business name, address, phone information, time zone, user assignments, website information, and which template or Snapshot should be used.

Having this information ready makes client onboarding more consistent.

A new sub-account can start as an empty business environment.

The agency then configures:

CRM fields
Pipelines
Calendars
Forms
Workflows
Websites
Phone
Email
Payments
Users
Integrations

This is appropriate when the client's system is highly customized.

However, agencies onboarding similar clients repeatedly will often save time by using Snapshots.

HighLevel allows agencies to create a new sub-account directly from an existing Snapshot.

The selected Snapshot can automatically load supported assets such as funnels, workflows, calendars, forms, and settings into the newly created location.

This changes onboarding from:

Create Empty Account → Rebuild Everything

to:

Choose Snapshot → Create Account → Customize

For niche agencies, that can save substantial time.

A practical agency process becomes:

Build Master Account → Create Snapshot → Create Client Sub-Account From Snapshot → Customize Client Settings

HighLevel notes that only one Snapshot can be selected during initial account creation, although additional Snapshots can be loaded afterward.

A Snapshot is not a replacement for client-specific configuration.

After creating a sub-account from a Snapshot, review items such as:

Business details
Phone numbers
Users
Domains
Calendars
Staff assignments
Payment providers
Email settings
External integrations
Custom values

HighLevel also notes that websites and funnels copied from a Snapshot are brought over as drafts and need the appropriate custom domain and publishing setup before they become live.

Create separate client workspaces, load a proven Snapshot, assign users, and test a repeatable onboarding process before scaling to more accounts.

Claim Your GoHighLevel 30-Day Free Trial →

HighLevel provides a centralized Sub-Accounts area where agencies can search, filter, open, and manage their locations.

In August 2026, HighLevel rolled out its redesigned Sub-Accounts List interface to the $97 and $297 agency plans, bringing modern filtering, bulk actions, and the same updated management experience already available on the Pro tier.

This becomes increasingly useful as the number of clients grows.

Managing five locations manually is straightforward.

Managing hundreds requires stronger filtering, bulk actions, standardized naming, and internal processes.

Use clear names.

For example:

Acme Dental — Austin

is more useful than:

Client Account 18

For multi-location clients, include location information consistently.

For agencies with many niche clients, standardized naming makes searching and support easier.

Users can be given access at the agency level or only to selected sub-accounts.

HighLevel's current access model lets an agency add users who can work across the agency or limit them to specific locations.

This is useful for employees and clients.

An agency owner may need access to every client.

A salesperson may need only selected accounts.

A client employee may need access only to their own business.

At the sub-account level, HighLevel currently uses two primary roles:

Admin

User

These roles can then be refined with granular permissions and visibility settings.

A sub-account Admin can generally manage more location-level settings.

A normal User can be restricted to the functionality required for their role.

HighLevel also provides Only Assigned Data visibility controls.

This can be useful when a salesperson should see only the contacts, opportunities, or appointments assigned to them rather than every record in the business.

For larger teams, this can make the CRM cleaner and reduce unnecessary exposure of customer information.

HighLevel's updated Feature Permissions system lets agencies control which platform modules a client can see and use.

As of September 2026, HighLevel documents more than 80 controllable features within the system.

For example, one client might receive access to:

Calendars
Opportunities
Phone System
AI Agents

while another receives a different combination.

This is particularly useful for agencies packaging HighLevel into different service tiers.

Giving every client access to every HighLevel module can create confusion.

A simple service client may not need to see SaaS tools, advanced AI features, website builders, or dozens of automation options.

Feature Permissions can create a cleaner interface by exposing only the functionality relevant to the client.

This can reduce training requirements.

An employee can also be given access to multiple sub-accounts without necessarily receiving full Agency View access.

HighLevel documents account-level user/admin configurations specifically for teams that need to manage several locations while remaining restricted from sensitive agency-wide settings.

This is useful for account managers.

An account manager may work with five clients but should not necessarily have access to agency billing or every customer account.

Agencies can give clients access to their own sub-account.

This allows the client to use appropriate CRM functions without exposing the agency's other customers.

The agency can decide which features and permissions the client receives.

For example, a client may need:

Contacts
Conversations
Opportunities
Calendars
Reporting

but not:

Agency billing
Snapshot management
Other sub-accounts
Global integrations

This separation is fundamental to the agency model.

Each client should generally have their own sub-account when their CRM data, users, workflows, phone system, and business configuration need to remain separate.

Do not combine unrelated clients simply to conserve locations.

Doing so can make permissions, reporting, compliance, and data ownership significantly harder to manage.

The sub-account model exists precisely to create that separation.

Phone numbers can belong to specific sub-accounts.

HighLevel now also provides a Move Numbers tool for eligible transfers between sub-accounts inside the same agency.

As of September 2026, the in-app tool supports eligible United States and Canada numbers under compatible phone environments.

However, moving a number does not automatically move contacts, conversations, historical analytics, A2P registration, or every related configuration.

This matters when reorganizing accounts.

HighLevel also provides a Copy Contact workflow action for duplicating contacts between sub-accounts.

HighLevel's March 2026 documentation says this can copy contacts along with supported tags and custom-field data when configured correctly.

This is different from transferring an entire sub-account.

Use contact-copying only when the business process genuinely requires the same contact to exist in more than one location.

Avoid duplicating large databases unnecessarily.

HighLevel supports transferring an entire sub-account from one agency to another eligible agency.

A transfer moves the sub-account as a whole rather than merging it with another location or moving only selected information.

HighLevel states that contacts, conversations, supported assets, and account history remain together within the transferred location.

This can be useful when a client changes agencies or assumes direct control of an existing location.

HighLevel's current process begins in:

Agency Level → Sub-Accounts → Manage Client → Actions → Transfer Sub-Account

The releasing agency enters the receiving agency's Relationship Number and submits a request.

The receiving agency then reviews and approves the transfer.

HighLevel now provides in-app tracking for sent and received transfer requests.

By default, the Agency Owner can initiate and complete eligible transfers.

The Agency Owner can also grant the appropriate transfer permission to selected Agency Admins.

This permission should be restricted carefully because transferring a client account can affect access, billing, integrations, and ownership relationships.

No. A sub-account transfer does not merge two locations.

HighLevel explicitly states that transferring a sub-account moves the entire location from one agency to another rather than combining its data with another sub-account.

If two businesses already have separate locations, moving one does not automatically consolidate their contacts, workflows, conversations, and history.

No.

HighLevel states that partial sub-account transfers are not supported.

The eligible sub-account moves together with its supported account data and assets.

This is why agencies should create clean account boundaries from the beginning.

HighLevel also supports bulk location transfers.

Its current bulk transfer workflow allows agencies to select multiple sub-accounts and move them to another eligible agency. The documented tool supports selecting up to 1,000 sub-accounts in one bulk operation.

This is more relevant to large agencies, acquisitions, migrations, or restructuring.

HighLevel also provides an Eject Sub-Account process that can turn an existing client location into a separate new HighLevel agency.

The process allows the existing sub-account to become independently owned rather than remaining under the original agency.

This can be useful when a client wants to leave the agency relationship but keep the account environment that has already been built.

HighLevel places additional restrictions around Agency Sub-Accounts because they may be tied to SaaS or billing dependencies.

Its current documentation specifically advises against transferring designated Agency Sub-Accounts and notes that removing the designation can be blocked while SaaS plans, subscriptions, or billing dependencies remain active.

This is another reason to designate the agency's own account correctly from the beginning.

SaaS Mode uses sub-accounts as the customer workspaces delivered through a HighLevel-based SaaS offering.

In this model, the agency creates SaaS plans and provisions client locations according to the selected package.

The customer receives access to the configured sub-account rather than the entire agency environment.

Feature permissions, user allowances, rebilling, and automation can then vary by SaaS plan.

HighLevel added additional control over SaaS user limits in 2026.

By default, SaaS plans allow unlimited sub-account-level users unless a specific User Limit is enabled. Agencies can define a limit at the SaaS plan level and override it for individual clients where necessary.

Agency-level users assigned to that location do not count toward the configured sub-account user limit.

This gives SaaS agencies another way to differentiate packages.

HighLevel also supports bulk actions for SaaS sub-accounts.

Agencies can select multiple locations and perform supported administrative actions without opening each account separately.

This becomes important once an agency manages dozens or hundreds of SaaS customers.

Manual configuration that works for ten customers becomes inefficient at scale.

Higher-level HighLevel plans can associate sub-accounts with supported rebilling and SaaS configurations.

This can allow an agency to charge clients for eligible services while keeping the billing structure linked to individual client locations.

The exact rebilling model depends on plan and service type.

Agencies should keep client billing settings separate and clearly documented.

A client location can also have its own payment integrations where appropriate.

For example, Client A may connect one Stripe account while Client B connects another provider.

This is another reason separate sub-accounts matter.

Customer payments from unrelated businesses should not be routed through one undifferentiated client configuration.

Integrations can also be configured at different account scopes.

Some agency-level services affect the wider organization, while many client-specific integrations belong inside the individual location.

For example, a client's calendar, payment processor, social account, or business-specific Marketplace connection normally belongs with that client.

Agencies should document which integrations require reauthorization when creating, copying, or transferring accounts.

Snapshots are one of the most useful tools for scaling sub-account creation.

Instead of manually building the same system repeatedly, an agency can create a standard source account and convert its supported configuration into a reusable Snapshot.

Then:

Snapshot → New Sub-Account → Client Customization

HighLevel's direct create-from-Snapshot functionality can automatically load the selected Snapshot during new account creation.

For niche agencies, this can dramatically reduce onboarding time.

Imagine an agency serving HVAC contractors.

The agency builds one master HVAC configuration containing:

Lead Pipeline
Missed Call Workflow
Estimate Follow-Up
Service Calendar
Review Workflow
Maintenance Reactivation

It converts that configuration into a Snapshot.

When a new HVAC client signs:

Create Sub-Account → Apply HVAC Snapshot → Add Client Branding → Connect Phone → Connect Calendar → Add Staff → Test

The agency now starts from a proven framework rather than an empty account.

Imagine a dental group with five locations.

The structure could be:

Agency / Organization

→ Austin Dental
→ Dallas Dental
→ Houston Dental
→ San Antonio Dental
→ Fort Worth Dental

Each location can maintain its own staff, appointment calendars, phone number, leads, patients, and reputation configuration.

Corporate management can still oversee the locations through appropriate agency-level access.

The most common GoHighLevel Sub Account mistakes are mixing unrelated businesses inside one location, creating inconsistent naming, granting excessive user permissions, duplicating contacts unnecessarily, and assuming Snapshots configure every client-specific integration automatically.

Another mistake is giving client users Agency View access when they only require their own location.

Use sub-account-level access whenever agency-wide access is unnecessary.

Agencies should also avoid sharing one client's connected payment provider, calendar, or phone configuration with another.

Transfers deserve particular care because moving an entire sub-account affects ownership and dependencies.

Finally, do not treat a Snapshot deployment as finished until client-specific details have been tested.

A scalable GHL account structure depends on consistent organization.

Use clear location names.

Decide whether internal test accounts should follow a naming convention.

Identify the Agency Sub-Account clearly.

Use standardized permission profiles.

Create niche-specific Snapshots.

Document which integrations belong in each client account.

Review inactive locations periodically.

These practices become increasingly important as the agency grows.

Client data separation is useful only when permissions are configured responsibly.

Give employees and clients only the access required for their work.

HighLevel's September 2026 permissions system allows agencies to control individual features and modules in much greater detail than older configurations.

Use those controls instead of making every user an administrator.

Review access when employees change roles or leave the company.

A practical sub-account setup should start with business identity and one working customer journey.

Create the location.

Confirm whether it is the agency's own account or a client account.

Set business information and time zone.

Add the appropriate users.

Create the primary pipeline.

Connect the main lead source.

Add the calendar.

Build the first workflow.

Configure phone and email if required.

Connect client-specific integrations.

Run a test lead through the entire process.

Only after that foundation works should more advanced features be added.

A clean agency onboarding process might look like:

Create Client Location → Load Snapshot → Configure Business Details → Add Users → Connect Calendar → Connect Phone/Email → Connect Payment Provider → Test Forms → Test Workflows → Launch

This process can then become an agency SOP.

Repeatability is one of the main advantages of the sub-account architecture.

Optimizing sub-account management means reducing repetitive setup while maintaining clear separation between clients.

Use Snapshots for repeatable systems.

Use Feature Permissions to simplify the client interface.

Use standardized naming.

Give employees only the locations they manage.

Use bulk actions where appropriate.

Review inactive or test accounts.

Document transfer and offboarding procedures.

As the agency grows, account management becomes an operational system of its own.

GoHighLevel Sub Accounts are separate location-level workspaces inside an agency account. They allow different businesses or locations to maintain independent contacts, workflows, calendars, conversations, pipelines, users, and other CRM configuration. HighLevel also distinguishes client sub-accounts from an Agency Sub-Account used for the agency's own business.

Yes. HighLevel currently describes sub-accounts as locations. The term represents an individual operational workspace under the larger agency account.

The limit depends on the HighLevel plan. Starter currently includes three sub-accounts, while Unlimited provides unlimited sub-accounts.

An Agency Sub-Account is a normal HighLevel location designated as the agency's own business workspace rather than a client's account. On supported higher plans it can also participate in SaaS, subscriptions, rebilling, and payment-provider configuration.

Yes. Users can be restricted to specific locations, and sub-account roles can be configured as Admin or User with additional granular permissions.

Yes. HighLevel's Feature Permissions system currently provides more than 80 controllable features that agencies can enable or disable for sub-accounts.

Yes. HighLevel allows an agency to create a new sub-account from a Snapshot so supported assets can be loaded automatically during account creation.

Yes. HighLevel supports eligible whole-sub-account transfers between agencies. The receiving agency must approve the transfer.

No. HighLevel states that the sub-account transfer system does not merge two locations.

Not through the normal sub-account transfer process. HighLevel states that partial transfers are not supported; the eligible location transfers as a whole.

Yes. HighLevel has a Copy Contact workflow action that can copy supported contact data between locations when configured appropriately.

HighLevel provides an in-app tool for eligible numbers under compatible phone configurations. As of September 2026, the documented in-app workflow supports eligible U.S. and Canadian numbers.

Yes. HighLevel supports account-level user/admin access that can be assigned across selected locations without giving the user full Agency View access.

Yes. HighLevel supports bulk transfer requests, with its current documentation allowing up to 1,000 sub-accounts to be selected in a single bulk transfer workflow.

Yes. HighLevel provides an Eject Sub-Account process that can convert an eligible existing location into a separate agency account.

HighLevel currently maintains promotional extended-trial routes in addition to its standard trial offers. The CTA links in this guide use the 30-Day Free Trial promotional path.

GoHighLevel Sub Accounts provide the structural foundation for managing multiple clients, businesses, or locations inside one HighLevel agency account. Each location can maintain its own CRM contacts, conversations, opportunities, workflows, calendars, users, marketing assets, and integrations while remaining accessible from the agency's central management layer.

The most important concept is separation.

Use Go High Level Sub Accounts when businesses need independent customer data, automation, staff, communication, or configuration. Do not place unrelated clients inside one CRM simply to reduce the number of locations.

Agencies should also distinguish client accounts from the newer Agency Sub-Account designation. HighLevel uses the Agency Sub-Account for the agency's own internal workspace and, on supported plans, for certain SaaS and rebilling operations.

As the agency grows, GHL provides increasingly useful management tools. Snapshots can standardize onboarding, Feature Permissions can control what clients see, granular user roles can restrict access, bulk actions can reduce repetitive administration, and whole-location transfers can support client offboarding or agency migration.

A practical scalable model is:

Agency → Standardized Snapshot → Separate Client Sub-Accounts → Controlled User Access → Client-Specific Configuration

Build that structure correctly at the beginning and adding more clients becomes much easier than reorganizing a mixed CRM later.

Create your agency workspace, build a client sub-account, configure permissions, test a Snapshot-based setup, and see how separate locations can support a scalable client-management process.

Start Your GoHighLevel 30-Day Free Trial →