Our team is needing a way to limit which units a particular user or team is assigned to. For example, if we have a team member who does support for one of our units and not another, I need to find a way to limit their access only to the unit they support.
Ideally, we'd be able to create roles for units and assign them to users based on which team they're a part of at our organization.
I'm not seeing any work-arounds for this, or any way to assign a user to a particular unit, which is somewhat disappointing and defeats the purpose of much of what we needed business units for.
It is ABSOLUTELY CRAZY that so many people have requested this for so long, and HubSpot has not done anything about it. We've just completely upgraded to Sales & Marketing Enterprise and sold on this feature only to find that it is not a part of it.
Terrible form HubSpot! You need to listen to your clients and get it sorted ASAP!
This is so crucial part for the business unit. We need to set permission for users to access their own business units. Please put this feature into the future roadmap!
This is still needed! Having difficulty setting up our sales team in husbpot because we need to limit their visibility to assets only in one business unit.
We're in the same boat as everyone else here - it makes no sense to me that you can have Business Units without being able to control or limit access. The feature is worthless to us - and many others I suspect - until this is available. Disappointing to say the least. As is the lack of movement since Oct 21 when this idea was first proposed. Will be escalating via our Success Manager.
How is this not a thing?! I don't get the point of. business units other than charging us more tbh. I need to limit access to so there aren't any issues with emailing the wrong people. Please release this Hubspot!
+1 that this feature is desperately needed. It is challenging when the user has to toggle between Business Units to find their specific contacts—that leads to errors and duplicate records being created.
The workaround I use for now if helpful. (If Team Permissions don't cut it for you as mentioned previousl in this thread, using a Team per Business Unit)
You can use Custom Owner Properties for permissions. When you set a user's permission to view/edit/delete any records they or their team own - HubSpot will look at all HubSpot User type properties on that object. e.g. Brand A Owner, Brand B Owner, Brand C Owner custom properties.
Note that permission to view a record with an 'Unassigned owner' is different - It always refers to the default record owner property i.e. if you tick that a user can see unassigned companies, they will be able to see any companies without a Company Owner, it will not refer to custom owner properties in that instance. (simply don't allow access to unassigned if you need permissions to refer to the Business Unit Permission properties).
I don't think this works for email templates though, does it? (only allowing Brand A to see certain email templates and Brand B to see other templates)
Hello! My name is Hallie, and I'm an APM on our CXM team here at HubSpot. I'm happy to share that permissions specific to Business Units is a feature currently being reviewed by our product teams. 🙂
For more context, our product teams are investing permissions based on the Teams feature throughout HubSpot. Their recommendation is for customers that want to limit access per Business Unit create a Team per Business Unit and then use the existing permissions capabilities to control access. Permissions across HubSpot is a big area of investment that our teams are continuing to make improvements in in 2025 and beyond. Additionally, another roadmap item being considered is one that would more easily link the user experience of creating Teams based on your Business Unit.
As any further updates are released, I will be sure to share them here. Please continue leaving your feedback here in the meantime!
This is a vital function please, we've just upgraded to this subscription this week, this function is already on our minds that we needed it, with so many comments here already. We are just hoping to hear the function will be available soon.
