Sub-Accounts in GoHighLevel: Complete Setup, Types & Management Guide
A sub-account in GoHighLevel is a separate, isolated workspace (technically called a “location”) inside your agency’s main account, with its own contacts, pipelines, workflows, funnels, and calendars that don’t mix with any other sub-account. Every client gets one.
On supported plans, you can also designate a sub-account as an Agency Sub-Account, meaning it represents your own agency’s internal operations, SaaS billing, or rebilling setup rather than a client’s business. The distinction matters operationally: Agency Sub-Accounts cannot be transferred to another agency, while ordinary client sub-accounts can be.
Sub-account confusion is one of the most common operational problems agencies run into with GoHighLevel, mostly because the platform gives you two account types that look identical in the interface but behave very differently once SaaS Mode, rebilling, or agency transfers are involved. This guide covers both types clearly, based on HighLevel’s own documentation.
What a Sub-Account Actually Is
Every sub-account functions as a location in HighLevel, a fully separate workspace with its own contacts, pipelines, calendars, funnels, workflows, and custom fields. Nothing is shared between sub-accounts unless you deliberately copy it across, typically via a Snapshot. (See our What Is a GoHighLevel Snapshot guide for how that structural copying works.)
This isolation is the entire point: it’s what lets one agency account manage dozens or hundreds of client businesses without their data, automations, or contacts ever crossing into each other.
A useful distinction: user accounts control who can log in and what they can access; sub-accounts control what data exists. A single sub-account can have multiple users attached to it (your team, the client, a contractor), and a single user can be granted access to multiple sub-accounts, but the underlying data in each sub-account stays completely separate.
Client Sub-Account vs. Agency Sub-Account
This is where most of the confusion starts, since both are technically “just” sub-accounts, but HighLevel treats them very differently once billing and SaaS features are involved.
| Feature | Client Sub-Account | Agency Sub-Account |
|---|---|---|
| Purpose | Managing a client’s business | Managing your own agency’s business or SaaS operations |
| Selected during creation as | “This is my client’s account” | “This is my own account” |
| SaaS plan creation | Uses SaaS products sold to clients | Creates and manages SaaS plans from this account, where supported |
| Rebilling configuration | Reads billing configuration from the linked Agency Sub-Account | Hosts the actual rebilling configuration and payment provider connection |
| Transfer support | Can be transferred between agencies when eligible | Cannot be transferred to another agency, ever |
| Removal behavior | Follows standard sub-account deletion checks | Can only be un-designated after dependent SaaS plans and client links are cleared |
| Visual indicator | No badge | Blue “Agency sub-account” badge |
According to HighLevel’s own documentation, when you create a new sub-account on supported plans, you’re asked to choose an account type: “This is my client’s account” for a client’s business, or “This is my own account” for your agency’s internal workspace, SaaS operations, or rebilling setup. Choosing correctly at creation matters, since an Agency Sub-Account carries permanent restrictions (most notably, it can never be transferred to another agency) that a normal client sub-account doesn’t.
How Agency Sub-Accounts Support SaaS Mode and Rebilling
If your agency runs SaaS Mode, meaning you’re reselling GoHighLevel under your own brand, or rebilling clients through your own payment setup, the Agency Sub-Account becomes the operational hub for that entire structure:
- SaaS products and subscriptions are created and managed from the Payments module inside the selected Agency Sub-Account.
- When a customer purchases a SaaS plan, the subscription is created through that linked Agency Sub-Account.
- Client sub-accounts provisioned through SaaS link back to the Agency Sub-Account that created them.
- The Agency Sub-Account is also where supported payment providers get connected for rebilling, including Stripe, NMI, Authorize.net, Square, Adyen, and Mercado Pago.
Selecting the wrong account as your Agency Sub-Account, for instance accidentally choosing a client’s account instead of your own, can cause SaaS plans, subscriptions, or billing settings to be managed from the wrong place. This is worth double-checking before you connect any payment provider, since it directly affects how your clients get billed. (For the fuller picture of structuring a resold GoHighLevel offer, see our Scale with GHL SaaS Mode guide.)
Which Plans Support Agency Sub-Accounts
Based on HighLevel’s documentation, Agency Sub-Accounts may be available across the Starter, Freelancer, and Pro plan tiers, but feature behavior varies significantly by plan:
- On the entry-level Starter tier, an Agency Sub-Account is mainly used as your agency’s own internal workspace.
- On the Freelancer and Pro tiers, an Agency Sub-Account may additionally support SaaS plans, subscriptions, rebilling, and payment provider configuration.
Because plan names and inclusions change periodically, confirm current tier details on our GoHighLevel Pricing breakdown or GoHighLevel’s official pricing page before making a plan decision based on this feature.
Who can manage Agency Sub-Accounts: Agency Owners, Agency Admins, and Agency Users who have been granted the specific Agency Sub-Account management permission. (See our Managing User Roles & Permissions context for how agency-level access controls work more broadly.)
How to Identify an Agency Sub-Account
Agency Sub-Accounts are visually flagged so you don’t accidentally treat one like a client account (or vice versa):
Checking this badge before making SaaS, rebilling, or account-level changes is a simple habit that prevents a surprising number of billing misconfigurations.
Transfer Restrictions: The Detail That Catches Agencies Off Guard
Agency Sub-Accounts cannot be transferred to another agency, under any circumstances. If you attempt it, HighLevel blocks the action outright and instructs you to manage Agency Sub-Accounts separately from any transfer request. In bulk transfer workflows, Agency Sub-Accounts are listed separately as blocked from transfer.
This becomes relevant in two common scenarios:
Ordinary client sub-accounts don’t carry this restriction; they can be transferred between agencies when eligible, which is the correct tool when a client’s whole live account, contacts and all, needs to move between agencies rather than just its structure. (For that distinction, see our What Is a GoHighLevel Snapshot article, which covers Snapshot vs. Account Transfer directly.)
Removing the Agency Sub-Account Designation
Un-designating an account (turning it back into an ordinary sub-account) can be blocked if it still has active dependencies. Specifically, removal may fail while:
The fix is to de-link SaaS client sub-accounts and remove active SaaS plans or related dependencies first, then attempt the removal again. HighLevel’s documentation is explicit that you should review the impact carefully before doing this, since customers linked to that sub-account may not be able to make payments seamlessly if the billing setup gets disrupted mid-process.
A Practical Setup Order
FAQ
Is an Agency Sub-Account different from a normal sub-account?
It’s still a regular sub-account technically, but it’s designated as your agency’s own account rather than a client’s, which changes how SaaS billing, rebilling, and transfers behave for that specific account.
Can I transfer an Agency Sub-Account to another agency?
No. Agency Sub-Accounts cannot be transferred to another agency under any circumstances; HighLevel blocks the action if attempted.
Why can’t I remove the Agency Sub-Account designation from an account?
Removal is blocked while active SaaS plans, SaaS products, contacts, or linked client sub-accounts still depend on that account. Clear those dependencies first, then try again.
Which GoHighLevel plans support Agency Sub-Accounts?
They may be available across Starter, Freelancer, and Pro plan tiers, though SaaS and rebilling capabilities are generally stronger on the higher tiers. Confirm current plan inclusions before deciding, since tiers are updated periodically.
Who is allowed to manage Agency Sub-Accounts on a team?
Agency Owners, Agency Admins, and Agency Users specifically granted the Agency Sub-Account management permission.
Getting your Agency Sub-Account and client sub-account structure right from day one avoids a painful billing untangling process later. Our CRM Architecture Setup service sets up your sub-account structure, SaaS billing hub, and permissions correctly the first time.
