Team Members
Team members refers to adding any additional users beyond the primary client contact who need access to the sub-account. This includes office managers, receptionists, sales staff, or business partners who will interact with the system. It happens during the quick start call while the client is present and can identify who needs access and at what level.
Why This Matters
Most businesses are not a one-person operation. The owner might be on the quick start call, but the person who actually answers leads, manages the calendar, or responds to reviews might be someone else entirely. If that person does not have access, the system sits unused during the exact hours when it matters most.
The pattern is familiar: you build a beautiful automation that routes leads to the conversation inbox. The business owner sees the leads on their phone but they are in meetings all day. Their receptionist could handle the responses but has no login. Leads go cold. The owner blames the system. The real problem is that the right people were never given access.
Adding team members during the quick start call also prevents the slow drip of “can you add my office manager” requests that come in over the following weeks. Each of those requests interrupts your build workflow, requires a separate conversation about permissions, and adds administrative overhead that could have been handled in three minutes on the original call.
How to Think About It
Ask the client directly: “Who else on your team needs access to this system?” Do not assume the answer is nobody. Even solo operators often have a virtual assistant, a spouse who handles admin, or a part-time employee who manages the phones. Get the names and email addresses during the call.
Permissions matter. Not everyone needs the same level of access. The business owner gets full user access. The receptionist might only need conversations and calendar. The marketing person might need social planner and reporting. GHL’s role system lets you control this. Set it up correctly from the start rather than giving everyone full access and dealing with the consequences.
Think about team members as force multipliers for your automations. Every workflow you build becomes more valuable when more people on the client’s team can see and act on the results. A lead notification is useless if it only goes to someone who checks their phone twice a day. Adding the right team members means your system has more hands ready to respond.
Common Mistakes
Not asking about team members at all. Many agencies assume the person on the call is the only user. They are not. Ask explicitly. Even if the answer is “just me for now,” you have planted the seed that adding people later is easy.
Giving everyone admin access. The path of least resistance is to give every team member full access. This leads to accidental changes to workflows, deleted contacts, modified pipeline stages, and other issues that are hard to trace. Match permissions to the person’s actual responsibilities.
Adding team members without the client present. If the client emails you after the call saying “add john@company.com,” you do not know John’s role, what he should see, or whether the client fully thought through the implications. Whenever possible, discuss team member additions live so you can set appropriate permissions.
Forgetting to have team members download the mobile app. Adding a user account is only half the job. That person also needs the Mobile App and proper Notification Settings. Send them the same onboarding sequence you give the primary user.
Not explaining the user vs. the client distinction. Team members who are added as users sometimes think they are customers of your agency. Make it clear that they are users of their employer’s system, and that support requests should go through the primary contact unless you have a different arrangement.
Tools Involved
Team members are managed through GHL’s Sub-Accounts user management. Invitations go out via email and include a link to set up credentials. Role-based permissions are configured at the sub-account level. For agencies managing many clients, GHL MCP can automate parts of the user provisioning process. If you are tracking onboarding tasks, the team member setup should be a checkbox in your onboarding pipeline.
Where This Fits
Team members runs in parallel with Mobile App and Business Profile at sequence position 12, right after Sub-Account Access confirms the primary user can log in. It does not block any of the connection steps like GBP Connection or Social Connections, but the team members should be added before Notification Settings so their alerts can be configured at the same time.
Common Questions
How many team members can be added to a sub-account? There is no hard limit on GHL sub-account users for most agency plans. You can add as many team members as the business needs. The constraint is usually practical, not technical: more users means more people to train and more notification configurations to manage.
What if the client wants to add someone later? That is fine. Walk them through the process so they know it is available, or let them know they can request additions through your support channel. The goal on the quick start call is to capture everyone they know about right now.
Should team members attend the quick start call? Ideally, yes, but practically it rarely happens. The business owner is usually the only one on the call. What works better is adding the team members’ accounts during the call, then having the owner introduce the system to their staff. Provide a short orientation guide or video they can share internally.