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.
Log In
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.