User Permissions - More Granular
in progress
A
Anthony CRM Admin
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
Log In
J
Joe Chew
seen the idea had been proposed since dec 2022. wondering when would GHL be implementing this idea.
J
Joe Chew
Key components and desired behavior:
Team Creation & User Assignment: Ability to create distinct "Teams" and assign individual users (staff/agents) to one or more Teams.
Team-Based Record Ownership/Association: Allow records (Contacts, Opportunities/Deals, etc.) to be associated with a specific Team, in addition to individual user assignment.
Role-Based Visibility by Team: Introduce a permission setting or role configuration that restricts a user's view of records based on their Team membership.
Manager-Specific Visibility: Enable a "Manager" role permission where the user can view all records associated with or owned by any user within their assigned Team(s).
Strict Cross-Team Restriction: Crucially, ensure this Manager role is strictly prevented from viewing any records associated with or owned by users in Teams to which the Manager is not assigned.
This feature would provide true data isolation between teams for management roles, enhancing security and aligning data access with organizational structure, beyond just filtering capabilities.
A
Alastair Mackenzie
Any updates on this, definitely needed and specifically separate out view only read access to manage per object
M
Marko Ivkovic
Access Rights Architecture Example from other CRM with advance setup
- Access Levels (Permissions)
Each object (Contact, Pipelines + Stage, other models with data view/entry) can be configured with the following rights:
- View (Read)
- Add (Create)
- Edit (Update)
- Delete
- Export / Import
- Move to Stage (Pipeline-specific)
- View on Kanban / Stage Totals
- Roles
Access is granted per role - YOU CAN CREATE ANY ROLE you want:
- Full Access
- Manager
- Operations Level 1 (customzible)
- Operations Level 2 (customzible)
(custom roles can be added)
A
Alastair Mackenzie
Marko Ivkovic this is spot on, can we ensure this is incorporated to the build?
M
Marko Ivkovic
Alastair Mackenzie this is how system should be build in order to have full controlment. Unfortunatelly, I am not GHL developer. I have provided sugestion here.
B
Books Open Media .
This really needs to hurry up ...
B
Basan Subedi
Very CRUCIAL feature. My Client want to give access to their staff just Documents & Contracts and not the invoicing/payments, but currently it's not possible. I'm eagerly waiting for extensive permission settings for users.
R
Romulo Pereira
CRUCIAL! Granular Access to Automations/workflows:
Let the subaccount admins choose wich automation or automation folder(s) the onboarded user may have access to.
Some of my clients need their users to add contacts to pre-built automations, and having the options to restrict which automation/workflow they can add contacts to will prevent misuse of the platform and acidents.
Looking forward to this one BIG TIME! 🤞�
R
Ryan Mayiras
Would love the ability to restrict users from customizing their own email signatures.
D
Drew Carmichael
Is this considering the opportunities window, having pipeline hiding? So some users cannot see a pipeline?
D
Dereck Johnson
Payments:
- View Only
- Assigned Data Only (Can only see payments/invoices associated with contacts assigned to that user.)
Load More
→