When several people use Claude with your clients' GoHighLevel accounts, you need to know who can change what. My GoHighLevel MCP keeps this simple, with three roles.
The three roles
Owner. The person who created the organisation. The owner can do everything an admin can, and is the only person who can delete the organisation.
Admin. Admins run the organisation day to day. They can sign in to the platform, choose which sub-accounts Claude may work in, add and remove people, switch tools off, look at the Activity log, and pay for sub-accounts.
Member. Members use Claude with GoHighLevel, and that's it. They don't sign in to the platform, and they can't choose sub-accounts or pay for anything. This is the right role for most of your team.
There is no seat limit: add as many people as you need at no extra cost. You pay per sub-account, not per person.
Everyone has their own sign-in
Each person signs in to My GoHighLevel MCP as themselves, and signs in to GoHighLevel from Claude with their own GoHighLevel login. Nobody shares a password. That matters for two reasons:
- GoHighLevel's own permissions still apply. If someone can't see a sub-account in GoHighLevel, they can't reach it through Claude either.
- The Activity log names real people. Every request is recorded with the person who made it.
Adding someone
An admin adds people on the platform's Team page, as a member or an admin. You can give each person a label, such as "looks after the dental clients", to keep track of who does what.
When someone leaves
Access should end the moment someone leaves. On the Team page, an admin can:
- Disable the person: they lose access immediately, including any Claude connections, but their history stays in the log.
- Sign them out of Claude everywhere, if you only want to end their current connections.
- Remove a disabled person permanently.
Disabling first is usually the right choice: it's instant, and you keep a record of what that person did.
Promote carefully
Admins can choose sub-accounts and spend money, so keep the admin group small. It's easy to change: Make admin and Remove admin are on the Team page.
A sensible setup for an agency
- One owner, usually the agency founder.
- One or two admins who manage billing and sub-accounts.
- Everyone else as members.
Combined with choosing sub-accounts carefully and switching off tools you don't need, this gives you clear control without slowing anyone down.
