Great minds think alike

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

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

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

Hi All,    For those of you who are not aware, HubSpot will be moving all existing customers to seats-based pricing in September if you were working with a partner. If you bought direct you might have already been migrated.   While for the most part there is no feature loss, a number of our customers are very concerned with this transition as they will be losing a feature that has been very important for their Management teams and Operations teams.   People who are transitioned to View Only or Core Seats will no longer be able to view deal and ticket tags.   This might affect customers who rely on their management or operations teams to see deal/ticket status without needing to manage them directly as is the case with a number of our customers.   Ideally, our customers would really appreciate it if deal tags and ticket tags could be visible for View Only and Core Seats as this feature adds a lot of value to customers who are not in a sales or support roles but not enough value to justify purchasing sales or service seats for these users.   Regards, Bryan ...read more

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': https://knowledge.hubspot.com/account/assign-users-additional-teams 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.   Any feedback? ...read more

I want to suggust to the HS product team that you address some of the limitations to Team membership.    I recently learned that if a user is listed in a team as an 'Extra' team member, that this limits certain functions. For one thing, they cannot be included in round robins.    I was excited by the potential for adding nested teams/subteams to larger teams, and adding users as 'extra' team members, as I felt this would provide several benefits.    Example A: Regional sales team round robins.    We have a team for our Enterprise Sales Department called "Enteprise Sales" the team includes any and all enterprise sales staff.    I went and created 2 subteams: Enterprise East, and Enterprise West, since certain staff are assigned to west coast leads, and some are assigned to east coast leads. However, the sales reps had the East/West teams as their 'extra' team membership, and so when I went to add those nested teams to the round robin I discovered I wasn't allowed to because 'extra' team members do not show up in round robins, and the east/west teams consisted entirely of 'extra' team members.   At first I thought this was a simple fix and I could just make the 'parent' departmental enterprise sales team to their 'extra' team membership (since it isn't as important from workflows.)    However, that ultimately did not appear to be an option, since 'extra' team members are not included on reports that are filtered by teams, and we have many dashboards/reports that are filtered on the primary, departmental, 'enterprise sales' team.    2.) Workflow maintenance   Another reason I was excited for subteams and 'extra team' memberships was because I thought it would make workflows much easier to manage moving forward, especially as our company continues to grow and expand.    For example: the average sales rep with a HS user account is incorporated into dozens of workflows. In the event that a sales rep leaves the company, or changes positions, we have to remember the 12+ workflows that need their steps and branches to be edited and updated whenever a staff person needs to be added or replaced.    A HUGE improvement would be to create subteams that only include 1 single user (for example: creat a Subteam called "Regional Sales Manager: Florida" and then assign the Florida regional sales manager as the one and only team member.)  Then our plan was to edit all of our workflows so that no branch is ever based around a specific user account, but rather steps and branches are based around that user's unique subteam. That way, if our Florida Regional Sales Manager leaves the company or changes roles, and somebody new is placed in that position, the only thing I need to edit is that new user's HubSpot Subteam, as opposed to spending tons of time editing dozens of workflows, and risking forgetting or neglecting to update one or two.  I'm honestly not certain what the function or utility is to subteams and 'extra VS main' team membership if users are limited to 1 main team and 'extra team' membership limits reporting, round robins, routing and notifications. Freeing it up so that people can be on multiple teams and still have all of the available features of a 'main team member' seems like it would 10x the value of having users on multiple teams.    I hope this feedback is helpful.  ...read more

Hello community 👋 and product team ✌️   Background Today it is possible to create and pin your own custom views within contacts, companies, deals, tickets and more (lets use the word objects from now on). A HubSpot user may edit columns, filters and save these according to their own preferences.    A view 👀 can either be standard, created by me, or created by others (see picture and ignore Swedish content). Once a view has been created by me no one else can edit this view and save it for all users 👥 - instead they have to clone their own version of the view in order to change it.          Issue We are growing our company fast ⏩ and we want to be able to scale our staff up and down without it affecting the infrastructure of what we have created. If one staff member decides to quit and move on to a new company - and that staff member being a core creator of the views that all other HubSpot users in our portal uses - we could be in big problem.   Why? All these views created by others can be pinned to my default view. I will have a standard set of up to 5 views in my portal that I will use in my day to day management. If the staff member that created that view quits users could be stuck 🔒 with old standard views in their pin bar without knowing.        Idea for solution (proposal for the product team) 🤗 There are several ways to solve this issue. Some better than others. I would really love them all to be delivered 👍 but as we all know thats not always possible.    A) Make it possible to pass ownership of a view Make it possible for a view owner to pass the ownership (and there by the uniqe rights to edit the view) to an other HubSpot user of the same portal.    B) Make it possible to collaborate in creating standardized views Make a setting so that a view can be collaborated on by all HubSpot users. Once a change is made by once user it will affect all others. Perhaps a small information box upon saving the view informing the user that it will affect all other accounts.    C) Make it possible to set up ownership of a view to a team Make a setting so that a view can be collaborated on by a specific team of HubSpot users. Once a change is made by once user in that team it will affect all other users (in the team or not). Also here recommended to have a small information box upon saving the view informing the user that it will affect all other accounts.  ...read more