GoHighLevel Sub-Accounts — The Complete Agency Guide (2026)

Agency Account vs Sub-Account — The Mental Model

Think of your GoHighLevel agency account as an apartment building you own, and sub-accounts as the units. Each unit is fully self-contained — its own contacts, pipelines, automations, calendars, phone numbers, and users — and tenants (clients) never see each other or the building's plumbing. From the agency view, you can enter any unit, replicate a fully-furnished model unit in minutes (snapshots), and charge rent above your costs (rebilling and SaaS mode).

• $97 Starter plan: up to 3 sub-accounts — fine for testing or a business running its own account.
• $297 Unlimited plan: unlimited sub-accounts + API access — the real agency plan.
• $497 SaaS Pro: adds SaaS mode — self-serve signup, automated rebilling with markup, and plan tiers you define.

Creating a Sub-Account the Right Way

From the agency dashboard: Sub-Accounts → Create Sub-Account. You'll choose a blank account or a snapshot (use a snapshot — see below). Then complete the setup checklist every new client account needs:

1. Business profile: name, address, timezone, logo — this feeds email footers and compliance.
2. Phone number: purchase via LC Phone, then complete A2P 10DLC registration immediately (US) — it takes days to approve and nothing SMS-related works properly until it's done.
3. Email sending domain: set up the dedicated sending subdomain (e.g. mail.clientdomain.com) with DKIM so deliverability doesn't depend on shared infrastructure.
4. Users and permissions: add client users with role restrictions (see below).
5. Integrations: Google Business Profile, Facebook/Instagram, Stripe, and calendar connections.

Snapshots — Never Build the Same Account Twice

A snapshot is a template of an entire sub-account: pipelines, workflows, funnels, email/SMS templates, calendars, custom fields, and tags, all packaged for one-click deployment into new sub-accounts. If you serve a niche, your snapshot IS your product — a new roofing client goes from signup to fully-built system in an afternoon.

• Create from the agency view: Account Snapshots → Create New Snapshot from your polished template account.
• Keep a "master template" sub-account per niche that you improve continuously; re-snapshot after meaningful upgrades.
• Push updates to existing sub-accounts selectively — GHL lets you choose which assets to overwrite (be careful with live client workflows).
• We build niche-tuned snapshots professionally — see our custom GoHighLevel snapshot service.

User Permissions — What Clients Should (and Shouldn't) See

Client users belong in their sub-account only, typically with an Account User role scoped so they can work leads without breaking the machine:

• Give clients: conversations, contacts, opportunities, calendars, reputation.
• Restrict by default: workflow editing, funnel/website builder, settings, and phone-number management. A client "just tweaking" a workflow is the #1 cause of mysteriously broken automations.
• Your agency staff use agency-level roles so they can move across sub-accounts without separate logins.

Making Money: Rebilling and SaaS Mode

Sub-accounts are also the billing unit. Three revenue models, in ascending order of leverage:

1. Service model: you charge a setup fee + monthly retainer; the sub-account is just your delivery vehicle.
2. Rebilling: on the $297+ plan you can rebill telephony and email usage (and premium features) to clients at a markup you set — costs become a margin line.
3. SaaS mode ($497 plan): clients self-signup to plan tiers you define, card on file with Stripe, sub-account provisioned automatically from your snapshot. This is the "sell GHL as your own software" model — see our white-label SaaS service and the SaaS mode deep-dive.

Common Sub-Account Mistakes

• Building clients inside your agency's own sub-account — data can't be cleanly separated later; every client gets their own sub-account from day one.
• Skipping A2P/domain setup on launch day — the client's first campaign lands in spam and first impressions are ruined.
• One giant do-everything snapshot — niche-specific snapshots deploy cleaner than a bloated universal one.
• Giving clients admin access — see permissions above; you'll rebuild that workflow eventually.
• No offboarding plan — decide upfront whether departing clients can export their sub-account (contacts export easily; workflows don't leave GHL).

Frequently Asked Questions