When a client hires a sales floor, or you onboard a new agency client with ten reps, adding them one by one in HighLevel gets old fast. This guide covers how to bulk add users in GoHighLevel: the native path and its shortcuts, how to script it with the API, and how to set permissions so you don't have to revisit each person later.
Plan roles before you add anyone
Most of the time spent on user setup is actually spent on permissions. Decide these first:
| Decision | Options | Tip |
|---|---|---|
| Role | Admin or User | Keep Admin for people who manage settings. |
| Modules | Contacts, Conversations, Opportunities, Calendars, Automation, Marketing, Payments and more | Turn off what they don't need. Fewer menus means fewer mistakes. |
| Only Assigned Data | On or off | On for reps who should only see their own contacts, opportunities and appointments. |
| Sub-accounts | One or several | Agency staff may need access to more than one location. |
A short sheet with one row per person (name, email, phone, role, permission template) makes the rest quick, whichever method you use.
How to add users natively
As of October 2026, HighLevel's help center describes the sub-account path as:
- Open the sub-account and go to Settings, then Users (older accounts and guides may call this Team or My Staff).
- Click Add User (some screens say Add Employee).
- Enter the person's name, email and phone, and set a password.
- Under Roles & Permissions, choose Admin or User and set the module permissions.
- Turn on Only Assigned Data if they should only see their own records.
- Save.
Agency-level staff are added from Agency Settings instead, where you can also give a user access to several sub-accounts.
Use Copy Permissions to save the toggles
HighLevel's help center says bulk assignment of permissions isn't supported, but there is a Copy Permissions option that copies one user's permission configuration to another. Set up one rep exactly how you want, then copy that setup to each new rep. You still create each user individually, but you skip re-clicking 25+ module toggles each time.
How to bulk add users in GoHighLevel with the API
For a real bulk add, the Users API is the native route. A POST to https://services.leadconnectorhq.com/users/ with a token that has the users.write scope creates one user per request. The body includes the person's first and last name, email, a password, a role (admin or user), the sub-account IDs they belong to and an optional permissions object. Depending on the token you use, the request may also need your agency's company ID, which you can read from the sub-account's location details (GET /locations/{locationId}).
Loop your sheet through Postman, a script or an automation tool, and pause briefly between requests. If you need a token for a single sub-account, see our Private Integration token guide.
A few things we learned building this:
- Generate a strong temporary password for each person and send it to them securely. Ask them to change it at first login.
- Read back each response and record the new user ID. You'll need it for later permission changes.
- Duplicate emails fail, so check for existing users first.
Permission templates that save time
Most teams only need three or four permission setups. Define them once and reuse them:
| Template | Role | Typical access | Only Assigned Data |
|---|---|---|---|
| Sales rep | User | Contacts, Conversations, Opportunities, Calendars | On |
| Team lead | User | Rep access plus Reporting | Off |
| Processor or ops | User | Contacts, Opportunities, Documents, Payments | Off |
| Manager | Admin | Everything, including Settings | Off |
Write these down before the first hire. When the next person starts, you pick a template instead of making new decisions, and every rep in the same seat ends up with the same access.
After the users are in
- Log in as one test user, or ask a rep to confirm, to make sure they see what they should.
- Check contact owner and round-robin settings if leads are assigned automatically.
- Keep your permission sheet. When someone leaves, you'll want to know exactly what they had. Our guide on how to pause user access in GoHighLevel covers offboarding.
Where the native way gets slow
One or two users at a time is fine in Settings. The friction shows up with a sales floor, a seasonal hiring wave or an agency rolling out the same team structure across several clients. Each user is a full form plus permissions, and Copy Permissions still needs a click per person. The API removes the clicking but adds token handling, company ID lookups and a script you have to maintain.
How Sub-Account Manager handles it
Sub-Account Manager's bulk user creator is the paste-a-list version:
- Pick the sub-account. A Detect button reads the company ID from the sub-account for you.
- Paste your people, one per line: name and email, with phone optional.
- Choose the role and set a permissions grid that applies to everyone in that batch.
- Preview, then create them all at once. Everyone gets a temporary password you can download.
Later changes are covered by the user and permission manager, which changes roles in bulk, or pauses a user's access and restores it exactly as it was.
If you add one person a month, the Settings page is plenty. If you onboard teams, pasting a list is faster and leaves fewer permission mistakes behind.
Questions
Can you bulk add users in GoHighLevel?
Not from the settings screen. As of October 2026 users are added one at a time in the sub-account's Settings, under Users. HighLevel's help center says bulk permission assignment isn't supported and points to Copy Permissions instead. The Users API can create users in a loop.
What is Copy Permissions in GoHighLevel?
It copies one user's permission configuration to another user, so you don't have to set every toggle by hand. It saves time, but you still create each user individually.
Should new users be admins or users?
Give most staff the User role with only the modules they need, and turn on Only Assigned Data for reps who should only see their own leads. Keep Admin for the few people who manage settings.