What does a GoHighLevel sub-account separate?
Each client gets its own contacts, pipelines and wallet inside your agency account. Billing, access and the exit stay with the agency.
The short answer
- A GoHighLevel sub-account is a client account managed within an agency's HighLevel account, with its own contacts, pipelines, workflows, phone numbers and usage settings.
- GoHighLevel sub-accounts keep one client's day-to-day work apart from another's, but the agency account stays the owner: agency admins can log in, and the agency keeps or deletes the sub-account when a client leaves.
- Starter includes 3 sub-accounts and the $297 and $497 plans include unlimited sub-accounts, per gohighlevel.com/pricing as of September 2026.
- SalesCrew separates clients at the database level instead: every client instance is its own Supabase project, with a full export on request.
A sub-account separates the work, not the ownership
Picture one agency account with a folder per client. Inside each folder the client's contacts, conversations, pipelines and automations live on their own. Your dentist client never sees your roofer client's leads, and a workflow built for one doesn't fire for the other.
The folder still sits in your account, though. HighLevel describes sub-accounts as client accounts managed within the agency's HighLevel account. You set the services and prices per sub-account, and usage bills through the agency wallet, which recharges the agency's card when the balance drops below a threshold.
That's why agencies and clients read the word differently. To you, a sub-account is tidy separation. To a client who asks "whose data is this?", the honest answer is that it lives inside the agency's platform account.
What a GoHighLevel sub-account keeps apart, and what stays with the agency
From gohighlevel.com/pricing and HighLevel's help centre.
| Area | Per sub-account | Held at agency level |
|---|---|---|
| Contacts, conversations, pipelines | Yes, one set per client | Agency admins can open the sub-account |
| Workflows and automations | Yes, built per client | Set back to draft when a sub-account is paused |
| Usage billing (phone, email, AI) | Charges tracked per client | Paid from the agency wallet; rebilling by plan |
| Sub-account count | n/a | 3 on Starter ($97); unlimited on $297 and $497 |
| What happens when the client leaves | n/a | The agency keeps or deletes the sub-account |
GoHighLevel plans and behaviour checked on gohighlevel.com/pricing and help.gohighlevel.com, September 2026.
When sub-account separation is enough, and when clients ask for more
For most small clients, a sub-account does the job. They want their leads answered and a report each month. They don't ask where the rows are stored.
The question changes when a client wants to own the system. A client who plans to bring sales in-house, sell the business, or pass a vendor review will ask for their data as a whole. With a sub-account, that means an export the agency runs, because the records sit in the agency's account. Our page on what happens to client data when they leave GoHighLevel lists the exports to run first.
Billing is the other pressure point. Every sub-account's usage runs through your agency wallet, so a client who sends heavy SMS volume draws on your card first. See how GoHighLevel wallet and usage fees work before you promise a flat fee.
How SalesCrew keeps each client in its own database
SalesCrew gives every client its own instance. Each instance is a separate Supabase project, with its own Postgres database, storage and edge functions. Your clients don't share tables with each other, and they don't share one with you.
You still run the work. Row-level security and a scope model with 3 axes (channel, profile and area) decide who sees what, and the same rules apply to people and to MCP tokens. When a client leaves, they get a full Postgres dump plus CSV exports. The instance turns read-only and is deprovisioned 90 days later, when a person triggers it.
Pricing is per instance with unlimited seats: Core is $299 a month, and the Agency tier is $1,200. For the full picture, read how to keep client data separate.
Put data ownership in the contract, not the pitch
Questions
- How many sub-accounts do you get on GoHighLevel?
- Starter at $97 a month includes 3 sub-accounts, per gohighlevel.com/pricing as of September 2026. Unlimited at $297 and Agency Pro at $497 include unlimited sub-accounts. Enterprise sets the number in a custom contract.
- Can the agency see a client's data in a GoHighLevel sub-account?
- Yes. A sub-account is a client account managed within the agency's HighLevel account, so agency admins can open it. HighLevel's help centre notes agency admins can still log in to a paused sub-account. Tell your client that plainly in the contract.
- Who owns a GoHighLevel sub-account when the client leaves?
- The agency decides what happens to it. HighLevel's SaaS cancellation guide, checked September 2026, has the agency either keep the sub-account and remove the client's user, or delete it. Transaction and wallet history goes once SaaS Mode is switched off, so export it first.
- Is a SalesCrew client instance the same thing as a sub-account?
- No. A SalesCrew client instance is its own Supabase project with its own Postgres database, storage and edge functions. Access runs through row-level security and a 3-axis scope model, and the client can take a full Postgres dump plus CSV exports at any time.