What This Update Actually Is
HubSpot shipped three specific capability upgrades to the User object on July 29, 2026. Before this update, the User object existed in your portal but behaved like a second-class citizen compared to Contacts, Companies, and Deals.
Now it's a fully selectable object across your data model, pipelines, and segments. That means three concrete things:
- Associations: link User records to other objects in your data model so you can see exactly how internal humans map to Contacts, Companies, Deals, Tickets, or custom objects.
- Pipelines: build a structured, stage-based pipeline around User records, useful for onboarding new team members or tracking any multi-step user lifecycle.
- Segments: filter Contacts and Companies based on assigned user properties, plus access rollup and sync properties on the User object itself.
This ships to all hubs and all tiers. No upgrade required.
Why HubSpot Shipped This
Here's the honest problem this solves. Your internal humans, the reps, CSMs, account managers, onboarding specialists, have always existed inside HubSpot. But the system couldn't formally connect them to the records they influenced or the processes they moved through.
That created a blind spot. You could see that a Contact was assigned to a rep. You couldn't model the rep as a node in your data model with their own associations, stages, or segment logic hanging off them.
The internal frustration we've heard repeatedly from RevOps leaders: "We track everything about our customers and almost nothing about how our own team moves through our processes." This update closes that gap directly.
Multi-stakeholder selling environments, complex onboarding motions, and CS handoff workflows all need a way to treat internal humans as structured objects. Now HubSpot can do that natively.
How to Use It Step by Step
- Navigate to Settings, then Data Management, then Data Model. Confirm that the User object appears as a selectable node. If you don't see it, refresh your portal and check again.
- Create an association between User and another object. Go to your data model, select the User object, choose "Add Association," and pick the target object (Contact, Company, Deal, Ticket, or custom object). Name the association label clearly, something like "Assigned CSM" or "Account Owner."
- Build a User pipeline. Go to Settings, then Objects, then Users. Create a new pipeline and define your stages. For a new-hire onboarding flow, stages might be: Invited, Credentialed, Trained, Active, Fully Ramped.
- Create a segment using User properties. Head to Contacts or Companies, open the segment builder, and filter by an assigned user property such as "Assigned CSM: Region = Northeast" or "Owner: Role = Enterprise AE." Save it as a list you can target or report on.
- Add rollup or sync properties to your User records. From the User object property settings, configure which properties roll up from associated records or sync bidirectionally. This is where you start getting real visibility into a user's book of business.
- Test your associations by pulling a User record and confirming the related object records appear in the associations panel. Validate your pipeline by moving a test User record through each stage.
What It Touches in Your HubSpot Strategy
This update ripples into more corners of your portal than it first appears. Let's be specific about where you'll feel it.
Data model design: your CRM data model now has an internal-facing layer. You can finally visualize how your humans sit inside your customer data structure, not just beside it. This matters for audits, handoffs, and any time you're mapping ownership.
Reporting: rollup properties on the User object mean you can build reports that aggregate deal value, ticket volume, or contact count by user, directly from the User record. That's a cleaner foundation than hacking together owner-based filters in your Contact or Deal reports.
Workflows and automation: while this update is about object capabilities rather than workflow triggers directly, pairing it with user availability statuses in HubSpot workflows gives you a strong combined signal. You can now route based on a user's status AND model that user as a formal object in your data model.
Segmentation strategy: filtering Contacts by assigned user properties opens up account-based segmentation you previously had to approximate. Sales regions, pod assignments, CSM specialties, these can now become crisp list filters rather than workaround properties on the Contact itself.
Key Takeaway
The User object's new pipeline capability is most immediately useful for internal onboarding. If your company brings on reps or CSMs and wants to track their ramp stages inside HubSpot rather than a spreadsheet, this is the cleanest native solution you've had.
Service and CX teams will want to connect this to the broader team visibility picture. If you're already using workforce management in HubSpot Help Desk, the User object associations give you a complementary layer: you can model which agents own which accounts, not just who's available to take a ticket.
Key Takeaway
Associations between User and Company records are a RevOps unlock. Account ownership, multi-stakeholder coverage, and territory mapping can all be modeled directly in HubSpot's data layer rather than maintained in separate spreadsheets or fields on the Company record.
For teams running a full revenue motion inside HubSpot, this is another building block. The HubSpot Revenue Hub guide covers how HubSpot is building out the full commercial stack, and the User object becoming a first-class CRM object fits squarely into that architecture.
Who Should Care Most
Not every update deserves equal attention from every role. Here's who should move on this one first.
- RevOps managers who own the data model: this is your update. Associations and rollup properties on the User object change what you can report and how you structure account ownership. Plan time to redesign your data model with this in mind.
- Sales and CS leaders at companies with named account models: if you run pod-based selling or dedicated CSM assignments, the User-to-Company association is exactly what you've been missing. You can now model coverage formally inside HubSpot.
- HR and enablement teams that use HubSpot for internal processes: the User pipeline is a legitimate onboarding tracker. If your team is already in HubSpot daily, this keeps the ramp process in the same tool rather than a separate system.
- Marketing ops leaders who segment by rep or territory: filtering Contacts by assigned user properties directly in the segment builder saves time and removes the workaround properties you've been cramming onto Contact records.
- HubSpot partners and admins managing multi-stakeholder client portals: this is the object architecture upgrade you needed to model complex team structures cleanly.
George's Take
I've been in a lot of portals over the years, and the User object always felt like HubSpot's forgotten child. It was there, you knew it existed, but you couldn't do much with it beyond basic ownership fields. What this update signals to me isn't just a feature add, it's HubSpot finally treating the humans inside your organization as first-class data in your CRM. That matters because the best RevOps teams don't just track what customers do, they track how their own humans interact with those customers. Now HubSpot can hold both sides of that picture.
“Your customers aren't the only humans who deserve a structured place in your CRM. Your team does too. This update finally gives them one.”
If you want help mapping this into your existing data model or figuring out which associations and pipelines actually make sense for your team, let's talk. Book a strategy call with Sidekick Strategies and we'll walk through your portal together.
Frequently Asked Questions
What did HubSpot add to the User object in July 2026?
HubSpot gave the User object three new capabilities: associations with other CRM objects in your data model, pipelines for tracking user lifecycle stages, and segments that filter Contacts or Companies based on assigned user properties. Rollup and sync properties are also now available on the User object. This update applies to all hubs and tiers.
Can I build a pipeline for HubSpot users?
Yes. As of July 29, 2026, you can create a pipeline specifically for the User object in HubSpot. This is useful for tracking internal onboarding stages, ramp milestones, or any multi-step process your team members move through. You define the stages, name them to fit your process, and move User records through them just like Deal or Ticket pipelines.
How do I associate HubSpot users with contacts or companies?
Go to Settings, then Data Management, then Data Model. Select the User object, choose Add Association, and pick your target object such as Contact, Company, Deal, or a custom object. Name the association label clearly, for example 'Assigned CSM,' and save. The association will appear on both the User record and the associated record's detail view.
What are rollup properties on the HubSpot User object?
Rollup properties on the User object aggregate data from associated records. For example, you could roll up total deal value or open ticket count onto a User record, giving you a quick summary of that user's book of business without building a complex report. This became available as part of the July 2026 User object update.
Who gets access to the updated HubSpot User object capabilities?
All hubs and all tiers have access to the new User object capabilities, including associations, pipelines, and segments. There's no tier restriction. If you're on any paid or free HubSpot plan, these features are available in your portal as of the July 29, 2026 release.
How does the User object update help with multi-stakeholder selling?
In a multi-stakeholder sales or CS environment, multiple internal humans are often involved with a single account. The User object associations let you formally link multiple users to a Company or Deal record, modeling coverage rather than just primary ownership. This gives RevOps cleaner data and gives leadership a more accurate picture of how accounts are staffed.
