Great minds think alike

The new beta update for Business Units is great, because you can now select from Navigation which Business Unit you are working on when in your portal. However, it gives access to all users.   There should be a way to filter or manage who can see the Business Units depending on the team or unit they actually work on: ...read more

Currently, you can only download files in bulk from the Files tool if you are a Super Admin. However, you can download files individually if you have the permissions.    I'm suggesting a change to the permissions options to allow for bulk downloading of files to anyone with that permission set. ...read more

Service Hub is lacking visibility on agents available/offline status (reporting, notifications).  Would be very interesting to add Availability Status to user based properties in HubSpot.    This would open some possibilities for team activity reporting. ...read more

Currently when people are building a survey and they don't have access to (create) properties they can't save a survey.  This is quite a annoying.   It would be great if my collegues could built their surveys and somebody else could create the properties.  Even better though would be if you could also create surveys without the need for properties. Not everything is always contact-based perse.  ...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

There has been a number of updates to help Hubspot users know when calendars or email inboxes have been disconnected. All are helpful improvements yet one critical piece seems to be missing. Request that would help solve the problem. Notify the Super Admins on an account when any user's calendar OR email is disconnected.   There are other Super Admin notifications (like when social accounts are disconnected). The user is notified when their email is disconnected (though if they miss that notice, it could be a while before anyone notices) AND there is no mention of the calendar on this notification making that 2nd action easy to overlook by a user.  Other recent tickets around this work This one is about a sales rep being notified, that is all fine and should happen BUT Super Admins should also be looped in to ensure the action is handled in a timely manner - it's a backup for support. This 'Delivered' idea has a number of improvements that are helpful but still fall short of being manageable in day-to-day. For an Admin to have to refer back to these daily to ensure all is operational is silly. Helpful to have the ability to see, but without a notification doesn't feel feasible to manage. ...read more

We would like to be able to have a ticket approval process set up. When a ticket enters a certain status it would be good to have a certain amount of users that can approve this.  At the moment there is a Deal approval process and it would work the same for Tickets. The only thing I would add to this approval process would be conditional approval on the status. That means that approval would be needed on a status if a Ticket meets certain criteria. This can be filtered on certain properties. The most useful filter would be Ticket Tags. Ex. Ticket Pipeline - Support Pipeline Pipeline Statuses - Received, In Review, Assessment, Approval, Closed. When the Ticket gets to Approval there are 2 options. IF Ticket Tag contains "Warranty" Approval is needed ELSE Ticket Tag contains "Service" or "Modification" Approval is NOT needed ...read more

HubSpot admins need to be able to prevent users from accessing the "edit columns" (see below) button while working in the Line Items editor / in the Quote tool.   Currently, users see the button "edit columns" and they are free to take advantage of making the tool suitable for their personal needs. This, in turn, complicates the lives of their colleagues and HubSpot admins.  As a CRM aimed at scaling businesses & enterprise customers, HubSpot should prioritize such an update with high priority.     ...read more

As of today, limiting user rights to "contacts/companies/deals/tickets - they own" does not hide meetings logged to contacts/companies/deals/tickets users do not own from the "Search HubSpot" results these users see.   This means that even though a user is not allowed to see a company record, when they search HubSpot, search results enable users to see meetings logged to said companies including attendees, dates, durations and most importantly descriptions.     Our customer has very strict legal requirements of what information select user groups are allowed to see. We need either...   1) a way to control a team's search results of the "Search HubSpot" search (similar to as described here: https://community.hubspot.com/t5/HubSpot-Ideas/HubSpot-Search-results-view-customization/idi-p/963266).   or   2) a way to control the user rights for "meetings" to "owned, team owns, everything".   This is a urgent must have. ...read more