How to Manage a Sales Team Inside GoHighLevel

Written by Niyamul Islam Sajal, COO & GHL Certified AdminBlog
GoHighLevel sales team meeting around a table in an office

A GoHighLevel sales team runs best when each rep sees only their own leads, new enquiries land with someone automatically, and nobody can casually change the settings that run the whole account. HighLevel's own help documentation covers each of those pieces, and the setup takes an afternoon rather than a week.

This guide covers five settings in order: roles, visibility, round robin routing, weighted routing, and the toggle that stops leads being reassigned. After that comes a look at what reporting can and can't tell you about individual reps. Test each step on a spare account before touching a live one, and a trial is a low-pressure place to start: there's a 30 day HighLevel Bootcamp trial for exactly that kind of practice.

Set up roles for your GoHighLevel sales team

Every user in a sub-account has one of two roles, Admin or User. According to HighLevel's guide to sub-account roles, permissions and assigned data, Admin gives administrative access within the sub-account, while User gives access according to the permissions you configure for that person.

Keep Admin for the people who manage the account. Everyone else on your GoHighLevel sales team gets User.

You set this under Settings, then Users, inside the sub-account. Open an existing user or add a new one, go to Roles & Permissions, pick the role, set the module and granular permissions, then save.

The granular list is long. It includes AI Agents, Automation, Contacts, Conversations, Opportunities, Payments and User Management, along with about twenty more areas. A rep who works leads all day has no reason to edit Automation or manage other users, so switch those off.

Two details save time. Copy Permissions copies one user's granular setup to another, so you can configure one rep carefully and clone the result for the rest of the team. And calendar permissions live in a different place, under Settings, My Staff, Roles & Permissions, then Calendars.

One warning from the same page. If you switch off a module for a user but a workflow relies on it, existing workflows can keep running, so make sure an authorised user can still manage those automations.

Limit your GoHighLevel sales team to their own contacts and deals

Only Assigned Data limits a user's visibility to the records associated with them. Depending on the module, that means contacts assigned to them, opportunities they own, and appointments or tasks tied to them.

HighLevel's example is a sales user who can see their own contacts and opportunities instead of another rep's pipeline. It sits on the same Roles & Permissions screen as the module settings.

This setting is only as good as your assignments, though. If a contact has no owner, nobody sees it, and if the wrong rep owns it, the wrong rep works it. That's why the next sections matter more than they first look. If you haven't built the pipeline those deals live in yet, our guide to building a sales pipeline in GoHighLevel comes first.

Route new leads with round robin lead assignment

The Assign To User workflow action hands each new contact to a rep automatically. Pick several users and, in HighLevel's words, the trigger rotates between them in a round robin for each assignment. Pick one user and every contact goes to that person.

The Assign To User help article gives a simple example: with Tom and Jane selected, contacts go to Tom, then Jane, then Tom again.

The usual setup is a workflow that starts when a contact is created, with Assign To User as the first action. From there, other steps can notify the rep or create a task. Our post on moving deals between stages automatically covers what comes next in that workflow.

Fast follow-up depends on a clear owner from the first minute. Round robin lead assignment gives your GoHighLevel sales team that without a manager sorting a queue by hand.

Weight the split when reps aren't equal

Equal rotation suits a GoHighLevel sales team of similar experience. When it doesn't, the Split Traffic setting has an Unevenly option where you give each user a weight.

HighLevel's example uses three users, and the pattern repeats once the last user's share is filled.

UserWeightLeads received in each cycle
Alan3Leads 1 to 3
Bobby3Leads 4 to 6
Charlie1Lead 7

Equally is the default, and it spreads leads evenly in the same way as plain round robin. A new starter can sit at a lower weight while they ramp up, then move to match everyone else.

There's one quirk worth knowing. With a 5 to 2 ratio, the second user receives nothing until the first has taken their fifth lead, so a weighted split works in blocks rather than interleaving.

Stop workflows reassigning contacts you've already routed

Sales rep reviewing GoHighLevel sales team leads on a laptop

Photo by Vitaly Gariev on Pexels

The Only Apply to Unassigned Contacts toggle decides whether the action can overwrite an owner. Switched on, a contact is assigned only if nobody owns it yet. Switched off, the new assignment overwrites the previous one.

The help article's FAQ warns that a previously assigned contact may be reassigned when the workflow trigger fires. If your trigger can fire twice for the same person, for instance because a returning lead fills in a second form, a rep could lose a deal they were already working.

Turn the toggle on for any lead-routing workflow, then test under a variety of conditions before publishing, as HighLevel itself advises.

The action also has a Dynamic option where you pass in a user ID, found under Settings, My Staff, below the person's email. HighLevel's guidance is that in most situations you should use the standard picker, and that's good advice for a team setting this up for the first time.

What reporting shows about your GoHighLevel sales team

HighLevel reports opportunity data per user, such as who has the most won opportunities. Beyond that, the limits matter if you manage more than one group of reps.

Kixie, which sells a calling add-on and so has a stake in the answer, argues in a November 2025 post on advanced sales reports in GoHighLevel that user management is flat, with no team entity. It says call report filters work on phone numbers rather than groups of users, that team call volume means exporting a CSV and adding it up by hand, and that an Answered status can include voicemails.

Treat those as one vendor's claims and check them in your own account. The practical response doesn't depend on who's right: choose two or three numbers you'll review every week, and write down how each is counted.

A lead score helps here too, because it tells reps where to spend their first call. Our walkthrough of setting up lead scoring in GoHighLevel shows how.

Where we can take the setup off your hands

Permissions, routing and reporting all interact on a GoHighLevel sales team, and a mistake in one shows up as a rep who can't see a lead or a lead nobody owns. We've built and configured 100+ GHL accounts, with 7+ years in production, and our team is made up of GoHighLevel Certified Admins.

If you resell GoHighLevel, see how we work with agency owners. For a single business, our GoHighLevel setup service covers roles, workflows and pipelines, and our pricing starts with plans from $149 for business owners.

Frequently asked questions

Can one rep see another rep's deals in GoHighLevel?

Not on a GoHighLevel sales team set up with Only Assigned Data for each user. It limits visibility to contacts assigned to them, opportunities they own, and their own appointments or tasks.

Can I assign leads using logic outside HighLevel?

Yes. The Dynamic option in Assign To User accepts a user ID, which can come from a variable earlier in the workflow. HighLevel's own example passes it in through an inbound webhook, though it recommends the standard picker in most situations.

What happens to my workflows if I turn off a module for a user?

Existing workflows can continue to run. Make sure an authorised user keeps the access needed to manage those automations.

Sources

Cover photo by Edmond Dantès on Pexels

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call