Block property changes via automation/imports (manual edits only)

Hello,

I’d like to check if the following is possible in HubSpot:

We want to protect a specific field from being changed by workflows, imports, or automations, while still allowing HubSpot users to update it manually.

Use case:

If a Contact has:

Lead Status = Disqualified

Disqualification Reason = “GDPR” OR “Unsubscribe”

→ These values should be locked from any changes by automation/workflows/imports.

→ But a HubSpot user should still be able to edit them manually inside the CRM.

Is there a way to enforce this logic in HubSpot (e.g., via workflow conditions, property permissions, or another approach)?

Thanks in advance!

Hi @ASobusiak,

No, this is not possible. There are currently no settings that would allow such a configuration, unfortunately. I agree that this would be useful and you could request it in the ideas section of the community: https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas

Keep in mind that in your specific example, an unsubscribe is / should be stored in the ‘Unsubscribed from all email’ property or as part of subscription types: Unsubscribe an individual contact from receiving all email

It is not a best practice to use fields for this as HubSpot does not check fields when sending emails – it does however check against an unsubscribe as per the link above and automatically exclude a contact.

“GDPR” seems a bit vague to me as it stands for a regulation, and doesn’t detail what exactly it’s referring to. If it is referring to the legal basis of data processing, there is an equally named default HubSpot property for this.

Best regards!


@karstenkoehler wrote:

“GDPR” seems a bit vague to me as it stands for a regulation, and doesn’t detail what exactly it’s referring to. If it is referring to the legal basis of data processing, there is an equally named default HubSpot property for this.


Thanks for clarifying! :slightly_smiling_face: Could you let me know which specific HubSpot property you have in mind?

@ASobusiak “Legal basis for processing contact’s data”