Enhanced Data Privacy with Custom Field Access Control
A
Aris Gil
I'm suggesting a feature to improve privacy and efficiency. Currently, when virtual assistants access the CRM, they can see all customer information, including sensitive data. This can be a privacy concern.
My Proposal:
Let's introduce restricted access custom field folders in the CRM. These folders would contain sensitive customer information and be accessible only to specific users, like administrators or certain team members. This way, we ensure that sensitive data is only seen by authorized personnel.
Benefits:
Improved Data Privacy: Restricts sensitive information access to only key personnel.
Cleaner Interface for VAs: Helps VAs focus on relevant data without being overwhelmed by sensitive details.
Role-Based Access: Tailors data access to suit the responsibilities and needs of different users within the organization.
Implementing this feature would make our CRM more secure and user-friendly, enhancing both data protection and operational efficiency.
Thanks for considering this idea!
Log In
A
Aayush Singhal
Merged in a post:
Lockable Fields in Custom Objects
B
Brady Bell
Currently each field is open to anybody that owns or follows a custom object to edit. We should be able to lock down individual. This would be helpful for my real estate clients that want to use custom objects to manage their transactions. For example, after a transaction is started we don't want the Transaction ID to be editable.
T
Terri Adler
We need this type of security in our business as well. We need to be able to store sensitive information within our database for service to our client base (not 2 separate systems), but only specific level employees need to be able to access information like SSN and credit card data. It would be immensely helpful if we could password protect, or encrypt this within a contact's information.
P
Pallavi Kothari
Merged in a post:
Lock Custom Object at Certain Status
B
Brady Bell
We are using a multi select field to track the status of our custom object. We use it for the real estate industry. Once a transaction has been marked as closed we need to lock the custom object down to prevent a user from editing it.
K
Ken Wood
I want to be able to use custom objects as an alternative to the "Deals" object that other platforms offer. This feature is one of the requirements to make that work.
G
Gaurav Arya
Capability to allow custom objects to be edited only via workflow or API. This drastically improves capabilities and prevents accidental overwrites. It also brings external system information into HighLevel while ensuring its accuracy. Some use cases can be:
- Claim ID generated by a broker and captured by a webhook in the workflow.
- Account access status or service delivery report from an external system.
P
Pallavi Kothari
Merged in a post:
Sensitive Field Masking - SSN, DOB, etc
J
Jacob Radcliffe
We want a user permission that allows masking of sensitive fields. And then an option on a custom field to mark it as sensitive like a SSN. So if they lack a permission they see it blurred out or hidden from view. Important for HIPAA agencies that dont want VAs exporting contact lists or viewing lots of SSNs.
D
Dannielle Spencer
Lockable and restricted access to fields for sensitve information would be amazing. As an accountant I collect a lot of details on my clients that I need to truly help them and do the work that they need. However, I don't necessarily want very many staff members to have access to that information. Typically, only the manager for that specific client and myself, not bookkeepers, not sales staff, etc. Because that's how fraud happens.
As I scale my business, it's impossible to make sure that every employee is handling sensitive info in the way we intend, even though I am on top of trainings, sops, etc. I'd love for a software to be able to do this for me so I don't have to worry.
Outside of accounting, I think this would be helpful in other industries with data breaches becoming so prevalent. In accounting and similar industries there are now laws about this with significant penalties, so I'm always on the lookout for how to keep our data safe and confidential. It's a huge concern.
To use high level in the way I'd like, it would become our client database. And because of the great functionality with the custom fields, I'm able to pass off information and slice and dice it in ways that all the other softwares I've used promise to do, but fall waaaaay short on. Ideally, I want to keep any sensitive information as secure as possible by locking access to the field except for certain roles or in instances when we pass that information off to a specific form or document. Otherwise, I want to have that information on lockdown.
I'm pretty sure that none of the other softwares, even the accounting specific ones do this or do it well. But I'd love to be able to tell my clients that we are "on it" and ahead of the curve!