Updates blog — Monday, June 22, 2026

HubSpot Updates: June 22, 2026

Nine updates landed June 22, and most of them are about plumbing rather than fireworks. Sandboxes keep inching toward real parity with production, the data model gets a proper home, and associations and permissions both get more granular. The one with a deadline attached sits inside the Notetaker update, so read that one closely if your team records meetings.

If you watched the show today, you already heard the conversation around several of these. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Activity Auto-Associations for App Objects

You can now configure activity auto-association settings for app objects from your connected apps, the same way you already configure them for standard CRM objects. When an activity like a call or email is logged on an app object record, it does not show up on related records' timelines unless association settings are in place. This update lets admins define the default auto-association behavior for activities logged on app objects, so the right records stay in sync. It is live across all hubs and tiers.

Why it matters: App objects have been moving toward first-class status for a while, and this makes them first-class for activity management too. The control here cuts both ways, which is the point. Auto-association can surface a full history of interactions, or it can dump every activity onto every related deal when you only wanted it on one. Putting the default behavior in the admin's hands is the right call, and it matters more every month, because the associations you set are exactly what Breeze reads from when it tries to make sense of unstructured data. Get the associations right and the AI has a chance. Get them wrong and it is working from noise.

For more details: Activity auto-associations for app objects live.

Centralized Data Model Management

This is a unified table and graph view for managing your entire data model, including objects, properties, associations, and conditional logic, from one place. It moved into public beta this round, after running as a private beta earlier in the spring, so more admins can get hands on it now. It is available across all hubs and tiers.

Why it matters: Managing the data model used to mean jumping between settings pages with no consistent picture of how objects, properties, and associations connect. This is one of the most requested admin updates HubSpot has shipped, and the move from private to public beta is the part to act on if you have been waiting on the sidelines. It reaches just about everything except pipelines, so auditing a complex configuration or making a quick edit to a property group becomes a single-screen task instead of a five-tab hunt. The bigger signal is that HubSpot now treats the data model as a surface you manage, not a settings detour you tolerate.

For more details: Centralized data model management public beta.

Notetaker with Smart Deal Progression

Smart Deal Progression already turns live calls and meetings into clear next steps, better CRM data, and faster follow-ups. It suggests CRM updates, identifies next steps, drafts personalized follow-up emails, and surfaces deal scores, risks, and buyer goals before your next meeting. The new pieces this round are about getting that work out of HubSpot and across language barriers. You can now share conversation recordings, summaries, and transcripts externally through secure links, with expiration dates, the ability to revoke access at any time, and no login required for recipients. Translation support arrives alongside it, so each user can review summaries and next steps in their own preferred language, switch languages on demand, and keep the original record intact. This is in public beta for Sales Hub Professional and Enterprise and Service Hub Professional and Enterprise.

The conversation review experience also picked up several quieter improvements. Auto-updates are now on by default for call and meeting outcomes, call stats and tracked terms now reach both the meeting and call review pages, email follow-up drafts open directly inside the Breeze panel with a cleaner format, and a new suggested follow-ups card brings post-engagement recommendations onto the deal record.

There is one change in here with a date attached. Starting July 31, 2026, meetings recorded through Notetaker, Zoom, Google Meet, and Microsoft Teams will create only a meeting record, instead of creating both a call record and a meeting record. Call objects still exist for actual phone calls; this affects recorded meetings only. If you run workflows triggered by call creation that were really meant for meetings, or rely on call-based properties like has transcript, transcript ID, or duration, or filter reports by call or engagement objects to track meetings, those need updating before the deadline. Expect a drop in call volume on activity reports after July 31. That is a duplicate record going away, not lost activity, and it reflects better data accuracy. HubSpot is already adding the key properties to the meeting record so you can rebuild workflows and reports ahead of time. This change first came up on the June 5 show; that earlier recap has the longer version.

Why it matters: The admin work bookending customer conversations is exactly what makes CRM data go stale, and Smart Deal Progression keeps chipping away at it. External sharing is the piece teams have been asking for, and it is harder to ship than it looks, because secure links, access controls, and replayable hosted video all have to come together first. Translation is the kind of thing that used to mean hiring for local fluency at real cost, so making it a per-user toggle is a meaningful opening for any multilingual team on HubSpot. The July 31 logging change is the item to put on a calendar today. It makes calls and meetings finally mean what they say, and the teams most affected are the ones already getting value from the meeting Notetaker.

For more details: Notetaker with Smart Deal Progression public beta.

Knowledge Vault Permissions

You can now manage access to knowledge vaults using Manage and Use permissions at both the portal and the vault level, with scope manage-by-default settings and granular control over who can use or edit each vault. It is live across all hubs and tiers.

