Great minds think alike

It would be greate to have the possibility to also setup "Create Forms" for specific Teams (like the team views).  This would help so much making sure that f.e. each specific teams has by default the most important ticket propertys visible when creating a new ticket. -> we are working with the Business Unit Add-On, so we have to set up many things differently for our teams as they work so individually. ...read more

Currently, within HubSpot settings, it is possible to enable approval permissions separately for email marketing content, landing pages, and website pages, ensuring these can be reviewed before being sent or published online. However, this functionality falls short when dealing with the frequency of updates that content often undergoes in a real work environment. The limitation lies in the fact that each user can request approval for a page only once. HubSpot team, please consider the possibility of allowing users to submit approval requests multiple times. Furthermore, once the content is approved, users should also have the ability to publish it, just like the approver. This enhancement would align more closely with the dynamic content strategies businesses require. #Users & Teams & Permissions  #Account Settings   ...read more

I would like it if the members of my sales team could assign leads to themselves without being super admin. This is not yet possible in the beta version of the lead overview. ...read more

It would be incredibly useful to see the time(s) that users were actively using the system. We worked with CS to set our session timeout to an hour so that users aren't indefinitely logged in, but it would be super helpful if our managers could see how much time someone is actually in the system. ...read more

We have a large number of users with frequent turnover, so we're often deactivating users.   Because we cannot filter incomplete tasks by deactivated users only, we have modified our process to delete, complete, or reassign any assigned incomplete tasks prior to deactivating a user.   In the UI, incomplete tasks assigned to a user will appear in the section at the bottom titled, "Review user's records and assets." The number shown will specifically reference the number of incomplete tasks. When clicking on the number of incomplete tasks, or clicking on "View all," however, you are taken to a page of ALL tasks assigned to that user.   If the user detail page is specifically showing incomplete tasks, it doesn't make sense that clicking on either/both of those links would not filter down to the incomplete tasks as well.   Because "task status" isn't shown as a quick filter at the top of the index page, it's especially annoying that each time, I have to go into "More filters" and add "task status = not started" to find the lingering incomplete tasks I need to address before deactivating the user; completed tasks will always default to the top too. This adds a ton of unnecessary clicks and really slows down the user management process.     ...read more

With the new change, users can edit but not view records if they are selected on a custom user property. If someone can edit a record, they should be able to view that record. This is creating a mess in our system since we often have several users on records, and they are not able to see those records anymore. The only way to allow them to view those records is by assigning view permissions for the relevant objects to "All records", which is a security risk.  ...read more

Hi HubSpot Community, We’re currently assigning each lead to three product managers for products X, Y, and Z. We’d like to restrict visibility so that only these assigned managers can view the lead, preventing others within the same product line from accessing it. Does HubSpot offer options to limit access or adjust visibility settings for specific users assigned to each lead? Thanks in advance for any guidance! ...read more

At the moment the audit log allows us to see which user created or updated a record but we can't see a log of who viewed which record.   This would be required for data security and privacy audit. ...read more

Currently, either providing full access of a contact to a certain user/team or not giving access at all is what's possible. The proposal here is to find a balance where a User/Team that perhaps is not owner of the contact, should be able to at least see the name and be able to associate to other Objects but without seeing the whole details of the contact. This brings privacy on one hand, scalability on the other hand because you can still maximize one of the main uses of HS which is the association between objects without having to open the whole cards and perhaps share sensistive data to other team members that don't need to see certain information. ...read more