I would like to propose more specific user permissions for marketing assets and the Social Planner.

"Use-Only" Permission for Marketing Assets: Create a permission level that allows users to use assets like Email Templates, Snippets, Brand Boards, and Trigger Links in their campaigns, but prevents them from editing or deleting the master versions. This helps maintain brand consistency while still empowering users.

Individual Social Planner Integrations: In the Social Planner, each user should only be able to see and access their own connected social media accounts. They should not see the integrations of other users in the same sub-account. This would improve security and prevent accidental posts to the wrong accounts.

Payment permission is still not right.

Why when someone is an account admin, they are an account admin with the same permissions for every account attached to their login.

I have a sales person who has access to multiple sub-accounts, but he shouldn't have full admin permissions to any of those accounts, only to his. But when I change his permissions, it changes for all his accounts.

This makes no sense at all.

We are in need to have different roles and permissions for users based on the subaccount that they are accessing without having to create a new user account.

For example, we have users that use our white label for their personal business and we want them to have full admin access. That same user may admin another subaccount with less accessibility. The same user may develop on on an agency subaccount and we would want significant restrictions to prevent them from seeing (payments) and editing websites, automations etc.

Pipelines and Dcouments need more granular permissions. Any basic CRM has this

This!

While the developers are at it, could you please allow granularity down to the [Fields] level for a [Support] role (could be another [User] role sure)?

I created another change request prior to reading this - the main consideration is to enhance data security and privacy by hiding/showing certain fields and functionalities for said [Support] role.

Enhance Data Security & Privacy - Add [Support] role

Enhance data security and privacy by adding a [Support] role to the current limited roles of [Admin] and [User], and giving Agency Admins the ability to hide/unhide certain fields and functionalities for said [Support] role.

Generally speaking, [Support] staff design, implement and debug solutions only, and do not need access to end-clients' private data like [First Name], [Last Name], [Name], [Contact Number], [Email], [Calendar] and [Address] etc, and rich functionalities like [Import], [Export] CRM data.

What [Support] staff need are certain functional fields like [ContactID], [Calendar.EventID], [PaymentID] etc and the ability to access as-needed functionalities like [Automation], [AI] etc and when bugs are reported and specific needed modules/ data may be selectively shared.

In other words, [User] role is for our clients and their users, [Admin] role is for our agency's OIC and our clients' OIC, and [Support] role is for our agency's and/or external 3rd party backend developers.

Such a demarcation will allow for greater scalability for agencies who would like to engage external/ remote backend help and have chosen not to do so due to data privacy considerations.

and permissions across sub accounts so they have different access on different accounts

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!

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).

Option to deploy directly at agency expense.

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