Users & Permissions

Roles and Permissions for Pipelines and more
I am currently using automations to manage opportunity visibility by dynamically adding and removing staff as "opportunity followers" based on the project stage. This is necessary to ensure each department only accesses relevant information. However, this workflow is fragile; it often fails to process correctly or conflicts when a contact has multiple active opportunities (addressed separately in https://ideas.gohighlevel.com/opportunities/p/make-opportunities-make-sense-again ), requiring constant manual intervention to correct access. I propose two feature enhancements to resolve this: Staff Roles/Groups: Introduce the ability to create custom staff roles (e.g., "Sales Team," "Office Support"). These groups should be selectable in automations (e.g., "Assign group as opportunity followers") to eliminate the need to manage individual users one by one. EDIT: Adding onto this first one, having the ability to have default permissions for these roles so when a employee is given one they assume the permission group tied to it (given that custom changes are not already made to the individual). A very basic version of this is already in place with the "User" vs "Admin" account type. Permission-Based Pipeline: Implement pipeline settings that allow pipelines, pipeline stages, lists, etc. to be restricted to defined roles or groups. Instead of relying on automations to add/remove followers, access to an opportunity would be automatically governed by the stage it currently occupies. For example, a "Sales Team" role could be granted exclusive view access to specific pipeline stages, ensuring that visibility is automatically updated as the opportunity moves throughout. These features would drastically simplify opportunity management, reduce the reliance on complex, error-prone automations, and provide a more secure, granular way to manage team access across the platform. Let me know your thoughts on this everyone! Thanks!
0
·
New Feature
Load More