Different User Permissions Across subaccounts
A
Ashley Durr
I came across this issue as I have a user that already exists in my system through someone else's sub-account and now they want their own account but they purchased a plan that gives them fewer permissions but I can't remove features from their profile without it affecting the other subaccount they are in. This is definitely a limitation for my (and probably other's) use cases.
Log In
C
Carlos Javier Alvarez
We Agency users really need this update. Currently it is not possible to give the same user access to different subaccounts, each with different permissions.
This would be really useful because the user can work with several businesses that are not related but that the same agency manages. That would remove the friction, allowing they to easily change subaccounts without having to do the tedious process of logging out and logging back in with a different username and password every time they need to change locations.
S
Sales & Marketing
Merged in a post:
Subaccount-Specific Role Permissions
C
Catherine Mahilum
We need the ability to set user role permissions on a per-subaccount basis.
Example:
In Subaccount A, remove access to Automations, Forms, Sites, Funnels, and Surveys.
In Subaccount B (and others), keep full access to these features.
Currently, changing role permissions affects all subaccounts a user is part of, which limits flexibility for agencies managing multiple clients and internal teams.
Benefit:
This would allow granular access control, improve security, and prevent unnecessary workarounds like removing users from certain subaccounts entirely.
Request:
Please add the option to manage permissions individually per subaccount without impacting other subaccounts.
S
Sales & Marketing
Merged in a post:
Allow Different User Permissions per Sub-Account
D
David Muñoz Maradiaga
Currently, when a user is assigned to multiple sub-accounts in GoHighLevel, they must share the exact same permission set and access level across all of them.
This limitation makes it difficult to manage users who need different roles or visibility scopes per sub-account — for example, an admin role in one client account, but only a restricted “view-only” role in another.
Proposed Improvement:
Enable administrators to assign unique permission levels per sub-account for the same user. Each sub-account should have its own role and permissions configuration, independent from the global user profile.
Why this matters:
Agencies with multiple clients or brands often have the same team members working across several accounts, but in different capacities.
It would improve security, flexibility, and operational efficiency by removing the need to create duplicate users with different email addresses.
Aligns with enterprise-level user management standards (similar to role-based access control per workspace).
Example Use Case:
A marketing manager could have full access to automation and pipelines in one client sub-account, but only reporting and conversation view access in another — all under the same login.
M
Mariah | FG Funnels Support Team
This create an issue for service providers. Currently, the HighLevel system does not allow user permissions to be isolated on a per-subaccount basis. This means that if changes are made to the permissions on your user profile in one subaccount, those changes will apply to all subaccounts associated with that profile.
However, the user (service provider) needs their permissions to be isolated by subaccount. So, they can have full access to their own subaccount, while only having access to some sections of their client's account. So, each of their individual clients can decide which section of their account the service provider can see and make changes to.
C
Chelsea Lahey
Need this please
T
Tanya Aliza
This would also help protect our snapshot subaccounts.
W
Wan Ahmad Daniel
Currently, GoHighLevel user permissions only allow me to hide or show the entire Websites/Funnels tab.
If the tab is visible, the client has full access — they can edit, delete pages, funnels, forms, and also see internal features like “Ask AI.”
This creates serious issues for how I deliver and protect client websites.
Problem
When a client purchases a website from me, they must be able to access what they purchased.
I cannot completely hide the Websites tab, because the website belongs to them.
However, when the tab is visible, the client can:
i)Edit or delete pages, funnels, and forms
ii)Break live websites accidentally
iii)Access advanced tools they don’t understand
iv)See the “Ask AI” feature, which:
-Reduces perceived professionalism
-Makes clients think the website was “just built with AI”
-Creates unnecessary questions and trust issues
There is currently no safe middle option between full access and no access.
Requested Feature
Please add granular permission controls for Websites & Funnels, such as:
i)View-only access
ii)View & edit (content only)
iii)Restrict delete actions
iv)Ability to hide advanced tools (including AI-related features)
Separate permissions for:
Websites
Funnels
Forms
This would allow clients to own and view their website without risking damage or confusion.
Why This Matters
Protects live websites from accidental deletion
Maintains professional positioning with clients
Reduces support issues and misunderstandings
Allows fair ownership access without full backend control
This feature would significantly improve trust, safety, and professionalism when delivering websites inside GoHighLevel.
J
Josh Salazar
Running into the same issue. Please roll this out dev team!
S
Shai Edri
must have please! it even can be considered as a bug ((:
T
Tristan Stier
We need THIS!
Load More
→