GoHighLevel Sub-Accounts are separate business workspaces created underneath a HighLevel agency account, allowing agencies, consultants, and multi-location businesses to keep each client's contacts, pipelines, workflows, calendars, funnels, conversations, users, and other operational data organized independently.

Sub-accounts are one of the most important structural features in GoHighLevel.

Without them, an agency managing twenty clients would need to keep multiple businesses inside one shared CRM environment or maintain separate HighLevel subscriptions.

Neither approach scales particularly well.

Sub-accounts solve this problem by giving each business its own operating workspace while allowing the agency to manage those workspaces from the broader agency environment.

For example, an agency could maintain:

Sub-Account 1 — Dental Practice A

Sub-Account 2 — Roofing Company B

Sub-Account 3 — Med Spa C

Sub-Account 4 — Real Estate Team D

Each account can have its own contacts, sales pipelines, forms, calendars, websites, workflows, AI agents, communication configuration, reporting, and users.

The agency can manage these client environments while preventing ordinary sub-account users from seeing unrelated agency-level settings or other client workspaces.

This architecture is one of the main reasons GoHighLevel works especially well for agencies.

Current HighLevel pricing reinforces that distinction.

The $97 Starter Plan includes three sub-accounts, while the $297 Unlimited Plan and $497 Agency Pro Plan include unlimited sub-accounts. All three core plans currently include unlimited contacts and unlimited users at the platform-plan level.

Sub-accounts also connect with several of HighLevel's most important agency tools.

Snapshots can copy reusable configurations between accounts.

Feature Permissions can control which software modules clients can access.

User roles determine what individual users can see and manage.

SaaS Mode can automate sub-account creation for software customers on Agency Pro.

And HighLevel now supports transferring complete sub-accounts between agencies when account ownership or provider relationships change.

This guide explains how GoHighLevel Sub-Accounts work, what each account contains, how many accounts each GHL plan supports, how agencies should use permissions and snapshots, and how sub-accounts fit into white-label and SaaS business models.

Start Your GoHighLevel 30-Day Trial →

What Are GoHighLevel Sub-Accounts?

GoHighLevel Sub-Accounts are individual business workspaces that exist underneath an agency account.

HighLevel often also uses the term location in parts of its documentation and interface.

Each sub-account represents a specific business, client, branch, brand, or operational location.

A marketing agency might create one account for each client.

A multi-location dental organization might create one account for each clinic.

A consultant could use separate accounts for unrelated businesses.

The important principle is separation.

Client A's contact database does not need to be mixed with Client B's contacts.

Client A's sales pipeline can follow a completely different structure.

Client B can use different calendars, workflows, forms, and users.

This makes account management much cleaner.

How Go High Level Sub-Accounts Fit Under an Agency Account

Go High Level Sub-Accounts operate underneath the agency layer.

The agency layer handles broader administration.

Depending on plan and permissions, agency-level functionality can include areas such as:

• Sub-account creation
• Snapshot management
• Agency billing
• White-label settings
• Agency integrations
• SaaS configuration
• Rebilling
• User management
• Agency-level permissions

Inside a sub-account, users focus on that particular business.

HighLevel's current permissions documentation distinguishes agency-only functionality from sub-account functionality. For example, creating or deleting sub-accounts, managing SaaS Mode, snapshot management, and agency branding sit at agency level, while pipelines, workflows, calendars, conversations, contacts, reputation management, and funnel building operate within sub-accounts.

GHL Sub-Accounts vs Agency Account

Understanding the difference between the GHL agency account and a sub-account prevents a lot of confusion.

The agency account is the management layer.

The sub-account is the business-operation layer.

A useful simplified structure is:

Agency Account

→ Client Sub-Account A

→ Client Sub-Account B

→ Client Sub-Account C

→ Client Sub-Account D

The agency can move between the environments according to its permissions.

Client users generally work only within the business environments to which they have been granted access.

GoHighLevel Agency-Level Functions

Agency-level functions typically concern administration across accounts.

Examples include:

• Creating sub-accounts
• Deleting sub-accounts
• Moving accounts
• Managing snapshots
• Configuring white-label settings
• Managing SaaS plans
• Managing agency billing
• Managing agency users

