Sub-Account Access
Sub-account access is the moment the client logs into their GoHighLevel sub-account for the first time. This happens live on the quick start call, not via an email link they may or may not open. You verify their credentials work, reset the password if needed, and confirm they can see their dashboard. It sounds simple, and it is. But skipping it or deferring it creates a chain of problems that ripples through the entire onboarding.
Why This Matters
A client who cannot log in is a client who is not engaged. They cannot see the work you are doing. They cannot complete tasks that require their authentication. They cannot explore the platform between calls. Every day they do not have access is a day the system feels like something that is being done to them instead of something they are part of.
The quick start call is the highest-energy moment in the client relationship after the sale. They just paid. They are motivated. They want to see what they bought. If you waste that energy by sending them a “check your email for login details” message and moving on, you are throwing away your best window to get them engaged with the platform. Many clients will not log in on their own. They will put it off, forget their password, get distracted, and then show up to the next call having done nothing.
Confirming access live also catches problems immediately. The invitation email went to spam. The password does not meet requirements. The client is using an old email address. Multi-factor authentication is blocking them. These are two-minute fixes on a live call. They become multi-day support tickets if you discover them later.
How to Think About It
Treat sub-account access as a gate, not a step. Nothing else on the quick start call should proceed until the client is logged in and looking at their dashboard. This is not about being rigid. It is about ensuring that every subsequent action — downloading the mobile app, connecting Google Business Profile, viewing the social planner — happens from a position of verified access.
The login moment is also your first chance to orient the client. Walk them through the dashboard briefly. Point out the sidebar navigation. Show them where conversations live, where contacts are, where settings are. You are not training them. You are giving them a mental map so the platform does not feel foreign when they log in on their own later.
Keep the energy collaborative. “Let’s get you logged in” is better than “Check your email for your credentials.” Make it feel like you are doing this together. The client should feel guided, not instructed.
Common Mistakes
Assuming the invitation email was received. Email deliverability is unpredictable. GHL invitation emails can land in spam, promotions tabs, or get blocked entirely by corporate email filters. Always have the client check for the email while you are on the call. If it is not there, resend it or manually set the password.
Moving on when the client says “I’ll do it later.” This is the number one mistake. The client is being polite. They do not want to slow down the call. But “later” usually means “never” or “three days from now after two support emails.” Insist on doing it live. It takes 90 seconds.
Not resetting to a strong password. Some agencies use temporary passwords that are easy to guess or share passwords via plaintext messages. Walk the client through setting a password they will remember, and encourage them to use a password manager. If they get locked out repeatedly, they will stop logging in.
Skipping the dashboard orientation. Logging in and immediately moving to the next setup task is a missed opportunity. Take 60 seconds to show them the lay of the land. The client needs to feel that this is their platform, not a black box you control.
Forgetting to confirm the correct email address. Clients sometimes have multiple email addresses. The one they used during the sale might not be the one they check daily. Confirm which email they want associated with their account before sending the invitation.
Tools Involved
The sub-account itself is created through GHL agency settings. User invitations go out via email from the platform. If you need to troubleshoot access issues, the agency-level user management panel lets you resend invitations, reset passwords, and verify account status. For agencies running GHL MCP automations, sub-account provisioning can be partially automated, but the live verification step on the call is still essential.
Where This Fits
Sub-account access runs in parallel with Expectation Setting at the start of the quick start call. Both depend on the sub-account having been provisioned (SAP) before the call. Once the client is logged in, it unlocks everything else: Mobile App download, Team Members setup, Business Profile verification, and all the connection steps like GBP Connection, Social Connections, and Google Calendar.
Common Questions
What if the client forgot which email they signed up with? Check your CRM records from the sale. If you captured their email in the contact record, reference that. If there is still confusion, ask them to check their recent email for anything from GoHighLevel or your agency domain. Worst case, create the account with their preferred email and move on.
Should I give the client admin-level access? In most agency setups, the client gets a user role, not an admin role. They need enough access to view conversations, contacts, calendars, and reputation, but they should not be modifying workflows, automations, or integrations. Set permissions based on what they actually need to do day-to-day.
What if the client is not tech-savvy and struggles with login? Patience and screen sharing. Walk them through it step by step. Have them share their screen if possible so you can see exactly what they see. For clients who are genuinely uncomfortable with technology, this moment sets the tone. If you handle it with calm confidence, they trust you with the rest. If you seem frustrated, they shut down.