Specific permissions sets pending on team

Right now, team-specific permissions sets apply the same for all teams you are assigned to (child or parents).

So, if you have the view or edit permission set for your team owned e.g. contacts - it applies equally for all teams you’re part of.

If we have Parent/Team A = Netherlands (Region) and Child/Team B = Customer Service, and someone is assigned to Team B (+Team A as parent). They can either edit all of the contacts assigned to those teams and/or view all of the contacts assigned to those teams. But, they cannot have view rights for all Netherlands AND edit rights for the Customer Service owned contacts.

(as far as we’ve tried?)

In our company structure, we’d really like to make a distinction this way so we can manage teams within regions that should be able to view all e.g. contacts assigned to their Team A region, but only edit those owned by their Team B team.

Hi @MBote,

You’re correct - this level of specificity is not possible with HubSpot permissions at the moment. You could request it from the product team here: https://community.hubspot.com/c/hubspot-ideas/59

Best regards!

Hi @MBote
I can definitely see the value in having more granular team-based permissions. In organizations with a regional hierarchy and functional sub-teams, it’s common for users to need broader visibility across a region while having edit permissions only for the records owned by their immediate team. That separation can help maintain data governance without limiting collaboration.

It would be interesting to know whether anyone in the community has achieved a similar permission model using a combination of teams, permission sets, or other HubSpot features, or whether this currently requires a different organizational approach.

Thanks for sharing the use case it provides a clear example of where more flexible permission controls could be beneficial.

according to Karsten above it’s not possible - also submitted a feature request which already got a reply, would be great to get this rolling as a feature improvement: Team-only permissions sets should be able to differ per team the user is part of

I agree this would be a useful feature, especially for companies with multiple regional teams.

Has anyone created a workflow or permission structure that gets close to this behavior without causing extra admin work? I think a simple screenshot or a short video showing a real-world setup would help everyone understand the limitation and any possible workaround much faster.