Users & Permissions

Granular, Role-Based Permissions Needed for Notes Section
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.
7
📌 Add Role-Based Permissions + Team Management for Marketing Teams in Sub-Accounts
GoHighLevel currently handles user permissions individually within each sub-account — with Admin and User types, and manual permission toggles. As marketing agencies, multi-client setups, and education businesses with internal marketing teams grow, this gets tedious, prone to human error, and limits scalability. We need a smarter, team-oriented permission system. 🎯 Feature Request: Marketing Teams + Roles System 📌 Roles Predefined permission profiles like: Marketing Admin Marketing Manager Campaign Specialist Content Creator Ads Manager Each Role would define: What areas they can access (CRM, Conversations, Opportunities, Campaigns, Ads, Reporting, etc.) What actions they can take (View, Create, Edit, Delete) What records they can access (All, Owned, or Team-based) 📌 Marketing Teams Groups of users organized by team responsibilities and roles. Example: “Facebook Ads Team” → 3 users with the Ads Manager role “Lead Nurturing Team” → 2 users with the Campaign Specialist role “Marketing Managers” → oversight across all teams Teams can be assigned to: Pipelines Ad Accounts Campaign Projects Automations Opportunities Dashboards Leads and opportunities should be assignable to Marketing Teams as well as individual users. ✅ Why This Matters 🚀 Faster onboarding: Assign a role, drop them into a team 📊 Easier scaling: Manage permissions by role or team, not one by one 🏢 Multi-client and agency ready: Control who works on what without risking account-wide access 📈 Cleaner reporting: Track both individual and team marketing performance 🔒 Better security: Consistent, reliable permission structures, reducing errors and overexposure 📊 Comparison to Current System: Current GHL User-level manual permissions No teams, only individual users Lead/campaign assignment to individuals only User-based reporting only VS Proposed System Role-based permissions with inheritance Group users into Marketing Teams (e.g. Ads Team, Nurturing Team) Assign leads, opportunities, and campaigns to Teams Individual + Team-based performance reporting
0
Load More