Les grands esprits se rencontrent

In this article, when a user is setting up 2FA it advises that back up codes are automatically generated.  HubSpot customers have different levels of security requirements.  It would be excellent if we could give HubSpot customers the ability to turn off the option to generate back up codes or not. ... Afficher plus

Allow settings of permissions for attachments. Currently, permissions for uploaded attachments can be controlled via notes. No permissions can be set at all for attachments that are received via e-mail. Since some contacts have to be visible to many employees, but certain sensitive attachments are not intended for everyone, this is very unsatisfactory.   Suggestion: Assign permissions separately to attachments, regardless of whether they are uploaded or received by e-mail. ... Afficher plus

Right now I can create permissions so that some team members can't see activity from certain contacts or companies based on owner. However, they can see a preview of conversations by looking at the activity report, making those no long completely private.  ... Afficher plus

Hi,   I have a suggestion about permission sets and teams. Typically when creating permission sets, I think of the roles and teams who need them.    Normally I create the permission sets and then the teams in the organization. This helps us to manage users at scale.    An important but missing feature is the ability to associate a permission set with a team. If we had this ability then we could manage and control permissions by groups of users or teams more effectively.    Currently, we have to scroll through users and manually add a permission set to each user. When you have a large number of users in HubSpot this can become unmanageable and a source of potential errors.    Hope this makes sense to the enterprise users out there.    - Dave ... Afficher plus

Love the new sales calling features for HubSpot.  It would be awesome to have the ability to create a shared line for HubSpot for inbound calling that routes to multiple users  (e.g. a company 1-800-support) line that any permissioned user can pick up through conversations and perhaps automatically opens a ticket... ... Afficher plus

Hey HubSpot,   We'd love to see something in the way of adding conditional logic as to WHEN somebody can edit a property rather than just WHO can edit/see etc   E.g When the Deal is Deal Stage "Pending Approval", properties such as "Conditions", "Amount", "Submission Date" cannot be updated.   This would allow for greater confidence and control around time crititcal processes and ensuring that information is not being incorrectly updated after a submission where details must remain the same for verification purposes etc   Ideally this would be similar to, but is not quite the same as User Permissions on Properties.   Thanks! ... Afficher plus

We have separate business units with different departments that use Service Hub (Tech Support Team #1, Tech Support Team #2, Warranty Team #1, Warranty Team #2, General Customer Service, Design Support, etc...). Each team has a specific specialty they serve within our company. However, our customers don't always submit their requests to the correct department. Therefore, our agents/users need the ability to move the ticket into the appropriate pipeline. But in order to give them access to do so, they get full access to the entire pipeline.   It would be nice if we had permissions similar to Objects where we could give a user None, View only, Transfer only, or Edit permissions to a specific pipeline. ... Afficher plus

Currently we are not able to select permissions around who can schedule or send a transactional email. With so many users in our account (large Marketing team), it would be ideal to have a permission like this to ensure a transactional email only goes out when necessary. Since there is minimal difference in setting up a marketing email vs. a transactional email, this could easily become an oversight. Making this change would allow for more control and security within our account. ... Afficher plus

Currently, I don't like how there is no way to restrict users from adding a new custom view to an index page. . .     This results in the following problems at the enterprise level:  1) Lot's of duplicate views  2) Inconsistent columns / properties included 3) Innacurate filtering 4) Having to log in every account to remove a view just to delete/archive an old property.   In a perfect world, it would be awesome if we could set permissions up so that the team lead is the only person able to add custom views.    Thus non-managers need to run their requests through them or the admin. Standardizing would greatly improve their experience with views.  ... Afficher plus