These controls should generally remain restricted to appropriate agency staff.

Go High Level Sub-Account Functions

Within an individual location, users can work with operational tools such as:

• Contacts
• Opportunities
• Pipelines
• Calendars
• Workflows
• Campaigns
• Conversations
• Reputation
• Funnels
• Websites
• Reporting

This separation helps protect both client data and agency administration.

How Many GHL Sub-Accounts Does Each Plan Include?

The number of GHL Sub-Accounts available depends on the core agency plan.

Current official pricing is:

HighLevel currently describes Starter as being suitable for smaller businesses and solo marketers, Unlimited as being built for growing agencies, and Agency Pro as the SaaS-focused tier.

GoHighLevel Starter Sub-Accounts

The $97 Starter Plan currently includes:

3 Sub-Accounts

It also includes unlimited contacts and unlimited users.

This can be enough for:

• One company
• A freelancer
• A consultant
• A very small agency
• A business with a few locations

For example:

Account 1: Your own business

Account 2: Client A

Account 3: Client B

Once another independent account is required, the Starter allowance has been reached.

Go High Level Unlimited Sub-Accounts

The $297 Unlimited Plan currently includes:

Unlimited Sub-Accounts

It also adds:

• Phone and email rebilling without markup
• Basic API Access

according to HighLevel's official pricing.

This changes the economics for agencies significantly.

An agency can add more client accounts without upgrading simply because it added another location.

Variable communication, AI, and optional-product costs may still increase, but the number of sub-accounts is no longer the core limitation.

GHL Agency Pro Sub-Accounts

Agency Pro currently costs:

$497/month

and inherits Unlimited's unlimited sub-account capacity.

It then adds:

• SaaS Mode
• Automated Sub-Account Creation
• Phone and Email Rebilling with Markup
• User/Agent Reporting
• Advanced API Access.

The distinction is therefore:

Unlimited → manually scale client management

Agency Pro → automate more of the SaaS customer lifecycle

GoHighLevel Sub-Account CRM

Every GoHighLevel Sub-Account can maintain its own CRM data.

This can include:

• Contacts
• Tags
• Custom fields
• Notes
• Tasks
• Opportunities
• Customer history

A roofing company's lead records can remain separate from a dental client's patients or prospects.

This separation is critical for agencies.

Mixing unrelated client contacts inside one shared CRM would create major operational and privacy problems.

Go High Level Contact Management by Client

Each client can organize contacts according to their own business needs.

For example:

A roofing business might use custom fields for:

• Property address
• Roof type
• Insurance status

A dental clinic might instead track:

• Requested treatment
• Appointment information
• Lead source

The agency does not need one universal data structure for every client.

GHL Pipelines and Opportunities by Sub-Account

Each GHL Sub-Account can maintain its own sales pipelines and opportunity structure.

For example, a roofing pipeline might use:

New Lead → Inspection → Estimate → Approved → Scheduled → Won

A marketing agency client might use:

New Inquiry → Discovery Call → Proposal → Negotiation → Won

The two systems are unrelated even though both exist underneath the same parent agency.

This gives agencies the flexibility to customize sales processes around each business.

GoHighLevel Workflows by Sub-Account

GoHighLevel workflows are also configured within individual client environments.

One client might use:

Form Submitted → SMS → Email → Create Opportunity

Another might use:

Appointment Booked → Confirmation → Reminder → Follow-Up

Workflows do not need to be identical across every client.

However, agencies can use snapshots when the same automation needs to be repeated.

This creates a useful balance:

Account isolation + reusable agency systems

Explore GoHighLevel for Your Agency →

Go High Level Calendars by Sub-Account

Calendars operate around the individual business.

Each client can configure its own:

• Availability
• Staff
• Services
• Booking pages
• Appointment settings
• Reminder automation

A med spa's appointment calendar does not affect a roofing company's inspection availability.

That seems obvious, but this account-level separation becomes essential when one agency manages dozens of very different businesses.

GHL Funnels and Websites by Client

A GHL Sub-Account can also maintain its own funnels and website assets.

This allows agencies to build client-specific:

