Las grandes mentes piensan igual

View only seats can review, analyze and compare emails. Shouldn't they be able to see our social channel too? Please add social to view only permissions so outide stakeholders can see the posts, their performance, and compare, etc. ... Mostrar más

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.  ... Mostrar más

We would like to restrict visibility of our Subscriptions in HubSpot for most users, but currently, this isn’t possible. Unlike other objects, there’s no option to disable access or limit visibility to only the subscriptions a user owns.   We’re aiming to grant external users access to our HubSpot account, and this limitation is our primary roadblock.     ... Mostrar más

Currently, admins can log in as users to see their views, but this process is time-consuming. In larger teams with varied permissions and team-specific views, admins frequently face questions like "Why can't I see X?" Adding a "View As" dropdown that allows admins to select any team member and see precisely what they see would save considerable time. This feature is already available in the sales workspace, so extending it across the platform would be incredibly valuable. ... Mostrar más

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! ... Mostrar más

We often need to treat a team manager differently from other team members. For instance, we might want to automatically assign leads to the sales team but exclude the manager from receiving them.   Now that the user settings include 'management hierarchy' information, it would be extremely useful to leverage this in the workflow's object assignment function. This would allow us to assign tasks to team members while automatically excluding the manager based on their position in the hierarchy.   Without the ability to use this hierarchy information, we face two challenges:   1. Selecting Individual Users for Rotation: We have to manually choose specific users to rotate assignments among. This approach becomes inefficient whenever there's a change in team personnel, as the workflow needs to be updated each time. 2. Assigning the Manager to a Different Team: Alternatively, we might assign the manager to a separate team to exclude them from certain assignments. However, this doesn't accurately reflect the true team structure and can lead to confusion. By integrating the 'management hierarchy' into the workflow assignments, we can maintain an accurate team structure and ensure the workflow remains efficient even as team members change.   ... Mostrar más

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. ... Mostrar más

I want to enable bulk delete (specifically index view, allow users to select multiple records and delete), but I want to enable it by user/permission set and by object.    Where we currently see, as admins, the ability to choose View, Edit, Delete, it would be awesome if Bulk Delete was the max permission for the object.   ... Mostrar más

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. ... Mostrar más