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
Jatinder Palaha
and permissions across sub accounts so they have different access on different accounts
B
Bobbie Sullivan
I agree with Anthony, the CRM admin. I’m working on a task that involves restricting access to specific information for employees in various departments. For example, an employee at a company should not be able to access another employee's HR records, except for those in the HR department. Being able to specify which “Custom fields” are viewable by different departments under “Contacts” would be a game-changer. A simple dropdown that allows selecting a group or department to enable “view” and “edit” rights for that field within the contacts section would be ideal. Thanks!
S
Sebastian Christ
We want to create an account that can only accept payments via the LeadConnector App. (Pay by Phone)
But currently this user can still see all contracts (both in Web and App).
K
Keith Besherse
Option to deploy directly at agency expense.
K
Keith Besherse
Granular permissions for domain purchases. Limit which account admin(s) can purchase additional domains. https://gokollab.com/highlevel-town-hall-community-q956ob/home/posts/68ac8d535cb439b8b9c5856e
H
Houtan Hormozian
I’d like to request a change in how new roles and permissions are handled during software updates and releases. Currently, whenever new roles or permissions are introduced, they are automatically assigned to all existing users. This requires me to manually go through each user one by one to remove any permissions they should not have, which is extremely time-consuming.
Could you please adjust the system so that new roles and permissions are not automatically granted to existing users, or provide an option to control this behavior?
Thank you for your help.
K
Keith Besherse
This is a very astute observation. HighLevel, we know you are proud of your new features. But the users are our customers. We know what they are ready for (or not). It is hard enough to get them using a limited feature set, adding more complexity only increases friction.
E
Esteban Méndez S
We also need to set the permissions in the SAAS: https://ideas.gohighlevel.com/users-permissions/p/automatically-restrict-user-permissions-with-saas-account-creation
L
Laura Timbrook
we need more granular permissions across sub accounts if a user has mixed access from sub account to subaccount. For example SubAccount1 they need Admin access but for SubAccount2 they need just user
T
Tom Houghton
Permissions should be able to be named for a specific type of user. For example, a "Sales" role could have one type of permissions versus a different type of role in the system. Instead of them being labeled "Admin" or "User" and only having those 2 choices.
A
Alannah Dance
have Store as a separate permission under Sites
Load More
→