What This Update Actually Is
HubSpot has always let admins control how activities automatically associate across standard CRM objects. Log a call on a contact, and HubSpot can auto-associate it with that contact's primary company or open deals. That logic has existed for a while.
What didn't exist until now: that same configurability for app objects. App objects are custom records created by connected third-party apps, like an applicant tracking system (ATS), a project management integration, or a custom-built data object from a HubSpot-connected tool.
With this update, admins can now define the default auto-association behavior for activities logged on those app objects. The configuration lives in the same place as standard object settings: Settings, then Data Management, then Objects, then Activities, then the Associations tab.
One important caveat: you can only configure logging behavior for an app object if an association already exists according to the data model configured by the connected app. If the app object isn't associated with an activity or a record, the setting will be unavailable.
Why HubSpot Shipped This
Here's the problem this solves. Your sales rep logs a call on an ATS Application record. That call is captured. But without auto-association settings in place, the call doesn't show up on the related contact's timeline, the linked company record, or the open deal.
The humans on your team then have to manually jump between records, piecing together a conversation history that should have been connected automatically. That's not just annoying. It's a real trust problem. Reps stop believing the CRM tells the full story, so they stop using it.
HubSpot shipped this because the CRM's value depends on complete context. When app objects live in a different visibility tier than standard objects, the whole data model feels inconsistent. This update removes that inconsistency.
How to Use It Step by Step
You'll need Super Admin permissions to make these changes. Once you're in, the path is straightforward.
- Click the Settings icon in the top navigation bar of your HubSpot account.
- In the left sidebar, navigate to Data Management, then click Objects.
- Click the Select an Object dropdown and choose Activities.
- Click the Associations tab.
- Select the app object where the activity is originally logged. For example, if you're using an ATS integration, you might select "ATS Applications" from the dropdown.
- Select the activity type you want to configure, such as Calls or Emails.
- Under Log Activity To, click the dropdown for each associated object and choose your preferred logging behavior.
- Click Save.
When choosing your logging behavior, you have five options per associated object:
- None: skips auto-association for that object entirely (contacts who were directly called or emailed are still associated).
- Log to All: associates the activity with all related records of that object, up to 500 of the most recent.
- Log to 1 Most Recently Associated: associates the activity with only the most recently linked record.
- Log to 5 Most Recently Associated: associates the activity with the five most recently linked records.
- Log to Primary Company (companies only): associates the activity with only the primary associated company record.
Options marked with an orange Default tag show HubSpot's current default for that object and activity combination. You can reset to those defaults at any time by clicking Reset All Changes.
For full details, see HubSpot's Knowledge Base article on setting up automatic associations for records and activities at https://knowledge.hubspot.com/object-settings/configure-automatic-activity-associations.
What It Touches in Your HubSpot Strategy
This update is narrower than it sounds on the surface, but it has a real ripple effect for portals that rely on connected apps.
Your Data Model Gets More Consistent
Standard CRM objects and app objects now behave the same way when it comes to activity logging. That consistency matters a lot when you're auditing your data model or onboarding a new admin.
Key Takeaway
App objects now participate fully in activity association logic. That means calls, emails, and meetings logged on connected app records can flow to contacts, companies, and deals without anyone manually linking them.
Record Timelines Become Trustworthy Again
We've seen this pattern across many portals: a connected integration creates app objects, activities get logged on those records, and the contact or deal timeline ends up looking sparse. The humans reviewing those timelines think nothing happened. But plenty happened. It just didn't associate.
If you've been working through your data model with HubSpot's Centralized Data Model Management tools, this update is a natural next step. Once your object relationships are mapped clearly, you can define exactly how activity data should flow across them.
Workflow and Reporting Implications
Auto-associations affect more than timelines. Any workflow or report that filters on activity data needs accurate associations to run correctly. If a deal enrollment trigger checks for recent call activity and that call never auto-associated with the deal, the enrollment won't fire.
This connects directly to the kind of data integrity work covered in our update on workflow enrollments surviving record merges. Both updates are about making sure your automation logic actually sees the data it needs to function.
Key Takeaway
Check any deal or contact enrollment workflows that trigger on logged activities. If those activities were previously being logged on app object records without auto-association, those workflows may have been quietly misfiring.
Important Limits to Know
Custom auto-association settings only apply to activities created or logged from within HubSpot. Activities created through HubSpot-built integrations (like meetings booked via HubSpot Meetings) follow default association behavior instead of your custom settings. Plan your configuration with that distinction in mind.
Who Should Care Most
This update isn't for every HubSpot portal. But if any of the following describe your setup, it's worth acting on soon.
- RevOps and HubSpot admins managing portals with connected third-party apps that create custom objects, especially ATS, ERP, or project management integrations.
- Sales and recruiting teams whose reps log calls or emails on app object records and need that history visible on contacts and deals without manual linking.
- Marketing ops leaders whose attribution reporting depends on complete activity data across all related records.
- Businesses running complex data models with multiple connected apps and multiple app objects that interact with standard CRM records.
If your portal only uses standard HubSpot objects and doesn't have any connected apps generating custom records, this update doesn't change anything for you today. But it's worth knowing about as your tech stack grows.
George's Take
I've sat with a lot of portals where the complaint is the same: "We have all this data, but nobody trusts it." Nine times out of ten, the trust problem isn't missing data. It's fragmented data. Activities logged in one place that don't connect to the records humans actually review. This update is HubSpot saying the CRM should work like a complete system, not a collection of siloed objects. If you've got connected apps and you haven't looked at your association settings recently, this is the nudge to go do that audit today.
“The CRM your team trusts isn't the one with the most data. It's the one where the data shows up in the right place at the right time. Auto-associations are how you build that trust into the system.”
This pairs well with HubSpot's push toward real-time data visibility, which you can read more about in our breakdown of real-time table updates in the HubSpot CRM. Accurate associations combined with live record updates make for a CRM your team will actually rely on.
If you're not sure whether your current association settings are working the way you think they are, that's exactly the kind of thing we dig into at Sidekick Strategies. Book a strategy call and we'll help you map out where activity data is falling through the cracks and how to close those gaps for good.
Frequently Asked Questions
What are activity auto-associations in HubSpot?
Activity auto-associations in HubSpot are settings that control whether activities like calls, emails, or meetings logged on one record automatically appear on related records' timelines. For example, logging a call on a contact can auto-associate that call with the contact's primary company and open deals, so everyone sees the full interaction history without manual linking.
What is an app object in HubSpot?
An app object is a custom record type created by a connected third-party app in your HubSpot portal. Examples include ATS application records from a recruiting integration or project records from a project management tool. App objects live in your HubSpot CRM alongside standard objects like contacts, companies, and deals.
Who can configure activity auto-association settings for app objects?
Only Super Admins can configure activity auto-association settings in HubSpot. The settings are found under Settings, then Data Management, then Objects, then Activities, then the Associations tab. From there, Super Admins can select any app object and define how activities logged on it propagate to related records.
Does the activity auto-association update work for all HubSpot plans?
Yes. HubSpot's activity auto-association settings for app objects are available to all hubs and tiers as of June 22, 2026. You don't need a Professional or Enterprise plan to access this feature, though you do need Super Admin permissions within your account to make changes.
What logging behavior options are available when configuring app object auto-associations?
You can choose from five options: None (no auto-association), Log to All (up to 500 most recent associated records), Log to 1 Most Recently Associated, Log to 5 Most Recently Associated, and Log to Primary Company (for company objects only). Options with an orange Default tag show HubSpot's current default for that combination.
Are there any limitations to the new app object auto-association settings?
Yes. Custom auto-association settings only apply to activities created or logged directly from your HubSpot account. Activities from HubSpot-built integrations (like HubSpot Meetings) follow default association behavior instead. You also can't configure settings for an app object unless an association already exists in the data model configured by the connected app.