• Landing pages
• Sales pages
• Websites
• Forms
• Booking pages

Domains and publishing settings can be configured according to the individual business.

This is important when an agency provides website or lead-generation services alongside CRM management.

GoHighLevel Conversations by Sub-Account

Customer conversations remain connected with the relevant business workspace.

This means employees working inside one client environment can focus on that business's communications rather than seeing unrelated conversations from other agency customers.

The account structure helps keep customer communication organized alongside:

• Contact records
• Opportunities
• Appointments
• Automation

Go High Level Reputation Management by Client

Reputation management can also be configured separately.

One client may connect one Google Business Profile.

Another client may have several location-specific profiles.

Review requests, reputation workflows, and client feedback remain associated with the relevant business environment.

For agencies selling reputation management, this makes each client's reputation operation easier to maintain independently.

GHL AI Configuration by Sub-Account

Many current HighLevel AI products are configured at the location or sub-account level.

For example, a business may need its own:

• Knowledge sources
• Conversation AI settings
• Voice AI agent
• Reviews AI configuration
• AI Employee subscription

This separation is important.

A dental office's AI should not answer using a roofing company's services or FAQs.

Each location needs relevant business knowledge and configuration.

AI pricing may also be applied per enabled location, depending on the product and AI plan.

GoHighLevel Users Inside Sub-Accounts

GoHighLevel Sub-Accounts can have their own users.

A client may need access for:

• Owner
• Sales manager
• Sales representative
• Receptionist
• Marketing employee

The agency can configure which people have access and what those users are allowed to see.

Current HighLevel documentation defines two main sub-account roles:

Admin

and:

User

These can be refined further with granular feature and data permissions.

Go High Level Admin vs User Roles

An Admin generally receives broader control inside the account.

A User can be restricted more heavily.

For example, a salesperson might only need:

• Conversations
• Contacts
• Opportunities

They may not need:

• Workflow editing
• Website editing
• Billing settings
• AI configuration

The permission system helps the agency avoid giving unnecessary access.

GHL Only Assigned Data Permissions

HighLevel also supports Only Assigned Data controls.

This can help organizations restrict users so they only see records relevant to them.

For example, one salesperson may need to see only the leads assigned to them rather than the entire company's sales database.

This becomes useful for larger client organizations where internal teams require different levels of visibility.

GoHighLevel Feature Permissions for Sub-Accounts

One of the more important 2026 improvements is HighLevel's updated Feature Permissions system.

Agencies can now control access to 80+ features within individual sub-accounts or SaaS plans.

This means an agency does not need to expose every available HighLevel module to every customer.

One client could receive:

• Calendars
• Opportunities
• Conversations
• Phone System

Another might additionally receive:

• AI Agents
• Funnels
• Workflows
• Reputation

This creates a cleaner product experience.

Go High Level Feature Permissions for SaaS Plans

Feature Permissions can also be incorporated into SaaS plans.

That makes it possible to create tiered software packages.

For example:

Basic

• CRM
• Pipeline
• Calendar

Growth

• Everything in Basic
• Workflows
• Reputation
• Funnels

Premium

• Everything in Growth
• AI tools
• Additional modules

HighLevel's current feature-permission system allows agencies to control these capabilities rather than showing the same software environment to every SaaS customer.

GHL User Limits for SaaS Sub-Accounts

SaaS agencies can also configure user limits.

HighLevel's SaaS Mode allows agencies to define how many sub-account users a particular SaaS plan supports.

By default, the user allowance can remain unlimited, or an agency can enable a specific cap.

A sub-account-specific limit can also override the broader SaaS-plan setting.

This creates another product-packaging option.

For example:

Basic — 3 users

Growth — 10 users

Premium — unlimited users

The exact commercial structure is up to the agency.

GoHighLevel Snapshots for Sub-Accounts

GoHighLevel Snapshots are one of the most important tools for scaling multiple sub-accounts.

A snapshot is a reusable package created from an existing sub-account configuration.

Current HighLevel documentation says snapshots can capture assets such as:

• Workflows
• Funnels
• Calendars
• Forms
• Emails
• Triggers
• Custom fields
• Custom values
• Membership content
• Services
• AI Studio projects
• Other supported configuration assets.

