Best Marketing Stack
Tutorial · beginner · 45 minutes

Setting up your first GoHighLevel sub-account

How to provision your first agency sub-account, apply a snapshot, configure branding, and invite a client team — the core agency workflow.

Open HighLevel in a new tab →

Before you start

  • An active GoHighLevel agency account (Starter plan or higher — Starter includes 3 sub-accounts)
  • A client business name and primary contact email
  • Optional: a logo file and brand colors for white-label setup
1

Open the agency dashboard and navigate to Sub-Accounts

After logging in, your top-level view is the Agency Dashboard. Click 'Sub-Accounts' in the left sidebar. This is where you create and manage every client account. The 3-sub-account limit on Starter shows in the header.

2

Click Create Sub-Account and fill in basic details

Use the client's actual business name (this is what they will see when they log in). Add the business address, phone, and timezone. Pick a sensible time zone — automation triggers fire on this clock, so getting it wrong skews everything from email send times to calendar bookings.

3

Apply a snapshot template (or skip and start blank)

Snapshots are HighLevel's pre-built sub-account configurations — funnels, automations, pipelines, and email templates packaged together. Browse the marketplace under Snapshots and pick one that matches the client's industry (Real Estate, Dental, Gym, etc.). Applying a snapshot saves hours but you can always start blank and build manually.

4

Configure white-label branding

Under Sub-Account > Settings > Company, upload the client's logo and set their brand colors. This is what shows when the client logs in — they should never see HighLevel branding. On the Pro plan you can also point a custom domain at the sub-account dashboard.

5

Invite the client and team members

Under Sub-Account > Settings > My Staff, add the client's primary contact as Admin and any additional team members with appropriate roles (User, Admin, or Agent). Each invited user gets an email to set their password. Make sure to set strong roles — Admin can change billing.

6

Test a basic workflow before handing over

Trigger one of the snapshot's pre-built workflows (e.g. send a test SMS to your own phone via the Conversations tab, or fill out a contact form in the funnel) to confirm everything works. Catch broken integrations now, not after the client logs in.

7

Hand over login info and document custom changes

Send the client their login URL, username, and a one-page handoff document listing what is set up: snapshot applied, automations enabled, integrations connected. This prevents future support tickets where the client has no idea what already exists.

Common pitfalls

What to do next

Full Review
Read our full HighLevel review
Strengths, weaknesses, pricing, and who HighLevel fits.

Ready to put this into practice?

Start HighLevel free →