Users & Permissions

Currently, we are only allowed just two main user roles—Admin and User. In our business model, we have sales reps who manage sensitive, high-net-worth clients. Some workw exclusively with these clients, and we need to ensure that only he and the admins can view and manage those particular contacts. On the other hand, we also have a broader group of salespeople who handle general incoming leads. These leads go into a user we created called "house account" and then i have an automation that assigns new contacts to that user. In that same automation, i add all the sales staff as contact followers so they can still be assigned tasks and see acitivy. While this workaround helps us, it also leads to intermittent issues and additional complexity. For instance, we recently had a scenario where a contact assigned to the house account had a task created that was assigned to a sales person (different user), but due to permission limitations, when the salesperson with the assigned task viewed his tasks screen from the contacts module, the associated contact field wasn’t visible to that rep. So there was no actionable way to conduct that task. Somehow that was eventually resolved on its own. Currently, contact followers cant see "house account" conversations, which created a big problem with one of our clients. It highlighted how fragile these workarounds can be. In other words, we’re relying on automations to manage workflows that would be much simpler if we had more nuanced user role permissions built into the platform. We are also sensitive to protecting a certain salesperson's contacts and have had staff in the past reassign contact ownership to themselves. Assigning the sales staff as followers allows them to see the contact, but not change the ownership, which currently works as a solution, but it is creating all the problems that i mentioned above. We believe that adding more granular permission controls, or allowing subaccounts to create their own user roles with more options for permissions with contact would benefit many businesses like ours. It would reduce the need for these complex workarounds and ensure a smoother experience.

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.

I need a way to limit the number of employees that a sub-account owner can add to their account AND even prevent a sub-account owner from adding employees all together. I would also like the option to charge an incremental amount to the sub-account owner by how many employees they add. Even further, by including these settings in a snapshot, it would help automate the process of granting user permissions based on the SaaS plan or snapshot selected. By adding more granular control of 'User Permissions' within various sections and items under, this could be achieved. For example, the User Permissions for Settings could have sub settings to check on or off each of the items under each category. For example within Settings, we would have a toggle for each of the following items: MY BUSINESS Business Profile My Staff Pipelines BUSINESS SERVICES Calendars Phone Numbers Reputation Management Profile OTHER SETTINGS Custom Fields Custom Values Domains Media URL Redirects Integrations Email Services Conversation Providers Tags Labs Audit Logs

I would like to request an enhancement to restricts users to be able to see the previous conversations with the contacts from other users as well as the notes of other users, tasks of other users and anything related to other users. Please vote this.

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.

Split View and manage for ALL existing permissions. Especially tags as we have users accidentally creating tags from contact records all the time and it is a lot of work to clean it up. Also allow us to determine what Admin and User can do. An example is we would like to give our users access to upload their own leads. But that requires admin access which we do not want to give them.

Small business owners also employ people and provide salary to them. If we add the HR features such as employee timesheet tracking and payroll processing for team members in Go high level, then our platform will be even more appealing to small business owners who wants to use our platform.

Create option in Agency company settings for agency admins/owners to turn on or off that is: "Allow all users to toggle light / dark mode individually." That way, this option is off by default, giving all GHL agencies time to write code for whichever mode they've not got code for. Turn current Custom CSS box in Agency company settings into "Custom CSS for light mode" ... and then "add Custom CSS for dark mode" right below it. Provide light/dark mode toggle for all users under "My Profile" or in upper right hand corner, similar to the light/dark mode toggle used in Community feature. Only make available if option in point #1 (above) is turned on by agency admin/owner.

Currently, users are all individuals. In the workflow (see attached image), when I want a lead assigned to someone from the sales team, I need to manually list every person in the sales team in the workflow. If the sales team are part of several workflows, this is a lot of work with a risk of error. Creating a team of users, with the option of a user to live in multiple teams, means the workflow could select SALES TEAM, instead of each individual in the team. This means, when the members of the sales team change, only the SALES TEAM bucket needs its contents updating, instead of going into every workflow where members of the sales team are selected and making changes one-by-one, with an increased chance of errors.

Currently the permissions are tagged to email however it should be at different sub account level. One user can be a admin at one sub account while normal user in other sub account. which is not possible at the moment.