This means an agency does not need to rebuild a proven system from scratch for every new customer.

How Go High Level Snapshots Work

The process generally looks like:

1. Build a well-configured source sub-account.
2. Create a snapshot from that location.
3. Select the assets to include.
4. Save the snapshot.
5. Load it into new or existing sub-accounts.

HighLevel specifically notes that you do not create a snapshot from a blank template.

You first create the working configuration inside a source sub-account and then capture it.

GHL Snapshot Example for an Agency

Imagine an agency specializes in dentists.

It creates a model account containing:

• New-patient pipeline
• Lead nurture workflow
• Appointment reminders
• No-show follow-up
• Review requests
• Forms
• Calendars
• Email templates

The agency can create a snapshot from that setup.

When another dental client signs, the agency can load the reusable configuration rather than building everything manually again.

This improves both speed and consistency.

GoHighLevel Create a Sub-Account From a Snapshot

HighLevel now allows agencies to create a new sub-account directly from a snapshot.

During creation, the snapshot assets are automatically loaded into the new workspace.

This reduces the number of onboarding steps.

HighLevel notes that only users with appropriate Agency Admin access can create sub-accounts using this method.

Go High Level Snapshot Assets vs Client Data

Snapshots should not be confused with full client backups.

HighLevel explicitly states that several live-data categories are not captured as reusable snapshot configuration.

Examples include:

• Contacts
• Appointments
• Conversations
• Reputation data
• Stripe connections
• Certain integrations.

Snapshots are primarily designed to duplicate configuration.

They are not intended to clone one client's live customer database into another account.

GHL Load Snapshots Into Existing Sub-Accounts

Snapshots can also be loaded into accounts that already exist.

HighLevel currently allows agencies to select the assets they want to import and manage potential conflicts with existing configurations.

This can be useful when an agency develops a new standardized workflow and wants to deploy it to established clients.

For example:

New review workflow developed

→ Load into existing client accounts

→ Customize client-specific values

→ Test

→ Publish

GoHighLevel Load a Snapshot to Multiple Sub-Accounts

A newer HighLevel capability allows agencies to load or link a snapshot across multiple sub-accounts from one centralized workflow.

The agency can open its account snapshots, select an existing snapshot, and choose multiple available locations rather than opening each client account individually.

This is especially valuable for agencies managing large portfolios.

Suppose an agency needs to deploy a revised intake workflow across:

50 client accounts.

Opening and configuring all fifty individually is inefficient.

Centralized multi-account snapshot deployment reduces that repetitive work.

Go High Level Snapshots and Standardization

Snapshots can create significant operational leverage.

Without standardization:

New Client → Build Everything Again

With a well-developed snapshot library:

New Client → Select Niche Snapshot → Deploy → Customize

The agency can maintain snapshots for different industries.

For example:

• Dental
• Roofing
• HVAC
• Med spa
• Real estate
• Legal services

Each can contain a different baseline system.

GHL Snapshots Still Need Client Customization

A snapshot should not be treated as a completely finished client account.

After loading, the agency may still need to configure:

• Business name
• Domains
• Phone numbers
• Email services
• Calendars
• Users
• Branding
• Integrations
• Payment providers
• AI knowledge
• Workflow details

The snapshot accelerates repetitive setup.

It does not eliminate onboarding.

GoHighLevel Sub-Accounts and White Label

GoHighLevel Sub-Accounts can operate within the agency's supported white-label environment.

Unlimited and Agency Pro provide broader agency branding capabilities than Starter, including HighLevel's branded desktop experience and custom-domain options.

This can allow clients to interact with HighLevel through an agency-branded experience.

For example:

app.youragency.com

The agency may also configure supported logos, company information, and related branding.

Go High Level White Label Limitations

White labeling should not be interpreted as guaranteeing that every external technology provider or technical dependency disappears in every context.

Third-party services can still have their own identities.

App stores have their own requirements.

Payment providers operate independently.

External integrations may show their own brands.

A more accurate description is:

HighLevel lets agencies white-label supported customer-facing portions of the platform.

