Great minds think alike

I manage HubSpot for sales reps at my company. We want to prevent reps from automatically opting out contacts that they enter. To do that, we have to turn off all marketing access permissions. This prevents them from being able to see the content of the marketing emails that have been sent to the contact or which ones they have opened/engaged with. I think we need an option specifically to prevent opting out, but still allowing viewing of marketing access.  ...read more

I think it would be a great addition to Hubspots Pipeline and Ticketing functionality, if we could restrict a given users ability to create tickets within a pipeline, while that User has access to work and receive tickets in that pipeline.   At present, you would need to disable the users access to work on the tickets overall to stop them manually creating tickets.  ...read more

With the update to the seats model, it would be good to be able to manage both user permissions and seat access on the same page. Currently we are having to flick between mulitple pages when setting new users up. ...read more

Please consider adding these features:    1) User property/user property option that allows a user to be selected without assigning ownership of the record to that user   We often have a need to be able to select users for a property, but don't want the selected user to be assigned as an owner of the record. For example, selecting a user that managers want the record assigned to so that other managers can review the assignments before they are made.   We've resorted to using a dropdown that has to be continually managed as users are added/removed. This also means that workflows become more complicated as we cannot easily relate dropdown property options to user property options (e.g. if 'Company owner' = 'Transfer to owner', clear 'Transfer to owner').     2) Ability to limit which users are displayed as options on the user property by Team and specific users   Having to scroll through all users in the portal, including those that are inapplicable to the specific use of the user property, means that the search bar must be used, which, in the case of a user property where only a few users need to be selected from, means that a significant amount of time must be spent searching compared to if the user property were limited to only those relevant few users.  ...read more

En los filtros avanzados de la gestión de usuarios echo de menos el filtro por correo electrónico.  Creo que es diferencial porque al gestionar las usuarios en masa es un filtro único ya que podemos tener usuarios que aún no han activado su cuenta o usuarios cuyo nombre y primer apellido coincida.  En cuentas con más de 100 usuarios comienza a ser necesario este filtro. ...read more

Para las licencias de View Only, no se permite establecer conjuntos de permisos.  En mi caso, mis usuarios SOLO pueden visualizar contactos, empresas y negocios de sus equipos, no deben visualizar nada de toda la cuenta. Tenemos más de 50 equipos diferentes en 16 grupos de trabajo de diferentes países. Cada vez que concedemos o cambiamos una licencia de View Only, debemos modificar manualmente el permiso, no es operativo. ...read more

It'd be great to have a dynamic Deactivated/Removed User option to avoid using custom code for the Criteria. For example, it makes no sense to manually select 5, 10, 20+ accounts and to keep manually adding those over the course of years. ...read more

When a user's permissions are set to private (own only) this should apply across the board (marketing emails, segments, dashboards). It's unrealistic to expect a user to manually go back in and set everything to private everytime they create something new.    The same applies to team only permissions. Why can't the default visability features tie in with the permission set? ...read more

(Posting on behalf of a customer)   We request the feature to restrict the manual sending of WhatsApp messages based on the value under a property X.    Use Case:    Our Sales team has a strict process for using WhatsApp. They are only allowed to contact a prospect via WhatsApp once the associated Deal has reached the "Qualified" stage.   Currently, manual sending is available on the Contact/Deal record without any property-based restriction. This creates a risk of sales reps prematurely sending messages to contacts who have not yet passed the necessary qualification stages, which can negatively impact the prospect's experience and the credibility of our process.   Proposed Implementation:   Add permitions to record activities or send messages, mails, etc. based on record properties. For example, if property "stage" is "client", action to send emails and WhatsApp messages is available. If not, activity is greyed out.    Thanks! ...read more