Grandes mentes pensam igual

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.)   ... Exibir mais

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.  ... Exibir mais

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. ... Exibir mais

Currently, you can setup Out Of Office availability at each User level. However, it does not "connect" with Meetings scheduler and the functionality "Consider working hours". It leads that when a User has a personal/individual Meeting, it does not take into account that the User is OOO, and clients could still book a meeting even if the User is OOO.  It seems urgent to connect those 2 features, so that the Meeting is able to understand that the User is not available during the OOO period.  ... Exibir mais

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. ... Exibir mais

Hi HubSpot Product Team 👋,   We need a better way for Admins to track expired HubSpot certifications across our organization. We have hundreds of users across multiple countries, and manually checking each person in the "My Team" dashboard is extremely time-consuming.   While the export feature is helpful, it still requires manual work to filter out expired certifications. A centralized dashboard or automated report that only shows users with expired certifications would greatly improve efficiency.   💡 Suggested Solution:   A new filter in the "My Team" dashboard to show only users with expired certifications. An automated report that Admins can subscribe to for periodic updates (e.g., monthly) listing expired certifications. A notification system where Admins receive alerts when a user's certification is about to expire. This would allow us to keep our global teams up to date with HubSpot best practices without unnecessary manual effort. Thank you for considering this improvement!   Best, Francesco Collacciani ... Exibir mais

Currently, HubSpot allows for bulk user creation via CSV import by uploading email addresses. However, assigning permission sets and teams still requires manual work after the users are created.   For companies with global teams, this process becomes even more time-consuming. We have teams across Europe, North America, Asia, and Latin America, each requiring different permission sets and team structures. Manually assigning these settings after every new hire or organizational change is inefficient and prone to human error.   Proposed Solution: Expand the current CSV import functionality to include columns for Permission Set and Team. HubSpot would then automatically assign these attributes during the import process. If a permission set or team name doesn’t match an existing one, an error message could prompt users to adjust their CSV. ... Exibir mais

The Super Admin Role should be available as a "Seat" allowing for functionality to set up and edit Sales and Service Hub Seat options.    As a super Admin I don't need to USE sequences, but I do sometimes need to set them up for sales hub seats. Similarly I need to be able to set-up and troubleshoot Service Hub functionality but not necessicarily USE inbod or helpdesk.    The option to "Log In As" is an option, but time consuming and not great for audit logs and users actively working in the system. it would be better if a Super Admin Seat was an option to have full setup functionality and testing ability of other seats.  ... Exibir mais

Currently for Task Permissions, I can set them to be either View/Edit either All, Their Team's or Theirs only.   I would like to be able to grant certain teams within my organization the ability to view/edit tasks from other Teams without having to give them access to ALL tasks.   The specific use case for my company, is that we have three separate Sales teams. I would like these teams to be able to view the tasks from the other teams, while preventing them from seeing my own tasks (my tasks are usually for administrative functions and don't need to be clogging up another user's screen) ... Exibir mais