HubSpot Teams lets you group CRM users by function so each person sees only the CRM data relevant to their role. You create a team and assign users to it. HubSpot then uses that membership to route deals and filter views by team. If your sales team is split across regions or product lines, Teams is the mechanism that keeps each group working inside its own lane without needing separate portals.
In HubSpot, click the gear icon (top right) to open Settings, then navigate to Users & Teams in the left sidebar.
Click Teams at the top of the Users & Teams page. You will see any existing teams listed here.
Click “Create team”, give it a name (e.g. “Bangkok Sales”, “Marketing SEA”, “Support Tier 1”), and optionally assign a parent team if you use team hierarchies.
Search for users by name or email and add them to the team. A user can belong to more than one team.
Once teams exist, deal boards and dashboards can be filtered by team. You can also set default team filters so each user lands on a pre-filtered view when they log in.
What does HubSpot Teams actually control?
Teams affect several areas inside HubSpot:
- Record assignment and routing. When you use deal rotation or workflow-based assignment, you can route to a specific team rather than a named user. HubSpot picks from the team’s members in round-robin or custom-weighted order.
- Default filtered views. Deal boards and contact views can be filtered to show “my team’s records” by default. This prevents a Bangkok rep from seeing unrelated deals from the Singapore team.
- Dashboards and reports. Many HubSpot reports accept a team filter, so managers can build a dashboard scoped to their team’s performance without separate portals.
- HubSpot Inbox routing. Conversations can be routed to a team’s members rather than to an individual, which distributes inbound chat and email across whoever is available.
Teams do not replace user permissions. Permissions control what a user can see and do across HubSpot. Teams control how records are filtered and assigned within the permissions a user already has.
How should you structure teams for a Southeast Asian business?
The right team structure depends on how your sales or service function is divided. Two approaches work well in practice:
By geography or market. One team per country works well when each market has its own reps and largely separate deal flow. A Thailand team and a Singapore team each route their own inbound leads and filter their own pipeline views independently.
By product or segment. A team for SME clients, a team for enterprise. If you sell HubSpot implementation to small businesses and separately to large corporates, splitting by segment lets each team track its own conversion rates and cycle lengths in isolation.
You can also nest teams. HubSpot supports parent and child teams, so you can have a “Southeast Asia” parent team with “Thailand” and “Vietnam” child teams underneath. Reports can roll up to the parent level, which is useful for regional managers.
Can a user belong to more than one team?
Yes. HubSpot allows a user to be a member of multiple teams simultaneously. This is common for managers who oversee several teams or senior salespeople who cover more than one territory.
When a multi-team user is included in a round-robin rotation, HubSpot counts their capacity once per rotation cycle regardless of how many teams they belong to.
How do Teams interact with object ownership?
Record ownership (the “Contact owner” or “Deal owner” field) is separate from team membership. You can filter contact views to show “my team’s contacts”, which returns all contacts owned by any member of your team, not just records you personally own. This is useful for managers reviewing their team’s pipeline without having to open each rep’s individual view.
You can also build workflows that check team membership. A workflow can look up the contact owner and determine which team they belong to. It then branches to set a property or send an internal notification based on that team. This makes team membership a usable data point inside HubSpot logic, not just a display filter.
What team features require a paid tier?
Basic team creation is available on Starter and above. Team hierarchies (parent and child teams) require a Professional or Enterprise subscription. Record-level visibility restrictions scoped to a team require Enterprise.
On Starter, teams are useful for routing and default view filtering. On Professional or Enterprise, teams become a structural element of your access control strategy.
Frequently asked questions
How many teams can I create in HubSpot?
HubSpot does not publish a hard cap on team count for Professional and Enterprise tiers. In practice, most accounts use between 3 and 20 teams. Creating a large number of teams with few members each reduces the value of team-level filtering.
Can I delete a team without losing the users in it?
Yes. Deleting a team removes the team but does not delete the users assigned to it. Those users remain active in HubSpot with their original permissions intact. Any deals or contacts that were filtered by that team will lose the team association.
Do Teams affect email sending limits?
No. Email sending limits in HubSpot are tied to the portal tier and the individual user’s sending account, not to team membership.
Can I use Teams to restrict which contacts a rep can see?
Strict record-level visibility restrictions require Enterprise-tier permissions. On Starter and Professional, teams filter views by default but do not prevent a user from searching for and finding records owned by other teams.
How do Teams work with HubSpot’s inbox routing?
In the Conversations inbox, you can assign incoming conversations to a team rather than a specific person. HubSpot will route to available members of that team based on the availability settings each user has configured.
This guide is produced by an independent informational resource created by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us