Users & Permissions

If we could create a custom field for team members (users) this would be MASSIVE. Means we can have way more flexibility in cycling users in campaigns (dynamically insert more things other than phone, email, signature, calendar).For example, this would also solve the problem I submitted in these ideas: https://ideas.gohighlevel.com/ideas/HIGHLVL-I-1308https://ideas.gohighlevel.com/ideas/HIGHLVL-I-1253A custom field for 'custom user calendar' would solve both of these. This is also a pathway to round robin cycling through calendars - the round robin would be done at the point they enter the campaign! HIGHLVL-I-1330

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

Description 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.

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.

Currently, GHL limits accounts to a single SSO provider configuration. This creates limitations for agencies with diverse client needs. Use Case: Agencies needing different SSO providers for different client teams White-label agencies serving multiple enterprise clients with their own identity providers Organizations using multiple authentication systems (Google Workspace, Azure AD, Okta, etc.) Requested Feature: Enable multiple SSO connections simultaneously, allowing different sub-accounts or user groups to authenticate through different identity providers. Benefits: Greater flexibility for enterprise and white-label scenarios Support for multiple enterprise clients requiring their own SSO Better scalability for growing agencies Current Limitation: One SSO provider per account forces password-based authentication or inefficient workarounds.

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.

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.

The ability to create custom fields/values for our users. Our team members have unique links for their clients, such as an application link that is tied specifically to that team member. We're currently having to make separate emails with their link for each user. Compared to making one email that has a link with the value of {{user.unique_link}}.

Objective: Improve metric tracking, lead distribution, and internal communication among user groups within the platform. Current Problem: Currently, GHL only allows the addition of individual users without the ability to organize them into teams. This limitation impacts: Group Metrics: It’s impossible to analyze conversion rates, performance, or productivity by team (e.g., sales team vs. support team). Uneven Lead Distribution: Leads are assigned to individuals, not teams, which can overload some users while leaving others underutilized. Fragmented Communication: There’s no way to send targeted notifications to specific groups (e.g., alerts to the sales team about hot leads). Proposed Solution: Introduce a "Teams" feature within GHL, with the following functionalities: Team Creation Hierarchical Organization: Allow admins to create teams (e.g., "Sales SP", "24/7 Support") and assign users to multiple teams if needed. Customizable Permissions: Define access levels by team (e.g., sales team can edit pipelines, marketing team can only view reports). Team Metrics Custom Dashboard: View total conversion by team (e.g., how many leads from Team X became customers). Compare performance between teams (close rates, response times, etc.). Filter reports by team for strategic analysis. Automatic KPIs: Generate metrics like "Team Conversion Rate" or "Leads Assigned per Team" in charts and tables. Lead Distribution to Teams Automated Rules: Distribute leads evenly among team members (e.g., round-robin). Prioritize teams with lighter workloads or higher conversion rates. Assign leads based on tags or specific criteria (e.g., SP leads → SP sales team). Workload Balancing: Prevent overload by monitoring how many leads each team is handling. Internal Notifications by Team Targeted Alerts: Send real-time notifications to entire teams (e.g., "New urgent lead for the sales team"). Integrate with channels like Slack, email, or push notifications within GHL. Automated Reminders: Notify teams about pending tasks (e.g., follow-ups for unattended leads). Strategic Importance for GHL: Scalability: Larger businesses need to manage multiple teams without losing the big-picture view. Decision-Making: Team metrics help leaders identify gaps and reallocate resources effectively. Customer Experience: Evenly distributed leads are attended to faster, boosting satisfaction. Competitiveness: Platforms like HubSpot and Salesforce already offer this feature – GHL needs to keep up. Example Use Case: A marketing agency with 3 teams (Sales, Onboarding, Support) would use GHL to: Measure which team converts the most leads into meetings. Distribute 100 leads/day evenly among 10 sales reps. Send an automatic alert to the support team when a client opens a critical ticket. Technical Implementation Suggestion: Simple UI: Add a "Teams" section in the settings menu, with drag-and-drop user assignment. APIs for Automation: Allow teams to be used in workflows (e.g., "Send lead to Team X if tag is Y"). Integration with Existing Features: Link teams to pipelines, calendars, and campaigns. Why This is Urgent: Businesses are migrating to GHL for its flexibility, but the lack of team management limits its use for medium/large organizations. This feature would transform GHL into a truly competitive all-in-one platform.

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