Great minds think alike

I would like to create a firm Calander that everyone at the firm has acess to. When there is a new meeting or event created, then that said meeting or event would also directly link to the asscoiated contact/company. It would also need to be a calendar that everyone at the firm has acess to, not only one person.  ...read more

Recently, we had a few cases where users bounced and therefore did not receive internal notifications anymore. In most cases, these bounces were caused by temporary IT related issues. Being able to see the bounce itself and the bounce reason, and also to unbounce the users would be extremely helpful. Even adding the users as contacts does not do the trick, since notifications are being sent from a different server. There are notifications and internal messages being sent that are crucial for the teams to receive, while currently there is no way to even identify that something has NOT been sent. Currently, contacting the support team is the only way to have the users identified and unbounced. ...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

I would love to see Husbpot consider opening Help Desk in the limited capacity that it does for Core and Sales seats, to View Only Seats as well.   For your customers, this would create efficiencies and improve ease of use since View Only users need to have visibility to tickets they are tagged in, and currently we can only @(mention) a View Only user by moving from Help Desk to the Tickets workspace.   For Hubspot, this would drive increased engagement in Help Desk and showcase the superior format and functions, creating stickier revenue. ...read more

Currently, only Super Admin can bulk assign leads from the Leads Summary (public beta) and this cause problems since Sales leaders are usually not Super Admin but they need to be able to assign leads to their team members, would it be great if it can be allowed in the permissions sets ...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

We just switched to Help Desk and when we were managing our emails in the Inbox we could limit who had access to the inbox and that made it so only the people with access to the Inbox could send emails using the "Send From" email address. This permission feature isn't in Help Desk so now everyone can send emails using our bigger email addresses. I need a way to limit who can send emails using our bigger email addresses (like support@company.com). ...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

Currently, HubSpot allows us to create permission sets and assign them to individual users. However, as organizations grow, managing permissions for each user becomes time-consuming and prone to errors. I propose implementing team-based permission sets to streamline this process.   Key Benefits: Time-saving: Admins can set permissions once for an entire team rather than individually. Consistency: Ensures all team members have the appropriate access levels. Scalability: Easily onboard new team members with pre-set permissions. Flexibility: Allows for quick adjustments to team-wide permissions as roles evolve. Proposed Functionality: Create permission sets at the team level Automatically apply team permission sets to new team members Option to override team permissions for specific individuals if needed Ability to view and manage permissions at both team and individual levels This feature would significantly enhance HubSpot's user management capabilities, especially for larger organizations with multiple teams and frequent onboarding.   I believe this addition would greatly improve efficiency and security in permission management across the platform. ...read more