Users & Permissions

Remove Launchpad from User. Currently Users can go in and configure account level stuff in the launchpad, such as adding services like WhatsApp, or adding team members, etc.. This can be problematic, as these types of users should have no ability to manage account level, stuff, or we should be able to control it in roles and permissions.

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

There should be an option to make certain custom fields lockable once information has been input (manually or through an automation). There are a lot of use cases for this but the most obvious one for me is to lock the custom attribution fields we have created (not the standard GHL ones) so that this information cannot be updated after it is entered. In my use case we track both first and last attribution and I want the "first" fields to be locked once info have been input so that no team member or automation can update this after the fact. The reason the this is important is that: A. I want accurate data, and... B. I want to make sure no team member can edit these as my team are compensated on commission based on where the lead was originally generated from. If you would like any further info on this shoot me a message and I will happily get on a call to walk the team through my personal use case.

Despite turning all permissions off, users are able to access other user's information, including booking appointments on other user's calendars and blocking off their times when calendar permission is enabled. Furthermore, user has access to dialer pad at the top right which can result in misuse and abuse, depending on user's role. There are other bugs as well such as UI bugs. I've attached screenshots. Please fix these privacy bugs at your earliest convenience.

I'm so surprised this isn't a feature. There should be an option to hide custom menu links for certain users in sub accounts. Literally just need to add a new tab for 'custom menu links' that can be toggled on and off.

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.

Ability to track email & sms sent as internal notifications seamlessly within the highlevel platform.

When a user is set up as an admin for either the agency or as a user for the sub-account, they get all of the notifications from that account. For example, all agency admins get an email notification that a new sub account was created. Is it possible that the agency can set which admins are allowed to get notifications? It seems that not all admins should be receiving information about the accoount.

Ability for admins, or at least agency owners, to see user activity (e.g. login, logout, WF updates, site updates, etc.). Important to see which users are engaged and which are dormant. Bonus: WF trigger on user engagement level, i.e. if a user's engagement level drops below x or rises above y, etc.