GHL Sub-Accounts and SaaS Mode

GHL Sub-Accounts are the basic customer unit behind HighLevel's SaaS Mode.

Agency Pro currently includes:

• SaaS Mode
• Automated Sub-Account Creation
• Rebilling with markup
• Advanced API Access.

Instead of manually creating a new location every time a software customer joins, SaaS Mode can automate more of the process.

A simplified SaaS journey becomes:

Choose Plan → Pay → Sub-Account Created → Configuration Applied → User Onboarding

This makes sub-account creation part of the product-purchase experience.

GoHighLevel Automated Sub-Account Creation

Automated sub-account creation becomes increasingly valuable as customer volume grows.

Imagine onboarding:

2 customers per month.

Manual account creation is manageable.

Now imagine:

100 customers per month.

Manual provisioning becomes a significant operational burden.

Agency Pro's automated sub-account creation is designed for this higher-volume SaaS model.

Go High Level Sub-Accounts and SaaS Packaging

Each SaaS sub-account can represent a paying software customer.

An agency may offer plans such as:

Starter Software

CRM + Pipeline + Calendar

Growth Software

CRM + Workflows + Reputation + Funnels

Premium Software

Broader feature access + AI + additional agency services

Feature Permissions and SaaS user limits can help control what each account receives.

This creates a much more structured SaaS offer than simply selling every customer unrestricted access.

GHL Sub-Accounts and Client Billing

Sub-accounts also matter for agency billing because many usage-based services occur at location level.

Examples can include:

• Phone
• SMS
• Email
• AI
• Optional services

The agency needs to understand which location generated which usage.

This becomes especially important when rebilling is enabled.

Current HighLevel pricing distinguishes between:

Unlimited — Rebill Phone & Email without markup

and:

Agency Pro — Rebill Phone & Email with markup.

GoHighLevel Agency Sub-Account

HighLevel also documents a concept called the Agency Sub-Account.

This is generally the agency's own location/workspace rather than a client location.

Current documentation explains that the Agency Sub-Account may be used differently depending on plan and can participate in areas such as SaaS, subscriptions, rebilling, and payment-provider configuration where supported.

The distinction is useful:

Agency View → manages the agency and clients

Agency Sub-Account → operates like the agency's own business location

Client Sub-Accounts → client business workspaces

GHL Sub-Account User Permissions

Permissions deserve special attention because agencies should not simply grant every client user Admin-level access.

Current HighLevel sub-account permissions include granular control over modules such as:

• Voice AI
• Calendars
• Workflows
• Opportunities
• Contacts
• Conversations
• Other account tools.

A good permission strategy uses the principle:

Give users the access they need, but not unnecessary administration rights.

GoHighLevel Permission Example

A receptionist might need:

• Conversations
• Contacts
• Calendars

A salesperson might need:

• Contacts
• Opportunities
• Conversations

A marketing manager might need:

• Workflows
• Funnels
• Forms
• Reporting

A business owner may receive broader Admin access.

The correct permissions depend on the organization.

Go High Level Agency User Access Across Multiple Sub-Accounts

Agency team members can also have access to the client accounts they are responsible for.

For example:

Account Manager A

→ Client 1

→ Client 2

→ Client 3

Account Manager B

→ Client 4

→ Client 5

This is much cleaner than sharing master credentials across the entire agency.

Role-based access also reduces the risk that employees accidentally modify unrelated client environments.

GHL Sub-Account Security Best Practices

Agencies managing many client accounts should treat account permissions seriously.

Good practices include:

• Avoid shared logins.
• Give each team member their own user.
• Restrict unnecessary permissions.
• Remove access when staff leave.
• Review Admin users periodically.
• Restrict sensitive billing controls.
• Keep client users inside their intended account scope.

The objective is to reduce unnecessary access while preserving efficient operations.

GoHighLevel Sub-Account Transfers

HighLevel currently supports transferring a complete sub-account from one HighLevel agency to another.

A transfer moves the account rather than merging it with another location.

HighLevel states that contacts, conversations, supported assets, and account history remain together with the transferred sub-account.

This can be useful when:

