Make Custom Fields Lockable (At An Individual Level)
P
Padraig Jordan
There should be an option to make certain custom fields lockable once information has been input (manually or through an automation).
There are a lot of use cases for this but the most obvious one for me is to lock the custom attribution fields we have created (not the standard GHL ones) so that this information cannot be updated after it is entered.
In my use case we track both first and last attribution and I want the "first" fields to be locked once info have been input so that no team member or automation can update this after the fact.
The reason the this is important is that:
A. I want accurate data, and...
B. I want to make sure no team member can edit these as my team are compensated on commission based on where the lead was originally generated from.
If you would like any further info on this shoot me a message and I will happily get on a call to walk the team through my personal use case.
Log In
F
Farhad Moradi
Yes please. I need this badly.
J
Jen Anne
Yessss! Please!!!
Although this is 2.5 years old....so probably not happening at this point....
J
Jackie Cabrera
+1 This is a critical feature for any CRM. Because our data is tied to workflows and triggers via specific tags, custom fields.. giving everyone full access to contact's data creates a high risk of accidentally disrupting the entire system. We really need the ability to restrict and lock some fields depending on the role permission.
F
Francisco Ferrari
I've been trying to lock some fields inside the opportunity cards, but currently it seems only the “Opportunity Name” field can be locked.
I’m writing this feedback to request the ability to lock other fields inside the opportunity card as well — similar to how the Opportunity Name works. Right now, every time I log in, I have to manually manage and reposition the fields inside each opportunity card.
It would be great if these fields could stay fixed (locked) even after logging out, so that when I log back in, they remain in place without needing to reset them each time.
This improvement would really help streamline workflows and keep opportunity management more consistent across sessions.
Thank you for considering this enhancement!
J
Jared Schoolcraft
I think it’s insane we do not have the ability to limit certain users from changing core fields or custom fields. Often times administrative or upper management does not want data being accidentally changed or corrupted from changes. We need the ability to make fields read only
J
John Byrd
Make it Lockable, with a notification for the field of what its locked, able to give warnings as to the consequences of changing the field
S
Scimon Hyatt
+1 this would be valuable. Not just to have lockable fields, but have fields be hidden from "User" types, or allow fields to be edited or not based on user type. (User/Admin)
M
Mark Roberts III
Would love to see the ability to lock custom fields as read only, this way a GHL user can view the data in the field but not accidentally change it. This becomes important if custom field data is generated and/or updated from a third party app and sent by a webhook. For example a custom field of QuickBooks_Client_ID. This should allow a GHL user to view this item but never be able to update the value. However, if Quickbooks updated this value, then it should be able to call the webhook and update the custom field value.
Attached is an example screenshot of how I envision it looking to the GHL user setting up custom fields.
Thank you for the consideration.
Photo Viewer
View photos in a modal
A
Adam Campbell
A feature like this would elevate High Level to be taken seriously as a CRM.
C
Chris Pope
Come on guys this is a fundamental requirement of any CRM!
Load More
→