GoHighLevel Launchpad: Client Sub-Account Setup (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 5 October 2026 · 9 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.
GoHighLevel Launchpad is the first screen most new clients see when they log into their sub-account, and it quietly shapes how their first week with you goes. Used well, it gets the basic connections done fast. Left on autopilot, it confuses clients who expected your team to do everything.
In this guide I'll walk through when to keep HighLevel LaunchPad visible, when to hide it, and how to pair it with your snapshot, onboarding checklist and white-label app. You'll also get the day-one setup sequence we use with Australian agency clients, plus the mistakes I see most often in inherited accounts.
Quick Facts
| What it is | The getting-started page inside a HighLevel sub-account |
| Typical items | Connections such as Google Business Profile, Facebook and the HighLevel mobile app |
| Default state | Visible at every level until you hide it |
| Control levels | Per sub-account, per SaaS plan and per user role |
| Agency-wide switch | Launchpad settings at /settings/launchpad on your white-label domain |
What GoHighLevel Launchpad actually does for a new sub-account
Launchpad is a guided starting point. It walks a new user through the first connections a sub-account needs before automations, reviews and conversations can do anything useful.
The items it surfaces include things such as:
- Connecting Google Business Profile, so review requests and review replies have somewhere to land
- Connecting Facebook, so the business can message leads from inside HighLevel
- Downloading the HighLevel mobile app, so the owner can reply to leads on the go
Treat it as a prompt list rather than a complete onboarding system. Launchpad tells a client what to connect; it does not tell them why your build depends on it, and that gap is where your own process has to take over.
HighLevel LaunchPad permission controls: the three levers
HighLevel shipped LaunchPad Permission Controls, which let you decide exactly who sees the page. Launchpad is visible by default at every level, and you can hide it at any time.
Per sub-account
Inside Sub-Account Settings → Features & Limits you can show or hide Launchpad for one client. This is the lever for exceptions, such as a single done-for-you client sitting inside an otherwise self-serve plan.
Per SaaS plan
If you run SaaS Mode, you can show or hide Launchpad for every account under a plan. That means your entry-level self-serve tier can keep it while your managed tier never sees it.
Per user role
Through Roles & Permissions you can control Launchpad by user role. This is the one most agencies forget, and it matters because a receptionist or sales rep has no business connecting the company's Facebook page. If you haven't tidied up roles yet, start with our guide to sub-account permissions and user roles.
The agency-wide switch
You can also disable Launchpad for all sub-accounts from your agency's Launchpad settings, found at /settings/launchpad on your white-label domain. Use this if your whole model is done-for-you and you would rather turn it back on case by case.
When to keep GoHighLevel Launchpad on, and when to hide it
The decision comes down to one question: who is doing the setup work? If the client is, Launchpad helps. If your team is, it creates noise and duplicate effort.
| Client or user type | Launchpad | Why |
|---|---|---|
| DIY / SaaS self-serve client | On | They need a guided path to connect accounts without waiting on your team |
| Hybrid client (you build, they connect) | On for the owner role | The owner holds the logins for Google and Facebook, so they finish the connections |
| Done-for-you client | Hidden | Your team connects everything; a checklist they cannot action only causes support tickets |
| Staff roles (reception, sales reps) | Hidden | They should work conversations and pipelines, not change business connections |
| Your internal team users | Hidden or on, by preference | Many admins prefer a cleaner dashboard once they know the build |
Self-serve clients are where Launchpad earns its keep. The faster they connect Google Business Profile and Facebook, the sooner they see a review or a lead come through, which is the whole point of shortening time to value in SaaS onboarding.
Done-for-you clients are the opposite. They paid you so they would not have to click through setup screens, and seeing an unfinished checklist makes them wonder whether you have started at all.
Pairing HighLevel LaunchPad with your snapshot and onboarding checklist
Your snapshot carries the build: pipelines, workflows, calendars, templates and custom fields. Launchpad covers the connections a snapshot cannot carry, because those belong to the client's own Google, Facebook and phone accounts.
That split is useful. Load the snapshot first, then let Launchpad and your checklist handle the client-owned connections. If you are still deciding what belongs in the snapshot, our walkthrough on building and deploying GoHighLevel snapshots covers the structure we use.
Your onboarding checklist then fills the gaps Launchpad doesn't cover, such as the email sending domain, number registration and user invitations. We map this against the 7-day client onboarding checklist so nothing depends on the client remembering a step.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
A day-one sub-account setup sequence that works with Launchpad
This is the order we follow on day one, whether the client is clicking through Launchpad themselves or our team is doing it on a call with them. Order matters, because some steps unlock the next.
- Connect Google Business Profile. Reviews, review requests and local visibility all depend on it, so it goes first.
- Connect Facebook. This lets the team message leads inside HighLevel instead of switching between apps.
- Set up the phone number. Provision LC Phone or connect the existing number, then test an inbound call and an SMS before any workflow sends.
- Configure the email sending domain. Sending from a properly set up domain protects deliverability; do this before the first campaign, not after complaints.
- Connect the calendar. Link the owner's calendar and check availability so booking widgets don't double-book.
- Install the mobile app. Get the owner logged in on their phone while you are still on the call.
- Invite users with the right roles. Add staff last, each with the narrowest role that lets them do their job.
Doing users last is deliberate. By then the connections are in place, so staff log in to a working account rather than a half-connected one, and you can hide Launchpad for their roles before their first login.
Who does each step
For self-serve clients, Launchpad guides the first connections and your checklist covers the rest. For done-for-you clients, run the whole sequence on a recorded screen-share so the owner only has to approve logins.
Either way, never leave a client to discover the phone or email setup on their own. Those are the two steps most likely to cause silent failures later.
Handing over with a white-label app
If you run a white-label mobile app, point clients to your branded app rather than the generic HighLevel app when they reach the mobile app step. Mixed messages here are common, and a client who installs the wrong app will ask why their login looks different.
Update your welcome email and checklist so the download link matches your brand. Our guide to white-label mobile app branding covers the setup, and it's worth finishing before you onboard clients at scale.
For the handover call itself, keep it short. Show the owner where conversations arrive, how to reply from the app, and where to find their review requests, then confirm everything on your checklist is ticked.
Tracking onboarding completion beyond Launchpad
Launchpad shows progress to the client, but it is not a reporting tool for your agency. You need your own view of which clients are stuck and on which step.
The simplest approach is an onboarding pipeline in your agency's own sub-account, with one opportunity per new client. Stages can mirror the day-one sequence:
- Snapshot loaded
- Google Business Profile and Facebook connected
- Phone and email sending domain live
- Calendar and mobile app done
- Users invited and handover complete
Attach tasks to each stage with a due date and an owner on your team. A task with a name and a date beats a checklist nobody opens, and it gives you a clear list of who to chase each morning.
Review the pipeline weekly. Any client sitting in the same stage for more than a few days usually needs a quick call rather than another automated reminder.
Common mistakes to avoid
- Leaving Launchpad on for done-for-you clients, so they see an unfinished checklist and assume work hasn't started.
- Forgetting role-level controls, which lets staff users poke at business connections they should never touch.
- Treating Launchpad as the whole onboarding process and skipping the email sending domain and phone setup.
- Pointing white-label clients to the generic mobile app instead of your branded one.
- Inviting staff before connections are live, so their first login lands in a half-working account.
- Hiding Launchpad agency-wide without a checklist or pipeline to replace it.
If you want a done-for-you sub-account onboarding system with Launchpad, snapshot and pipeline set up properly, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
What is GoHighLevel Launchpad?
GoHighLevel Launchpad is the getting-started page inside a HighLevel sub-account. It walks new users through first connections such as Google Business Profile, Facebook and the HighLevel mobile app. It is a helpful prompt list, but it does not replace your own onboarding process.
Can I hide Launchpad for just one client?
Yes. In Sub-Account Settings → Features & Limits you can show or hide Launchpad for a single sub-account. This suits a done-for-you client who sits alongside self-serve clients.
Can I hide HighLevel LaunchPad for a whole SaaS plan?
Yes. LaunchPad Permission Controls let you show or hide it for all accounts under a SaaS plan. That lets a self-serve tier keep the guided setup while a managed tier never sees it.
Can staff users be blocked from seeing Launchpad?
Yes. You can control Launchpad visibility by user role through Roles & Permissions. Hiding it for reception and sales roles stops them changing business connections they should not touch.
How do I turn off Launchpad for every sub-account?
Go to your agency's Launchpad settings at /settings/launchpad on your white-label domain and disable it for all sub-accounts. You can then turn it back on per sub-account, plan or role where it helps.
Is Launchpad turned on by default?
Yes. Launchpad is visible by default at the sub-account, SaaS plan and user role levels. You can hide it at any time, so review your settings before onboarding new clients.
Does Launchpad replace an onboarding checklist?
No. Launchpad covers early connections, while your checklist should also cover items such as the phone number, email sending domain, calendar and user roles. Track both with an onboarding pipeline and tasks so you can see who is stuck.
Related Articles on HL Growth Partner
SaaS Mode and plans
Snapshots and white-label
- Pushing snapshot updates to live sub-accounts
- The complete GoHighLevel white-label setup guide
- Custom menu links for your agency
