Granular, Role-Based Permissions Needed for Notes Section
C
Charles Higgins
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 Onlypermissions 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/Editnotes to update information as situations evolve, but should still be restricted from deleting notes entirely to maintain record integrity.
- Full Create/Edit/Deletepermissions 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 deleteanyexisting 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.
Log In
K
Keith Besherse
Chase Buckner, this is the concept we mean when we say granular permissions. Not just access/no access to feature areas but limitations/controls on what the user/user role can do within that feature.
D
Davene Januszewski
That would be great but I believe the unsubscribe issue is far more important there are leads on many different products and workflows and if the unsubscribe from one they not longer get any correspondence thats a problem
K
Keith Besherse
Davene Januszewski that is a different ideas board suggestion.
Shaun Clark has told us repeatedly that, because developers don’t work on projects outside their team, the teams can work on many priorities simultaneously.
D
Davene Januszewski
Yes thats simple to understand so don't waste anymore time trying to help me. EVERYONE in GHL needs to know that that is the top priority not this stuff. But Mahalo for the effort
D
Davene Januszewski
Keith Besherse I was there before here but mahalo