What This Update Actually Is
HubSpot has added a new CRM property called Owning Teams as part of its Support Multiple Teams private beta.
This property captures every team directly assigned to a user, including both the Default team and any Additional teams. Before this, the existing HubSpot Team property only ever stored the default team value. If a user belonged to three teams, two of those teams were invisible in reports and filters.
One important caveat: Meetings round robin routing is explicitly excluded from this update. HubSpot removed it from the list of supported routing rules during this beta. Don't build round robin workflows around multiple teams just yet.
Why HubSpot Shipped This
Many growing companies structure their HubSpot accounts around overlapping teams. A sales rep might sit on a regional team and a product-line team at the same time. A service agent might belong to a tier-1 queue and a VIP escalations group.
The old model forced a single default team onto every user. Reports built on the HubSpot Team property would only show one dimension. Admins had to build workarounds: custom properties, manual list segmentation, or extra workflows just to approximate what a real multi-team report should show automatically.
The internal frustration is real. Ops leaders would set up team structures in HubSpot's user management, then discover those structures didn't flow into reports at all. The tool felt disconnected from how the actual business was organized. This update closes that gap.
How to Use It Step by Step
- Confirm your account is enrolled in the Support Multiple Teams private beta. All accounts in the beta as of April 14, 2026 have access. Check your product updates feed or ask your HubSpot contact.
- Navigate to Settings, then Users and Teams. Verify that each user has a Default team set and that any Additional teams are assigned correctly. Owning Teams pulls from both fields, so messy user setup will produce messy property values.
- Open your CRM property manager and search for Owning Teams. Confirm the property is visible on the contact, company, deal, or ticket records where your team-based workflows run.
- Build or update your reports to filter or segment by Owning Teams instead of, or in addition to, the existing HubSpot Team property. Use Owning Teams when you need full coverage. Use HubSpot Team when you specifically want to isolate default-team activity.
- Audit any active workflows that route records based on team ownership. Replace legacy team-property logic with Owning Teams where multi-team membership matters for routing decisions. Skip round robin meeting routing for now.
- Document the change in your internal ops runbook. Note which reports now use Owning Teams and what the HubSpot Team property still covers. Future admins will thank you.
What It Touches in Your HubSpot Strategy
This update ripples across more of your portal than it might first appear. Here's where to look.
Reports and Dashboards. Any dashboard built to measure team performance needs to be reviewed. If your current reports filter by HubSpot Team, they're showing a partial picture. Owning Teams lets you build accurate cross-team pipeline reports, service ticket breakdowns, and activity summaries without manual workarounds.
Workflow Routing. Enrollment triggers and branch logic that depend on team membership can now be more precise. A workflow that previously missed records because a user's secondary team wasn't visible can now catch them correctly.
Key Takeaway
The existing HubSpot Team property isn't going away. It still reflects only the default team. Think of Owning Teams as the complete version. Use both intentionally, not interchangeably.
Filters and Views. Contact, deal, and ticket list views can now filter on Owning Teams. This means team leads can build saved views that accurately reflect their full book of work, not just the records tied to their default team.
Data Hygiene Implications. This update makes your user-team structure more load-bearing than ever. If team assignments in HubSpot are outdated or inconsistent, Owning Teams will surface those inconsistencies directly in reports.
Before you start building new reports on top of Owning Teams, run a quick check of your user-team assignments. Our data hygiene framework covers the governance steps that keep properties like this reliable over time.
Key Takeaway
Don't build Owning Teams into critical workflow routing until you've verified that every active user has accurate Default and Additional team assignments. Garbage in, garbage out applies here just as much as it does anywhere else in your CRM.
This update fits a broader pattern of HubSpot tightening the connection between its user management layer and its reporting and automation engines. We broke down that signal in our analysis of 34 recent HubSpot updates: cleaner data structures are a recurring theme, and multi-team visibility is a direct example of that work.
Who Should Care Most
Not every HubSpot account feels this pain equally. Here's where it hits hardest.
- RevOps and HubSpot admins at companies with 10 or more users organized across multiple teams. You've likely already built workarounds for this. It's time to clean those up.
- Sales and service managers who lead cross-functional or matrix teams. You've been asking for accurate pipeline and ticket reports by team for a while. This is the start of that answer.
- Ops leaders at agencies, SaaS companies, or service businesses that assign reps to multiple pods or verticals simultaneously. Your reporting has been underrepresenting team-level activity. Owning Teams fixes that.
- Humans managing HubSpot portals for enterprise or mid-market companies where team structures change frequently. The more fluid your org chart, the more this property matters.
If your company only uses a single team in HubSpot, or if every user belongs to exactly one team, this update won't change much for you yet. Bookmark it for when you scale.
George's Take
I've audited a lot of HubSpot portals over the years, and one of the most common frustrations I hear from ops leaders is that their team structure in HubSpot doesn't match how their business actually works. They've set up teams thoughtfully in user management, then discovered that layer has almost no influence on what shows up in reports or filters. This Owning Teams property is HubSpot finally connecting those two worlds. It's not flashy, but it's exactly the kind of foundational fix that makes everything else more trustworthy.
“The best HubSpot portals aren't the ones with the most features turned on. They're the ones where the data structure actually reflects how the humans inside the business operate. Owning Teams moves us one step closer to that.”
If you're in the beta, start with a team assignment audit before you build anything new on top of this property. Our HubSpot portal audit checklist includes a user and team review section that'll help you clean up the foundation first.
If your portal has more than one team and your reports have never quite reflected how your business is actually structured, let's talk. Our team works inside portals like yours every week, and we can help you build on this update the right way from day one.
And if you want to understand how shared data structures like this one power your full HubSpot strategy, start with our piece on how shared data becomes a quiet superpower across hubs. It gives the strategic context that makes updates like Owning Teams click.
Frequently Asked Questions
What is the HubSpot Owning Teams property?
Owning Teams is a new CRM property available in HubSpot's Support Multiple Teams private beta. It stores all teams directly assigned to a user, including both the Default team and any Additional teams. This lets reports and filters reflect the full scope of a user's team membership, not just their primary team.
How is Owning Teams different from the existing HubSpot Team property?
The existing HubSpot Team property only stores a user's default team assignment. Owning Teams captures every team the user belongs to. If you need complete multi-team visibility in reports, filters, or workflows, use Owning Teams. Use the original HubSpot Team property only when you specifically want to filter by default team.
Does this update support round robin meeting routing for multiple teams?
No. HubSpot explicitly removed Meetings round robin from the list of supported routing rules in this beta. Multi-team round robin meeting routing is not yet available. Don't build that logic into your workflows based on this update. HubSpot has indicated it's a future consideration, not a current one.
Who has access to the Owning Teams property?
Access is limited to accounts enrolled in the Support Multiple Teams private beta, which was active as of April 14, 2026. If your account is in the beta, the property is already available. Check your HubSpot product updates feed or contact your HubSpot rep to confirm enrollment status.
What should I do before using Owning Teams in reports and workflows?
Audit your user and team assignments first. Owning Teams pulls from both Default and Additional team fields in user management. If those assignments are outdated or inconsistent, your reports will reflect those errors. Clean up team assignments before building new reports, filters, or workflow logic on top of this property.
Which types of companies benefit most from the Owning Teams property?
Companies where sales reps, service agents, or other HubSpot users belong to more than one team benefit most. This includes agencies, SaaS businesses, and service companies that organize humans into overlapping pods, regions, or verticals. Single-team organizations won't feel the impact until their team structure grows more complex.
