Grandes mentes pensam igual

Some integrations can process sensitive information. It would be nice for the Admins to be able to restrict access to certain integrations for a group of users for example or just one person. This could be through the "Permission sets" settings or the apps integrations settings or even the ability to remove the integration view for certain users from the right pane in contacts and deals. ... Exibir mais

This issue has been brought up a few times in the Community, but it doesn't look like it was added as an Idea.   When an employee leaves, we deactivate their account in HubSpot. This allows us to preserve historic detail. This is great and something that we want.   However, the deactivated user is still available to be assigned as an owner of stuff. It should be possible to prevent a deactivated user from being assigned to anything after they are deactivated. ... Exibir mais

Our team is needing a way to limit which units a particular user or team is assigned to. For example, if we have a team member who does support for one of our units and not another, I need to find a way to limit their access only to the unit they support.   Ideally, we'd be able to create roles for units and assign them to users based on which team they're a part of at our organization.   I'm not seeing any work-arounds for this, or any way to assign a user to a particular unit, which is somewhat disappointing and defeats the purpose of much of what we needed business units for. ... Exibir mais

Do not allow non-admin users to access and view other users within the Portal.   If a user does not have the permission allowed for Account Access - they should not be able to view User and Team information!   For portals where we are supporting internal and external users, emails and access levels are displayed.   I see this being a significant security issue - for: 1. Sharing emails and contact details with users who should not have access to this information 2. Providing details for admin users that if a users account was compromised could be used to try and get other access        ... Exibir mais

Currently, a user can be a 'primary' member of only one team. The user can be added to other teams as an 'additional team member', but many team features are unavailable to these 'additional' users (see list of restrictions below).   This is problematic and causing us considerable pain because some users need full access to multiple teams, e.g. an individual who is multi-role, or management/supervisory staff who need to monitor what goes on in the team. This is particularly true in smaller businesses. The one primary team restriction seems unjustifiable .   Restriction's on 'additional team members': https://knowledge.hubspot.com/account/assign-users-additional-teams These users will not be included in any team reports, routing rules (e.g., conversation routing rules), team notifications (e.g., form submission email notifications to a team), or workflow rotation actions. They will also not be able to view any custom records views set up for the team.   The solution is to allow users to be primary members of multiple teams.   Any feedback? ... Exibir mais

I would love to give sales managers access to create templates for their team, however i don't want to give them super admin permissions for our whole account! Please amend the permissions functionality to allow this. ... Exibir mais

It's great that HubSpot supports several different types of 2FA including authentication apps but most of these are phone based. Phone based systems are increasingly vulnearable to hacking (digitally, physically, and human engineering). While no system is perfectly secure nor perfect for every use but hardware based solutions like Yubikeys are an affordable highly secure way to implement 2FA. Please support Yubikeys! ... Exibir mais

We've had a sales person leave our company and found it somewhat challenging to cleanly manage their associated data while we find and onboard their replacement. It would be very helpful to have a way to temporarily re-direct a deactivated user's tasks, deals, and other objects to a manager without reassigning ownership completely. It seems ineligant to create a custom property for each of the relevant data objects or manually sort out all the objects which need to then be reassigned from the manager to our new hire when they arrive. ... Exibir mais

Hello community 👋 and product team ✌️   Background Today it is possible to create and pin your own custom views within contacts, companies, deals, tickets and more (lets use the word objects from now on). A HubSpot user may edit columns, filters and save these according to their own preferences.    A view 👀 can either be standard, created by me, or created by others (see picture and ignore Swedish content). Once a view has been created by me no one else can edit this view and save it for all users 👥 - instead they have to clone their own version of the view in order to change it.          Issue We are growing our company fast ⏩ and we want to be able to scale our staff up and down without it affecting the infrastructure of what we have created. If one staff member decides to quit and move on to a new company - and that staff member being a core creator of the views that all other HubSpot users in our portal uses - we could be in big problem.   Why? All these views created by others can be pinned to my default view. I will have a standard set of up to 5 views in my portal that I will use in my day to day management. If the staff member that created that view quits users could be stuck 🔒 with old standard views in their pin bar without knowing.        Idea for solution (proposal for the product team) 🤗 There are several ways to solve this issue. Some better than others. I would really love them all to be delivered 👍 but as we all know thats not always possible.    A) Make it possible to pass ownership of a view Make it possible for a view owner to pass the ownership (and there by the uniqe rights to edit the view) to an other HubSpot user of the same portal.    B) Make it possible to collaborate in creating standardized views Make a setting so that a view can be collaborated on by all HubSpot users. Once a change is made by once user it will affect all others. Perhaps a small information box upon saving the view informing the user that it will affect all other accounts.    C) Make it possible to set up ownership of a view to a team Make a setting so that a view can be collaborated on by a specific team of HubSpot users. Once a change is made by once user in that team it will affect all other users (in the team or not). Also here recommended to have a small information box upon saving the view informing the user that it will affect all other accounts.  ... Exibir mais