Teams in HubSpot are groups of users, such as Sales East or Support Tier 2, set up in account settings. They control team-based record access, power routing and assignment, and let reports and forecasts be broken down by group.
Every user can belong to a primary team and, depending on your subscription, additional teams. Teams can also be nested, so a regional team can sit inside a broader sales team. Once teams exist, many HubSpot features use them: record permissions that let users see records owned by their team, ticket and lead routing, forecast roll-ups, and team filters in reports.
Team-based permissions are one of the main reasons teams matter. If a user’s access is set to records owned by their team and they have no team, they may see far less than they need. If teams are out of date after a reorganization, people see records they should not, or managers cannot see their own team’s work.
Reporting is the other reason. Leaders usually want numbers by team: pipeline by region, tickets by support tier, activity by sales pod. Users with no team appear in no team breakdown, so their work is missing from the reports managers read.
Mirror your real organization in HubSpot teams, give every active user a primary team, and update teams in the same week as any reorganization.
Crestview Staffing, a fictional recruitment firm, reorganized into regional teams but never updated HubSpot. Regional managers could not see their recruiters’ deals because permissions were set to team-owned records, and pipeline reports by region were empty. Updating teams fixed both problems in an afternoon.
Yes, depending on your subscription. A user has one primary team and can be added to additional teams.
Team-based record permissions, routing and assignment, forecast roll-ups and team breakdowns in reports.
Ancil connects to HubSpot read-only in about 60 seconds. Nothing changes in your portal without your approval.