Your GoHighLevel Sub-Account Setup, Step by Step

A GoHighLevel sub-account setup starts before you ever click "Create New Account." Each sub-account is a separate workspace: its own CRM, workflows, calendars and pipelines, walled off from every other client sitting under the same agency login.

Get the structure right at creation and a new client's onboarding takes minutes. Skip that step, though, and you end up rebuilding pipelines and permissions by hand months later.

Where a GoHighLevel sub-account setup actually starts

From the agency dashboard, open Account Snapshots in the left-hand menu. Next to any snapshot you've already built sits a blue Create New Account button, and clicking it opens a short form for the new client's details.

Submit that form and the sub-account loads with the snapshot's assets already attached. That skips the separate import step, so you're not rebuilding the same workflows by hand for the tenth client in a row.

A snapshot can carry funnels, forms, email templates, workflows, pipelines, custom fields, calendars and dashboards, copied from whichever source account you built it on.

It won't bring across live contacts, appointments, conversations or third-party integration connections. Funnels and websites land as drafts, too, so they still need a domain and a publish click before a client ever sees them.

If this is the first sub-account you're standing up, our GHL setup and configuration work usually starts with one clean account built the way every future client should look, then turns it into the template the rest of your snapshot library gets built from.

Deciding whether this is a client account or your own

HighLevel asks a blunt question at creation: is this your client's account, or your own? The second option designates an agency sub-account, the workspace your agency uses to run its own SaaS plans, rebilling and payment provider connections rather than a client's business.

The two look almost identical day to day. They behave very differently once money or SaaS billing gets involved.

Choose wrong and the fix is not simple. An agency sub-account cannot be handed off to another agency later, and removing the designation gets blocked while billing or SaaS dependencies are still attached. Decide which one you're building before you connect a payment provider, not after.

Agencies running white-label SaaS tend to keep one agency sub-account as the hub for every white-label support and rebilling setup, with client sub-accounts spun up underneath it from a snapshot.

Getting roles and permissions right before clients log in

Every sub-account carries two role types: Admin, with full administrative access subject to whatever granular permissions you set, and User, which starts restricted and only opens up where you allow it.

Both are configured from Settings, then My Staff. Edit the person's profile, open the Roles and Permissions tab, and switch individual modules like Workflows, Calendars, Payments or Conversations on or off one at a time.

Toggle "Only Assigned Data" for a user and they stop seeing the whole account's contacts, opportunities and tasks, limited instead to the ones assigned to them specifically.

Once you've built that permission set for one role, HighLevel lets you clone it onto the next hire instead of rebuilding it by hand, which matters more than it sounds like once you're staffing more than a couple of sub-accounts.

Run through that permission check before a client ever logs in themselves. A sub-account that looks finished in the builder can still hand a new user access to billing or every contact by default.

Finding that gap during setup beats finding it after a client's staff member has already poked around where they shouldn't.

Cover photo by Towfiqu barbhuiya on Pexels