Why it matters: As an organization grows, it accumulates more vaults, and not all of them are relevant to every user. Vault-level permissions let builders control who can see and edit each one, which keeps workspaces organized and cuts noise for people who do not need access. It also reduces the risk of accidental data loss or unauthorized exposure, which starts to matter for compliance as teams scale. The bigger context is that vaults are becoming where business context lives, the kind of context that used to sit in personal inboxes and desk notes. Once that context drives what your AI does and says, governing who can touch it stops being optional.

For more details: Knowledge vault permissions live.

Allow Visitors to Leave Live Chat Messages When Your Team Is Unavailable

Your Live Chat chatflow can now capture visitor messages when your team is away, at capacity, or outside business hours. When enabled, visitors can reach out at any time, and reps can view and respond to those messages from the inbox or help desk once they are back. This is in private beta across all hubs and tiers.

Why it matters: Plenty of teams use Live Chat as an async channel, not a strictly real-time one, and a chat input that locks after hours throws those conversations away. Giving admins control over when visitors can still reach out restores a behavior teams had built processes around. The setting is a choice, not a default, so decide deliberately. If your team can keep up with overnight messages, turn it on and route them. If response expectations would suffer, point the off-hours experience to another channel instead.

For more details: Live Chat messages during unavailable hours private beta.

Close a Chat and Keep the Ticket Open in Help Desk

Help desk users can now close a live chat while leaving the ticket open in help desk. This is in public beta for Service Hub Professional and Enterprise.

Why it matters: Tickets are not always resolved over a single chat. The rep may need to do more investigation, or the customer may have to leave before a resolution lands. Until now, the chat had to stay open, which made it look to the customer like the rep was still online and made it harder to start a fresh chat. Closing the chat while keeping the ticket open is a small fix to a gap that quietly eroded the support experience, and it lets the work continue without the conversation pretending to still be live.

For more details: Close a chat and keep the ticket open public beta.

Sandbox Creation Now Copies Automated Transactional Emails

When you create a sandbox, automated transactional emails are now copied along with any workflows or segments that reference them, and Deploy to Production is supported for new transactional emails as well. This moved to live after running in development earlier in the month. Sandboxes require an Enterprise subscription with the Sandboxes add-on, and testing this specific feature requires the Transactional Email add-on.

Why it matters: If transactional emails run through your workflows, you previously had to rebuild them and their dependent assets by hand every time you spun up a sandbox. Copying them across, with the workflows and segments that rely on them, lets you test that whole path without recreating it first. It is one more piece of the steady, worthwhile project of bringing sandboxes to parity with production.

For more details: Sandbox copies automated transactional emails live.

Sandbox Creation Supports Copying of Playbooks

When you create a new sandbox, playbooks from your production portal are now copied over automatically, including their content and recommendation settings. This is live. Sandboxes require an Enterprise tier, and playbooks themselves require Sales Hub or Service Hub Professional or Enterprise.

Why it matters: You can now test and confirm playbook configurations in a sandbox before they touch production, which catches issues early and keeps the sandbox a true reflection of your live setup. For teams that lean on playbooks to standardize how reps work a record, this removes a manual rebuild and one more reason the sandbox never quite matched reality.

For more details: Sandbox copying of playbooks live.

Sandbox Creation Now Copies Team-Based CRM Views

When you create a sandbox, team-based and shared CRM views across contacts, companies, deals, tickets, and custom objects are now copied from production. This is in private beta across the Enterprise tiers, including Commerce, Content, Marketing, Data, Sales, Service, and Smart CRM.

Why it matters: Saved views define what reps see on the index page, which filters surface the right records, and how managers operationalize playbooks across a team. Without them, a sandbox does not reflect how your team actually uses HubSpot, which makes it hard to test changes realistically, train new hires, or validate end-to-end workflows. Recreating those views by hand every time was tedious and easy to get wrong. This is the same parity story as the transactional emails and playbooks updates, applied to the layer your reps look at all day.

For more details: Sandbox copies team-based CRM views private beta.

Key Takeaways and Next Steps

Put one date on the calendar: The July 31 Notetaker logging change is the only item in this batch with a hard deadline. If your team records meetings through Notetaker, Zoom, Google Meet, or Teams, audit any call-triggered workflows and any reports filtered on call objects before then, and lean on the meeting-record properties HubSpot is pre-adding so you can rebuild ahead of the switch rather than after it.

Sandboxes are quietly closing the gap with production: Three of these nine updates are the same project from different angles, copying transactional emails, playbooks, and team-based views into new sandboxes. If you have avoided testing in a sandbox because rebuilding it never felt worth the effort, that math is shifting. The environment you spin up now looks a lot more like the one your team actually works in.

Structure is becoming a first-class surface: Centralized Data Model Management and Activity Auto-Associations both point the same direction. HubSpot is giving you one place to see and manage how your objects, properties, associations, and activities connect. That is worth caring about beyond tidiness, because the cleaner and more intentional that structure is, the better every Breeze experience reading from it performs.