Users & Permissions

I am very frustrated that a personal calendar is created every time a user is added to an account (and also at the agency level, to every account you give them access to). This creates what my clients see as an unsecure and violation of their control on the platform. My clients do not need a VA who is building funnels to have a personal calendar, when they often do not even have access to the calendars. It makes no sense. AND the "XX's" Personal Calendar creation makes no sense overall because it literally does nothing. You still have to go in, fix the name and all the details and get it set up before you use it anyway. Please take this off to enhance the User Experience.

Recently when you guys created the "Launchpad" toggle in user permissions it automatically added the permission to all my agency and subaccount users. This is a no no. Every time High Level rolls out a new permission or changes how one works I can't have all my users getting automatic access to it.

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.

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.

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 am having issues selling sub-accounts because I have full access to the confidential data within sub-accounts. How can I turn that off? I should not be able to see the contact data from the sub-accounts unless authorized. I'm a realtor and I'm trying to sell my program but other realtors don't want to sign up because I get access to their entire database. And I should not have access to this. That is a massive breach of confidentiality.

I need to raise this as a critical issue rather than just an idea: It seems that whenever new features are introduced (or existing ones are enhanced), permissions are automatically being enabled across existing roles without the account owner being notified or given the choice. For example: We carefully roll out features like the AI Agent for clients, with strict role-based access in place. Later, we discover that team members or third-party users (who should have minimal permissions) suddenly have full access to make changes—simply because a new update gave them that ability by default. 📌 This has resulted in clients’ set-up work being disrupted multiple times a week. This kind of behind-the-scenes change creates: 📌 Operational risk (users unintentionally breaking workflows) 📌 Security concerns (granting privileges that were never intended) 📌 A heavy management burden (we have to manually re-check permissions daily to ensure nothing broke). Request: Please, moving forward, do not auto-enable new permissions across existing roles. Instead: 📌 Default new permissions to “off” unless explicitly granted by the account admin 📌 Provide clear release notes or alerts so account owners can decide how and when to adjust access Our customers are understandably upset when their workflows get disrupted, and it places avoidable strain on agencies and business owners trying to manage users responsibly. This feels like a bug in role/permission handling rather than a feature request. Thank you for taking this seriously and helping us protect both our clients and your platform’s stability.

Can we please have a toggle to turn off the "Launchpad" in either the sub-accounts (Business Profile) or in a sub-account's (User Permissions). The launchpad is great when we first onboard but becomes a massive distraction afterwards. Based on what is already in the suggested posts, this will help solve multiple other requests. Thank you dev team for reading this and I hope you have an amazing day.

Description: Currently, managing permissions for the Notes section (on contacts, opportunities, etc.) lacks the necessary granularity for effective team management and data protection. To better manage diverse teams and safeguard important information, we require finer, role-based controls over what users can do with notes. --- Problem & Use Case: Different user roles within our business require different levels of access to notes. For example: We need the ability to assign Create Only permissions to certain roles (like VAs or entry-level staff) so they can add new information without the risk of accidentally editing or deleting crucial historical notes logged by senior staff or other team members. Other team members might need the ability to Create/Edit notes to update information as situations evolve, but should still be restricted from deleting notes entirely to maintain record integrity. Full Create/Edit/Delete permissions should be reservable for administrators or specific trusted roles. Without these distinct levels, we either grant too much access (risking accidental data loss or unauthorized modification) or restrict users too much, hindering productivity. This also makes it harder to maintain data integrity and accurate historical records. --- Proposed Solution: Please implement the following distinct permission levels that administrators can assign to users specifically for the Notes section: Create Only : User can add new notes but cannot modify or delete any existing notes. Create/Edit : User can add new notes and edit existing notes, but cannot delete notes. Create/Edit/Delete : User has full control – allowing adding, editing, and deleting of notes they have access to view. --- Benefits: ✅ Improve security and data integrity by limiting modification/deletion rights. ✅ Prevent accidental loss of important client history or internal communication. ✅ Empower administrators to configure user access precisely according to job responsibilities and trust levels. ✅ Enable more secure, effective, and clearly defined team collaboration within HighLevel. Implementing these granular permissions would be a valuable improvement for managing teams and protecting data within the platform.