• A client changes agencies.
• A business wants direct ownership under another agency structure.
• Agencies restructure accounts.
• Ownership arrangements change.

Go High Level Transfer Permissions

Current documentation states that sub-account transfers can be initiated by:

• Agency Owner
• Agency Admins specifically granted transfer permission.

This restriction helps protect client data from unauthorized moves.

GHL Bulk Sub-Account Transfers

HighLevel also supports bulk transfers between agencies.

Its current tool can process multiple sub-accounts as part of one transfer workflow, with documentation noting that up to 1,000 sub-accounts can be selected at a time for the supported bulk-transfer process.

This is primarily useful to large agencies undergoing structural changes or portfolio transfers.

GoHighLevel Sub-Accounts for Multi-Location Businesses

Sub-accounts are not useful only for marketing agencies.

A multi-location business may also benefit from separate workspaces.

Imagine a dental organization with:

• Austin clinic
• Dallas clinic
• Houston clinic

Each location may need its own:

• Contacts
• Staff
• Calendar
• Phone number
• Pipeline
• Reviews
• Reporting

Separate locations can keep operations organized while still being managed under a broader account structure.

Go High Level Sub-Accounts for Franchises

Franchise organizations can use a similar model.

Each franchise location may have unique:

• Users
• Leads
• Reviews
• Appointment availability
• Marketing activity

At the same time, the organization may want standardized workflows and funnels.

Snapshots can help distribute the standardized infrastructure while sub-accounts preserve local operational separation.

GHL Sub-Accounts for Marketing Agencies

Marketing agencies remain the strongest use case.

An agency can build a standardized service around:

• CRM
• Lead capture
• Funnels
• Appointment scheduling
• Follow-up
• Reputation management
• AI

and deploy the system across separate client workspaces.

Instead of purchasing a separate CRM subscription for each customer, higher HighLevel agency plans support unlimited sub-accounts at the core-plan level.

For independent resources covering GoHighLevel CRM, sub-accounts, snapshots, pricing, AI, workflows, SaaS Mode, and agency operations, visit GHLCRM.US.

GoHighLevel Sub-Account Cost

A sub-account does not currently have a separate base account fee on Unlimited simply because another location is created.

Current pricing is:

Starter — $97/month → 3 sub-accounts

Unlimited — $297/month → unlimited sub-accounts

Agency Pro — $497/month → unlimited sub-accounts.

However, this does not mean each additional sub-account is free to operate.

Locations can still create additional costs through:

• Communication usage
• AI subscriptions
• WhatsApp
• SEO
• Premium features
• Domains
• Other optional products

The distinction is:

No additional core Unlimited subscription fee for each account

does not mean:

No additional operating cost per client.

Go High Level Sub-Account Economics for Agencies

Consider an Unlimited agency paying:

$297/month

with 10 clients.

Base-plan allocation:

$297 ÷ 10 = $29.70 per client

With 30 clients:

$297 ÷ 30 = $9.90 per client

With 100 clients:

$297 ÷ 100 = $2.97 per client

These examples divide only the base Unlimited subscription.

They do not include:

• Phone
• SMS
• Email
• AI
• Labor
• Support
• Payment processing
• Add-ons

Nevertheless, the calculation illustrates why unlimited sub-accounts can create favorable economics for a growing agency.

GHL Sub-Account Management Best Practices

Use Clear GoHighLevel Naming Conventions

Create a consistent account-naming system.

For example:

Client Name — City

or:

Brand — Location

This makes a large account list easier to manage.

Standardize Go High Level Onboarding

Use an onboarding checklist covering:

• Business details
• Users
• Domains
• Calendars
• Phone
• Email
• Integrations
• Workflows
• Reporting

Use GHL Snapshots for Repeatable Systems

Avoid rebuilding standard configurations manually.

Review GoHighLevel User Permissions

Do not give every person unrestricted Admin access.

Use Go High Level Feature Permissions

Hide tools the client does not need.

A simpler interface can reduce confusion.

Track GHL Usage by Sub-Account

Monitor clients whose communication or AI usage could affect agency margins.

Keep GoHighLevel Client Data Separated

