Currently, a user can be a ‘primary’ member of only one team. The user can be added to other teams as an ‘additional team member’, but many team features are unavailable to these ‘additional’ users (see list of restrictions below).
This is problematic and causing us considerable pain because some users need full access to multiple teams, e.g. an individual who is multi-role, or management/supervisory staff who need to monitor what goes on in the team. This is particularly true in smaller businesses. The one primary team restriction seems unjustifiable .
Restriction’s on ‘additional team members’:
These users will not be included in any team reports, routing rules (e.g., conversation routing rules), team notifications (e.g., form submission email notifications to a team), or workflow rotation actions. They will also not be able to view any custom records views set up for the team.
The solution is to allow users to be primary members of multiple teams.
I’m working with a client where the visibility of Companies and Contacts is based on a matrix of products and regions. They’re a small organisation with only 10+ sales users, so we can’t warrant going up to Enterprise just yet for more flexbliity around team reporting. We need a Territory Management capability, where we can assign visiblity of records to a Territory or selection of products and then allow visibility of those records to the user. It’s not suffiient to only have one primary Team, especially where you can’t assign ownership of a Company or Contact to a Team directly (but rather to a Team indirectly through the Team of the record owner). This is a feature which should be included in Sales Pro, since it’s quite common to have cross-functional teams in SMEs.
Upvoting this. The current setup of Additional Team Members defeats the purpose of Teams. If a user is assigned to multiple teams, they should be able to be treated as full team members. We have 6 branches (or Teams in HubSpot) but we have some salespeople who work at multiple branches. They should be able to be looped into round-robin meeting assignments, automation, workflow rotation, etc. just like a primary member of that team. This is a crucial function that we need for our business.
This is very important. It would give the “teams” function so much more flexibility, especially in Service Hub. It is common for a support member to be part of numerous teams, needing access to list views, etc which are currently not allowed within sub teams.
I agree. We are implementing Service Tickets and I need to be able to send internal emails to teams as opposed to users for making management easier, however users can belong to multiple teams - though this is impossible currently to define in HubSpot.
Teams could be a very flexible solution to the classic problem of grouping. However in its current implementation it is broken. A user should be able to belong to multiple groups. For access - it is simple - allow rights are OR-ed, deny rights (if applicable) are AND-ed. No conflict.
All team members, regardless if they are primary or secondary team members should be included in the reporting tool. There are many times when a Deal Owner may play a fundamental part in two different teams, and should therefore not be excluded in the reporting for that team.
At the moment, it is a limitation that almost defeats the purpose of having teams. It would be brilliant to see in a future product rollout
We need customization where we can group members in primary teams and additional cohorts. On which Reporting can be done too.
Scenario:
Let;s say we have 50 sales rep joining us, and they will be divided across different teams & regions. If we need to compare their performance with old or experienced sales rep on different metrics, it will be very insightful.
++ to both commenters here. We are also running a pod model with our teams. I would have expected “additional teams” to pull those members into reports filtered by “Hubspot Teams”
Yes, also critical for our business. We have some blended roles until the business grows to support dedicated new hires to report within a single team.
Yes, this is a VERY important feature.
In addition to the requirements from a pure sales team perspective (different regions/areas) also our CSM team is responsible for sales (upsell til existing clients)
So I want also to report (from report builder) but also should subteams contribute towards sales goals.
This is such a fundamental need I was very surprised to find out it wasn’t possible. One of the biggest pros of HubSpot is the ease of reporting and the ability to choose a team to report on. Please include this function!
It’s a must, for High level Managers to be able to aggregate teams performance and for Team leaders and teams to be able to have a single dashboard to refer to without having to duplicate it and select all the different deal owners !!
I think this feature should be handled at least for nested teams to begin with. If I am part of a parent team, then a sub-team within that, that’s a different scenario to me being part of two completely different teams.
This would be fantastic feature to have when organisations have sales reps that cut across multiple teams.
To those asking, “Why would I use nested teams if I can’t use more than a user’s main team for reporting?” You may be interested to know that, in addition to reporting, teams are used for other things in HubSpot, which take nesting into account - namely permissioning of HubSpot features and content.
If you are using team-level permissioning and have a nested team structure, it’s important to be aware of how access levels flow. According to HubSpot, “Teams above others can see everything owned below them, but the teams under can’t see everything owned by the team above them.” For example, In the nested team structure below, Team 1 will have access to everything that it has specifically been granted access to AND it will acquire the access granted to the teams below it (Team A, Team B, Team i, and Team ii). Similarly, Team A will have access to everything that it has specifically been granted access to AND it will acquire the access granted to the teams below it (Team i and Team ii). Conversely, Team i will only have access to the content that it has been specifically granted access to; it will not inherit access from the teams above it.
