T
Tim Colling
Right now it’s not possible to protect GHL assets and settings from being changed intentionally or unintentionally. For example, forms and surveys submissions can overwrite field values. Snapshot deployments can overwrite almost any GHL object.
We need the ability to “lock” or “protect” sub-account assets to prevent unintended updates to these (and probably other) items in CHL
  • Field values and names
-- “Standard” fields e.g., in Contacts
-- Custom fields
-- Custom values
  • Tags
  • Marketing/Emails
  • Marketing/Templates
  • Marketing/Trigger Links
We also would need workflow actions to set and release these locks