Do not intentionally combine unrelated client records inside one location merely to avoid upgrading plans.

Start Your GoHighLevel 30-Day Trial →

Common GoHighLevel Sub-Account Mistakes

Using One GHL Sub-Account for Several Unrelated Clients

This makes CRM data, permissions, reporting, and automation much harder to manage safely.

Giving Every Go High Level User Admin Rights

Most users only need access to specific tools.

Building Every GoHighLevel Account From Scratch

Snapshots can reduce repeated setup work significantly.

Ignoring GHL Feature Permissions

Showing every possible HighLevel module can overwhelm clients who only use a few tools.

Assuming Go High Level Snapshots Copy Everything

Snapshots copy reusable configurations, not every category of live client data.

Assuming Unlimited GHL Sub-Accounts Mean Unlimited Free Usage

Communication, AI, and add-ons can still generate costs.

GoHighLevel Sub-Accounts vs Separate HighLevel Accounts

An agency could theoretically maintain completely independent HighLevel agency subscriptions for different clients.

That would create unnecessary complexity in many situations.

The agency would have:

• Multiple logins
• Multiple subscriptions
• Separate agency settings
• Separate snapshot libraries
• More billing complexity

Sub-accounts provide a cleaner structure.

The agency maintains one agency environment while client operations remain separated underneath it.

GHL Sub-Accounts vs Users

A sub-account and a user are not the same thing.

Sub-Account = business workspace

User = person with access

One sub-account can contain multiple users.

One agency user may also have access to multiple sub-accounts, depending on permissions.

This distinction becomes especially important when comparing HighLevel plans.

Starter can have unlimited users while still being limited to three sub-accounts.

GoHighLevel Sub-Accounts vs Snapshots

A sub-account is an active workspace.

A snapshot is a reusable configuration template.

They serve different purposes.

Sub-Account

Contains live business operations.

Snapshot

Copies selected configuration assets so they can be deployed elsewhere.

An agency typically builds a well-configured sub-account first and then creates a snapshot from it.

Go High Level Sub-Accounts vs SaaS Plans

A sub-account is the underlying workspace.

A SaaS plan is the commercial package an Agency Pro customer can sell.

The SaaS plan can define what a customer's sub-account should receive.

Feature Permissions and user limits can further refine those packages.

This distinction matters because one technology layer supports the other:

SaaS Plan → Provisions Sub-Account → Customer Uses Software

Frequently Asked Questions About GoHighLevel Sub-Accounts

What Are GoHighLevel Sub-Accounts?

GoHighLevel Sub-Accounts are independent business workspaces created beneath an agency account. Each can maintain its own CRM, pipelines, workflows, calendars, funnels, users, conversations, and other business configuration.

How Many Go High Level Sub-Accounts Does Starter Include?

The current Starter Plan includes 3 sub-accounts.

Does GHL Unlimited Include Unlimited Sub-Accounts?

Yes. The current $297 Unlimited Plan includes unlimited sub-accounts.

Does GoHighLevel Agency Pro Include Unlimited Sub-Accounts?

Yes. Agency Pro includes everything in Unlimited and therefore includes unlimited sub-accounts.

Are Go High Level Contacts Shared Between Sub-Accounts?

Separate client sub-accounts are intended to maintain their own business records and account environments rather than functioning as one shared customer database.

Can GHL Sub-Accounts Have Different Users?

Yes. Sub-account users can have Admin or User roles with additional granular permissions.

Can GoHighLevel Restrict Features in a Sub-Account?

Yes. HighLevel's current Feature Permissions system provides control over more than 80 features and can be applied to individual sub-accounts or SaaS plans.

Can Go High Level Limit Users in SaaS Sub-Accounts?

Yes. SaaS plans can define user limits, and specific sub-account limits can override the general plan configuration.

What Is a GHL Snapshot?

A snapshot is a reusable template created from a configured sub-account. It can include supported assets such as workflows, funnels, calendars, forms, emails, custom fields, and other configuration items.

Can GoHighLevel Create a Sub-Account From a Snapshot?

Yes. HighLevel can create a new sub-account and apply a selected snapshot during the creation process.

Can Go High Level Load a Snapshot Into Several Sub-Accounts?

