HubSpot Ideas

ilonamiller

Create a setting to turn off autosave feature

Per this thread, I am requesting that you provide us a setting to turn off this feature. It would be ideal if we could turn this off at either at the individual user level or at the admin level. This autosave feature is extremely disruptive to our workflow.

HubSpot Updates
Delivered
May 07, 2025 12:07 PM

In Planning
April 28, 2025 08:41 AM

Hi everyone! My name is Hallie, and I'm an Associate Program Manager on our CXM team here at HubSpot.

Our product team wanted to share an update with you all! They're actively developing an 
'opt out' toggle for autosave. This will be available as a configurable setting for admins. If enabled, it will require users to explicitly click a Save button when editing properties in the CRM UI.

Autosave will remain 
ON by default unless an admin chooses to activate this opt-out settingOur goal with this solution is to offer immediate relief while we consider enhancements to the core problems identified by users (e.g., automation triggers).

 

Since it's actively being developed, there isn't a hard deadline of when this will be available. However, we are planning to have this available in the coming weeks (aiming for mid-May). I will be sure to update this post as soon as we have confirmation the option is available for our customers. Thanks for all of your patience & for sharing valuable feedback on this feature! 

53 Replies
AustenOzzy
Participant

This is the main thing that is stopping an entire trade portal from launching.  Reps can create deals, which then trigger several integrations when those deals are set to 'closed won'.  It's too easy to do that and then realise something is missed - meanwhile, money is taken, orders are sent for fulfilment, etc etc.  Please give the option to bring the save button back.  😞

SKurtz
Member
Hi HubSpot Product Team,
I'd like to suggest an improvement regarding how property changes are handled in the system—specifically, the autosave functionality when editing properties.
Currently, autosave is triggered instantly upon any selection or change, which often leads to unintended issues:
  • Incorrect selections are immediately saved, increasing the risk of errors that can affect reporting and data accuracy.
  • There is a noticeable lag as each change is saved in real time, which slows down productivity—especially when multiple properties need to be edited quickly.
To improve the user experience and reduce these productivity disruptions, I recommend either removing the autosave feature or, ideally, making it optional or user-configurable. Allowing users to manually save once they’ve finalized their edits would give more control, reduce errors, and enhance performance.
Thanks for considering this suggestion!
hhiggins
HubSpot Product Team
RFransway
Contributor

Only pro and enterprise... come on.  🙄

cecilia-thespot
Contributor

THANK YOU, @hhiggins AND TEAM!! 

I'm usually a grump, but you brought a smile to my face today. We appreciate you hearing us and delivering quickly!

cecilia-thespot
Contributor

Thank you so much to @hhiggins and team for delivering this so quickly!

We appreciate that you listened and gave a solution!

Support_K
Participant

We sincerely appreciate Hubspot Team's swift resolution of the issue we faced.


Our sincere thanks to @hhiggins and everyone who contributed to making this solution as quick as possible.

MHolzer
Contributor

It's absurd that customers are forced to bear the burden of HubSpot developers' lack of oversight and negligence in product design.
Features should be thoroughly tested and collaboratively reviewed across all internal teams—UI, Workflow, Reporting, and more—before release.
It is unacceptable to release features that are poorly conceived or fail to function cohesively within the HubSpot system, expecting customers to effectively "test" them.

MHolzer
Contributor

@hhiggins  this feature is not even close to delivered 

  1. Hubspot releases a feature that fails to integrate with their own workflows and the triggers of that workflows!

  2. The community is outraged because this feels like it wasn’t properly tested—or even tested by people who know how workflow trigger work.

  3. Now you added a button to revert changes after listening to the backlash, but it’s half-baked.

The UNDO button is still there even after switching to manual save changes....

Do you even understand the core issue with autosaving properties?
How does it make sense to implement an UNDO button without thinking about workflow triggers?
At the very least, implementing a grace period for workflow triggers is essential. That’s product development 101.

It literally makes no sense to have an undo button when the saving of a property can still trigger a workflow even tho u pressed UNDO!!!!

It genuinely feels like the team shipping these features don’t fully grasp how HubSpot workflows work.

This lack of understanding is frustrating for those of us who rely on these tools every day.
This isn’t just a missed detail; it’s a fundamental oversight that damages trust

GM
Member

Why is the toggle only available for Pro and Enteprise customers only. We have a starter account and have had to turn off all our triggers, which are business critical, as autosave is causing chaos with our zapier integrations

ea82z
Member

This change, apart from breaking existing processes, makes using HubSpot much more risky and error-prone as the likelihodd of unwanted changes being saved skyrockets! It’s baffling to see such careless design decisions in business software. Reliability and a safe, predictable UI/UX are not optional—they’re essential. This feels like a script-kiddie move, not the behavior of a serious business software vendor. My trust in HubSpot has taken real damage.

LAnderson22
Participant

We were also experiencing workflow issues, so we've requested the toggle to turn it off for now.  Having said that, we want to express to HubSpot dev that if this toggle is ever sunsetted, they need to ensure that the auto-save functionality allows for multiple fields to get updated at the same time, as otherwise it casues issues with conditional field relationship types and workflows.  

RebeccaPSE
Member

Glad to see we now have a toggle! Just as a point of feedback though - I see it's only available to Pro and Enterprise customers. Is that also true for conditional logic? The auto-save has made the conditional logic moot since it saves the field whether the additional required properties are updated or not.