White-label GoHighLevel: what to hand a build partner

A client signs for a CRM build on a Thursday, and by Friday the fulfillment partner is asking for a login. The quickest answer is to make them an agency admin and move on. It is also the answer that gives a contractor the keys to every client you have, your billing and the domain your white-label app runs on.

HighLevel already splits the account the way a white-label arrangement needs: an agency layer you run, and sub-accounts where the client work happens. The job is to put the partner in the second layer and keep the first. Here is how we would divide it, with HighLevel’s own help pages for each setting.

The two layers of a HighLevel account

HighLevel sorts every login by user type and role. The type decides where a person works: Agency for people who need agency-level access, Account for people who should only see selected sub-accounts. The role, Admin or User, decides how much they can do inside that scope.

HighLevel’s agency permissions article says it plainly: for users who need selected client accounts without agency-wide access, use the Account user type and assign only the sub-accounts they need. That one setting is most of a white-label access policy.

Two agency-level powers matter more than the rest:

• Sub-account transfers. By default only the Agency Owner can request or complete one, and the owner can grant that permission to specific Agency Admins. A transfer moves the whole sub-account, contacts and history included, to another agency.
• Login As. An eligible Agency Admin can sign in as another user, and the permission is on by default. Anyone you make an agency admin can, by default, work as any of your users.

What to hand the partner

Give a build partner exactly what the build needs, written down before the first login:

• An Account-type login on the named sub-accounts, with the Admin role if they are building workflows, calendars and phone settings, and the modules they will not touch switched off.
• A one-page scope: pipeline stages, the calendars and their rules, which forms feed which workflow, who gets notified and how, and what “done” means.
• The client’s answers, not their website: hours, service area, services they do not offer, who picks up a transferred call.
• The A2P details, collected from the client (more on that below).
• DNS records to forward, not registrar access. The partner sends the records for a funnel or email domain; you or the client add them.

What the partner should never need is an Agency-type login, the client’s billing or a seat on your agency’s own sub-account.

What stays with your agency

The white-label promise is that the client sees one company. That holds only while these stay yours:

• The agency owner seat and every Agency Admin seat.
• Sub-account transfer permission.
• The HighLevel subscription, and whatever you rebill to clients.
• Your branding at agency level: the app domain, logo and colors clients log in to.
• The client conversation: support email, change requests and the monthly call.

The trap is an offer to host the client in the partner’s own HighLevel account to save setup time. If that relationship ends, getting the sub-account back is a transfer, and only that agency’s owner, or an admin they have authorized, can submit it.

Snapshots: who owns the master

A snapshot is a copy of a source sub-account’s setup that you can load into new or existing sub-accounts. Have the partner build the source sub-account inside your agency account, so the snapshot is created in your library and stays there whoever you work with next year.

Know what a snapshot leaves out before anyone promises a fast launch. HighLevel lists contacts, appointments, conversations and their history, reputation data, Stripe connections, integrations and the phone numbers assigned to Voice AI agents among the things that do not transfer.

Two more points belong in the agreement. A snapshot does not update itself when the source changes; someone refreshes it and pushes the update, so name who approves a push to live clients. And if a partner shares an Assets Protected snapshot with you, HighLevel lets you reuse those assets across your own sub-accounts but not resell or share them with another agency, so ask before you build an offer on one.

A2P and phone numbers sit in the client’s name

Texting from a HighLevel number needs an A2P 10DLC brand, and the brand is the business that sends the messages. HighLevel’s brand article asks for the legal business name and EIN exactly as they appear on the IRS CP-575 or 147C letter, warns against using a DUNS number, and notes that an EIN issued in the last 15 days may be rejected.

So the onboarding form asks the client for those documents and for an authorized representative whose email and mobile number carriers can check. If a registration comes back rejected, our A2P rejection guide walks through the usual fixes.

Phone numbers follow the sub-account. When both agencies use LC Phone, HighLevel moves the numbers with a transfer and eligible A2P registration stays with them; on other providers the number has to be moved separately. That is one more reason the client’s sub-account belongs in your account from the first day.

What to do this month

• Open Agency View, Settings, Users, and switch any partner login of the Agency type to Account type with named sub-accounts.
• Check who holds sub-account transfer permission, and remove it from anyone who does not need it.
• List any client sub-account that lives in someone else’s HighLevel account, and ask for the transfer while the relationship is friendly.
• Add the CP-575 or 147C letter and an authorized representative to your client onboarding form.
• Write down what your main snapshot does not carry, and put it in the welcome email so nobody promises a same-day launch.

Agencies send us GoHighLevel builds to deliver under their own brand, and the partner model explains how that works. For notes like these once a month, the agency newsletter is the lighter option.