Great minds think alike

Currently, it is not possible to create and test users along with the permissions, permission sets and seats assigned to them in a sandbox portal and then sync these to the production portal. The new feature from https://knowledge.hubspot.com/account-management/deploy-sandbox-changes-to-production allows this for assets but not for users.   Suggestion: allow syncing users and their set up from sandbox to production portals ...read more

Problem Today in HubSpot, it’s not possible to fully hide a property. You can set field-level security to “private to super admins only”, but this only hides the field content — the property label (name) is still visible to end users. As a result, users often see property names that are irrelevant to them, which clutters their interface. This problem grows when multiple teams are using HubSpot across different pipelines. Proposed Solution Allow super admins to completely hide a property from end users, either globally or at the team level. This would provide: The ability for admins to create private properties and still use them for reporting in the background. The possibility to hide a property before archiving it. If it’s forgotten, end users will naturally flag it, and field-level security can be reopened if needed. Cleaner views for sales reps: today, when they build lists or views, they see countless variables that don’t apply to them. With multiple teams working on different pipelines (each with its own set of properties for deals and companies), being able to display only the properties relevant to their team would bring real clarity and efficiency. Impact Less clutter for end users Better adoption of properties that actually matter Easier management of multi-team setups and pipelines More intuitive experience for sales and service teams ...read more

I'm one of two Super Admins in our organization's IT department, tasked with managing permissions for all of our Hubspot users.   Since our organization's use of Hubspot has grown tremendously this year, we have new teams coming on board, while existing teams basically had 'default' permissions, with no explicit permission set assigned.   As a part of this process, I collected all IT Department users (which ended up grabbing my own user record) and assigned the appropriate "IT Department" permission set, not realizing that doing so was going to **strip** my own Super Admin permissions!   This was last week, so I only have my vague memory to go by, but I sure don't recall seeing a big red banner that said anything like, "WARNING: You're about to remove your own Super Admin privileges!" I would have greatly appreciated such a warning.   The only remaining Super Admin in our account was a third party contractor, temporarily invited to help us onboard more of our own staff! Hubspot's own support staff recommended I reach out to that contractor to have them re-promote me to Super Admin, even though our account's own internal audit logs showed I demoted myself and the other Super Admin from IT all on my own. So kudos for tight security I guess? ...read more

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. ...read more

Unbounce HubSpot User option for HubSpot Admins to self-serve instead of contacting HubSpot Support.   I have made this request before every time I have a support ticket- but giving the ability to unbounce users for HubSpot Admins to self-serve and unbounce users in HubSpot would be more efficient. This has a lot of wasted time working on these by asking our internal networking team to check if emails were blocked before hubspot support will check if an email was "bounced". I need to be more strategic with my time and give our hubspot users back in more efficiently. Also, I have had this happen to many hubspot users who are active everyday, so them becoming bounced at somepoint makes no sense and wasted time for them and me. ...read more

HubSpot has removed the ability for company users with Account Access permission to see all company tickets in the Support Inbox.   This is a terrible decision on HubSpot's part. We have 20 people at our agency and any one or small group of them could be communicating with HubSpot support across any of the 60+ accounts we service. It's not practical to forward messages to the whole company on such matters. Furthermore, we have now irrevocably lost access to the ticket history for any team members who have left the company.   HubSpot support team, imagine trying to do this for your own ticketing system and if you couldn't see prior ticket history coming in cold to service an account. Please fix this! (It's fine if it's just for Super Admins, we just need to be able to see the history somehow.)   ...read more

The New Lead Object is fantastic however the lack of granular settings is a massive roadblock when it comes to team adoption of the tool.  For example; we can only give users access to all prospecting workspaces or only their workspaces - what about global companies with multiple team levels Example 2; we cannot create custom lead properties that are only visible & editable to specific teams (important for multibrand companies). With any custom property created, when cannot customise the lead area display to ensure teams are looking at the core set of properties for this object  Example 3; when it comes to properties there is no setting to restrict which properties are editable and which are not - the system will preset some of these properties and should not be editable by the individual sales users There are many more instances where the default functionality within other objects has not yet been brought into the lead object. Teams are used to the set-up and functionality within HubSpot being mirrored across objects, and this stark difference with leads results in frustration towards a fantastic tool. ...read more

We have Lifecycle Stage on the contact record set to "View Only" for our sales managers due to automations that run to create leads for them when moving to specific stages (MQL & SQL). It appears that these rules only take affect on records that are already created and blocks them from editing said records. That said, when creating a contact record from the contact creation form, these users have access to set the Lifecycle stage, even though they have view only permission. This needs to be fixed as it is causing automation to create new leads for sales managers who sources their own contact and created their own contact and should not be counted as a lead. This should be a fully restricted property, not just on exisiting records, but on new record creation as well. The responses provided to me by support are not feasible. I was told that we should restrict record creation to Super Admins only. This goes against everything that HubSpot is built for...efficiency and autonomy of sales and marketing managers. It doesn't make sense for us to have a sales manager request admins to create a contact for them...that would take the same amount of time to make the request then for them to just create the contact.  ...read more

Currently, HubSpot lacks the functionality to restrict record views (e.g., contacts, companies) based on assigned Business Units (BUs). While it is possible to manage access through "Team Only" permissions, this method requires assigning contacts to specific team members. However, newly created contacts without an owner remain visible to all users, even if a BU is already assigned to the record. This limitation creates challenges for organizations managing multiple BUs, as users cannot be restricted to only seeing records associated with their BU unless every contact has an owner. A proposed solution would be to enable user permissions to restrict access based on the BU assigned to records. This feature would enhance security, improve usability, and streamline workflows for organizations with multiple BUs. I believe this would significantly benefit HubSpot users, and I encourage the product team to consider implementing this feature.  ...read more