A Meaningful Career
100% virtual · 50 state coverage
Structure map
July 9, 2026
July 9, 2026
Account Structure
One agency, one sub-account, and the room to grow
This is how the GoHighLevel account is built today, and the two ways a VP's downline can grow from it. Read it top to bottom: the Agency holds billing and owns everything, sub-accounts (GoHighLevel calls them Locations) sit under it, and users live inside a sub-account. Hover any node to trace it, click to lock the detail open. Then use the Path A and Path B toggle to see the two growth stories.
1 agency
·
1 live sub-account
+
2 future (VP)
11 users
·
251 contacts
A2P 10DLC pending
Agency (billing owner)
Live sub-account
Future sub-account (not created)
Users
Risk or hard truth
Connectors
Owns or contains
Future or clone
Path B (independent)
Growth path
Scroll sideways to see the full structure.
Agency
Tier 1
Holds billing. Owns every sub-account. Builds snapshots. Sees everything.
Sub-accounts
Tier 2 · Locations
Each sub-account is a self-contained GoHighLevel Location.
Users
Tier 3 · Inside a sub-account
Downline growth
Growth · When a VP graduates
A snapshot of the live build is the fork. It goes one of two ways.
Path A · stays in the family
New sub-account per VP, cloned by snapshot. Andre keeps billing and visibility.
Path B · goes independent
The VP buys their own agency. A snapshot rebuilds the account. History does not travel.
GoHighLevel AgencyA Meaningful Career, LLC
Live sub-accountA Meaningful Career, LLC
Future VPnot created yet
Future VPnot created yet
No spin-off buttonseparation = rebuild
11 usersall Agency type
Account vs Agencytype decides visibility
All 11 users are Agency levelthey will see every new sub-account
A2P is per sub-accountnever inherited
Snapshotclones the build, not the data
New sub-account per VP
Clone the build with a snapshot
Own contacts, calendar, number, A2P
Andre holds billing, optional SaaS
VP buys their own agency
Load Andre's snapshot link
Contacts by CSV, history left behind
Register own A2P from scratch
owns every sub-account
can see it
snapshot the build
clone
share link
What a snapshot carries, and what it leaves behind
A snapshot is a clone of the build, not a copy of the account. Whichever path a VP takes, this is the line between what travels and what has to be rebuilt or re-registered.
Travels in a snapshot
The build comes across, ready to run.
Workflows and automations
Triggers
Calendars, including round robins
Custom fields
Pipelines
Tags
Funnels and websites
Forms and surveys
Email and SMS templates
Does not travel
This is why separation is a rebuild, not a transfer.
Contacts (CSV export and import only)
Conversation history (texts and emails)
Call recordings
Appointment history
A2P 10DLC registration
Phone numbers