Users & Permissions

It'd be really helpful if we were able to group together a segment of Locations (eg. all of our team-related accounts, or clients-only) in our Agency so we could grant them all access to a specific Custom Menu button.

We use signatur because its a great feature that allows easy bulk for sender info for all our emails. But if we design our emails with another color and has a picture of the therapist, it dosent work. We need a proper designer for signature.

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.

We're encountering a specific need among our Virtual Assistants (VAs) who manage multiple client accounts through our White label SaaS. These VAs, although not directly affiliated with our SaaS, have started utilizing us and bringing their clients over due to its comprehensive feature set. Currently, VAs are signing up for sub-accounts for themselves and then we are assigning access to their clients’ accounts. However, this setup presents a few challenges that could be addressed through something like a "Sub-Agency Account" User level: Default Sign-In Page: Our VAs are often working across numerous client accounts, and currently, when they log in, they are directed to the last account they accessed, which lacks a central "home base." It would be highly beneficial for their default login to be their personal account. This would act as a guardrail against accidental actions in a client’s account, such as sending emails or making edits. Ideally, the account switcher would offer two options: A) "My Account" for their personal use, and B) "Client Accounts," which would lead to a list of managed sub-accounts they can select from. This additional layer would help prevent accidental transitions into client accounts. Template and Workflow Management: Due to the nature of their work, VAs often use the same templates and workflows across different client accounts. At present, they must recreate these templates in each client's account, which is inefficient. A feature allowing a "Sub-Agency Admin" to share templates directly to their managed sub-accounts through a simple checkbox list would streamline this process. This feature should be visible only to the "Sub-Agency Admin" role and show only the sub-accounts they manage. Alternatively, provide permissions for VAs to create and share snapshots within their managed accounts. Essentially, it would enable them to select content for snapshots and choose the destination account for installation seamlessly. This is the same was above just for multiple assets at a time vs sharing an email, a workflow, etc. Additional Context: This functionality is particularly crucial for network marketers, as having duplicatable systems ready for team members is a significant advantage. Implementing these features would not only enhance user experience but also strengthen Our capability as an integrated solution for network marketing teams.

Objective: To implement a more granular permissions system for account settings in Go High Level, allowing admins to individually control access to specific settings (e.g., calendar settings) rather than a single toggle that enables or disables all account settings. Feature Description: Create distinct permission toggles within the user roles and permissions settings that allow admins to enable or disable access to individual components of account settings. For instance, calendar settings should be separate from other account settings, providing more control over user permissions. Implementation Details: Granular Permission Toggles: Introduce separate permission options under the “Account Settings” category, such as: Calendar Settings Access: Control over calendar visibility and updates. Notification Settings Access: Control over notification preferences. Profile Management Access: Control over personal profile details. Integrations Access: Control over third-party integrations. User Interface Adjustments: Update the permissions management interface to include checkboxes or toggles for each specific setting under account settings, allowing admins to customize user access based on their roles. Dependency Management: Ensure that if an individual setting is disabled (e.g., Calendar Settings Access), the user cannot view or modify their calendar settings. This should be clearly indicated in the user interface. Feedback Mechanism: Provide a notification or message to users when they attempt to access a setting they do not have permission for, explaining that the restriction is based on their role permissions. Benefits: Increases security by ensuring users only have access to the settings relevant to their roles. Enhances flexibility for organizations by allowing tailored permissions based on user responsibilities. Reduces the risk of unintentional changes to important settings, leading to better account management.

Whilst the recent enforcement of 2FA (via email) is a welcome addition to the security of High-Level, email based 2FA is unfortunately one of the least secure 2FA methods. So, please add more 2FA options. Including at a minimum TOTP codes (a global standard) that people can use through whatever TOTP App they use. (E.g. Authy, Duo, Google Authenticator, Microsoft Authenticator etc). And at the same time, please: Allow an agency to select what 2FA options they will allow to be used across their clients. Allow Admins of a sub-account to also have this level of functionality to select what 2FA options users in their Sub-Account can use IF the Agency gives it to them.

Would be great to enable (or disable) new features for users and add a filter based on permissions to certain features. Current Painpoint/ Workaround: When HL releases a new feature, we have to manually update 100's of subaccounts.

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.

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

Objective: To add an optional permission setting that allows admins to restrict user access to the billing section within the company profile, providing more control over sensitive financial information. Feature Description: Introduce a user-specific permission toggle within the Go High Level admin settings labeled “Billing Access.” By enabling this, admins can prevent selected users or roles from viewing or accessing the billing section, which includes subscription details, invoices, and payment information. Implementation Details: Admin Settings Update: Add a new permission toggle under user roles/permissions labeled “Billing Section Access.” When disabled, users assigned to this role will not see or access the billing section in the company profile. User Interface Adjustments: Update the user interface so that, for users with restricted access, the billing section is either hidden entirely or grayed out with a lock icon to signal restricted access. Notification: Provide a tooltip or notification for restricted users indicating that the billing section is not accessible due to role permissions set by the admin. Benefits: Enhances security by preventing unauthorized users from viewing sensitive billing information. Offers flexibility for organizations needing stricter access control over financial data. Aligns with best practices for data privacy and financial information security.