Editing a deal property from the card

Who can use it. Staff, on any deal page. Owners choose *which* properties can be edited, in Settings → Deals & pipeline → HubSpot → Deal Card Layout.

What it's for

The About this deal card shows what HubSpot holds for a deal. Until now, fixing a typo in the scope of work or filling in a budget that came in over the phone meant leaving Summit, finding the deal in HubSpot, editing it there, and waiting for the next sync. This lets you do it where you're already standing.

How to use it

1. An owner opens Settings → Deals & pipeline → HubSpot → Deal Card Layout and ticks Editable next to each property the team should be able to change.
2. On a deal page, those properties now show an Edit link next to the value.
3. Click Edit, change the value, Save. The new value goes to HubSpot and the card updates immediately.

Good to know

• Nothing is editable by default. Every property stays read-only until an owner ticks it. That's deliberate: HubSpot refuses changes to properties it calculates itself (a deal's created date, its last-modified date), and Summit can't always tell which those are, so the safe answer is to let you decide.
• If HubSpot refuses the change, you'll see why. The value on the card doesn't change, and the failure is recorded in the sync log alongside every other HubSpot write.
• A property you've never used still shows up if it's marked editable, as a dash with an Edit link. Otherwise setting it for the first time would be the one change you couldn't make from here. A property your HubSpot portal doesn't actually have gets no Edit link; there'd be nothing to save it to.
• File properties can't be edited here. They hold uploaded files, not text, so they stay read-only however the layout is configured. Use HubSpot for those.
• The deal's pipeline and stage can't be changed here. Moving a deal to a different pipeline makes HubSpot pick a new stage for it, which Summit can't predict. And moving a deal between stages isn't just setting a value — it's what starts the automations, reminders and status changes attached to that stage, and only certain moves are allowed in the first place. Editing the stage as if it were a text field would skip all of that, so neither property gets an Editable tickbox or an Edit link, whatever the layout says. Change a deal's stage or pipeline in HubSpot; Summit picks the move up on the next sync.
• Amounts have to be numbers. Typing anything else into the deal amount is refused before it reaches HubSpot, so nothing is half-saved.
• You're editing HubSpot, not a copy. The change is written to the deal in HubSpot; Summit's card is updated to match straight away so you're not left looking at the old value.
• You get the right control for the property. A yes/no property is a tick box, a date is a date picker, a dropdown is a dropdown of its real options (multi-choice ones get a tick box each), and a number or amount is a number box. Summit uses HubSpot's own type for the property, so what you pick is what HubSpot accepts, with no retyping an option name and hoping it matches. Where HubSpot gives Summit nothing to go on, you get the plain text box as before. File properties can't be edited here at all.
• A value the control can't show is never quietly replaced. If a deal is carrying something that isn't really a date, a number or a yes/no (a stray import, an old sweep), you get a plain text box holding the value as it stands, with a note saying so. Fix it or clear it there. The point is that opening the editor, or saving some other field on the card, can't turn that value into a blank or into "No" behind your back.
• A date your region skipped is refused, not nudged. A handful of places have lost whole calendar days to a time-zone change (Samoa never had 30 December 2011). Picking one tells you the day doesn't exist there rather than saving the day next to it, and the field keeps the date it already had, so saving after a refused pick can't wipe it. Clearing the box yourself still clears the property.
• An option that HubSpot has since retired isn't thrown away. If a deal is sitting on a dropdown value that no longer exists in HubSpot, it stays in the list and stays selected. Opening the editor never silently changes the value. Multi-select properties get the same treatment: a retired value gets its own tick box, so you can see it and untick it rather than being stuck with a value you can't reach.
• Stage-scoped sections still apply. A property is only editable on a deal whose stage the section covers.
• It can be switched off centrally. If your Summit is running with in-place editing disabled, the card stays read-only and the Editable tickboxes don't appear in the layout settings at all, so nobody configures something that can't take effect. Any ticks made earlier are kept and take effect the moment it's switched back on.

Related

• Building out the deal card