Yes. HighLevel's updated snapshot workflow can select and load a snapshot across multiple sub-accounts from a centralized interface.

Do GHL Snapshots Include Contacts?

No. Current HighLevel documentation says snapshots are designed primarily for reusable configuration and do not include live contact records, appointments, conversations, reputation data, Stripe connections, or certain integrations.

Can a GoHighLevel Sub-Account Be Transferred to Another Agency?

Yes. HighLevel currently supports transferring an entire sub-account between eligible agencies. Supported account records and history remain with the location during the transfer.

Can Go High Level Transfer Several Sub-Accounts at Once?

Yes. HighLevel supports bulk location transfers, with current documentation allowing up to 1,000 sub-accounts to be selected in a supported bulk-transfer operation.

Does GHL SaaS Mode Create Sub-Accounts Automatically?

Yes. Automated Sub-Account Creation is currently an Agency Pro feature.

Are GoHighLevel Sub-Accounts Free?

Unlimited and Agency Pro currently allow unlimited sub-accounts without an additional base platform subscription charge for each location. However, individual sub-accounts can still generate communication, AI, add-on, and other usage costs.

Who Should Use Go High Level Sub-Accounts?

Sub-accounts are especially useful for marketing agencies, consultants managing multiple clients, franchises, and multi-location organizations that need independent CRM environments under one broader HighLevel account.

Final Thoughts on GoHighLevel Sub-Accounts

GoHighLevel Sub-Accounts are one of the structural features that separate HighLevel from a basic single-business CRM.

The agency layer provides centralized management.

Sub-accounts provide separation.

That combination makes it possible to manage many different businesses without combining their operational data into one workspace.

Each client can have its own CRM.

Its own pipeline.

Its own workflows.

Its own calendars.

Its own funnels and websites.

Its own users.

Its own AI configuration.

And its own business processes.

At the same time, the agency can maintain standardization through snapshots, user permissions, feature controls, and reusable systems.

The current HighLevel plan structure reflects this model clearly.

Starter — $97/month

supports three sub-accounts.

That can be enough for a single business, freelancer, consultant, or very small agency.

Unlimited — $297/month

removes the sub-account ceiling.

This makes it much more appropriate for a growing agency with many clients.

Agency Pro — $497/month

keeps unlimited sub-accounts and adds SaaS Mode, automated provisioning, markup-based rebilling, and Advanced API Access.

But sub-account count is only one part of the system.

HighLevel's current permission tools give agencies much more granular control over what users and clients can access.

Sub-account roles can limit user capabilities.

Only Assigned Data can restrict visibility.

The newer Feature Permissions system can control more than 80 HighLevel features.

SaaS user limits can help agencies package different subscription levels.

Snapshots add another layer of scalability.

Instead of rebuilding workflows, funnels, forms, calendars, and other assets for every client, an agency can capture a proven configuration and reuse it across new or existing accounts.

HighLevel's newer multi-account snapshot workflow makes that model even more scalable by allowing agencies to distribute configurations across several sub-accounts from one central process.

Sub-accounts can even move between agencies when necessary.

HighLevel's current transfer tools preserve supported account history and data, and bulk transfers are available for larger account portfolios.

For marketing agencies, this means GHL Sub-Accounts are much more than folders used to organize clients.

They are the basic infrastructure around which client operations, white-label services, automation templates, usage billing, and SaaS products can be built.

For multi-location businesses and franchises, they provide a similar advantage by combining centralized administration with location-level separation.

The strongest way to use Go High Level Sub-Accounts is therefore to combine three principles:

Separate client operations.

Standardize repeatable systems.

Restrict access appropriately.

When those principles are followed, an agency can add new customers without turning its CRM environment into an unmanageable collection of mixed data, duplicated setup work, and excessive user access.

That is ultimately why sub-accounts are such an important part of GoHighLevel's agency architecture.

GHLCRM.US is an independent informational resource and is not the official HighLevel website. Sub-account limits, permissions, snapshot functionality, SaaS capabilities, transfer rules, usage costs, and plan pricing may change. Verify current HighLevel documentation and account settings before configuring client systems.