Grandes mentes pensam igual

Goal To use a Preset in order to apply a specific email signature to all Users of certain teams; and For the Email Signature to include the User's Job Title Issues w/ HubSpot ✖️If the User already created their own email signature from their user account, then it will override the Preset email signature. ✖️There is NO way to delete all email signatures created by an indivudal User once they exist. ✖️Only the following User properties are OOB available to personalize an email signature created via a Preset: First Name, Last Name, Phone Number, Email, Meeting Link, Profile Picture ✖️ (Custom) Email tokens do not map to User properties. Instead, you have to manully type in the value for each (custom) Email Token and each User assignd to the Preset. Solutions Email Signature User Property (TRUE/FALSE) HubSpot should have a User property (TRUE/FALSE) for whether a User has created an email signature or not. This would help admins out who want to leverage presets to apply email signatures at scale. HubSpot should either allow a User to delete ALL email signatures they created -OR- make it possible for a Preset's email signature to override.  Email Tokens for Email Signatures in Presets Either ALL User properties should automatially be available as tokens -OR- it should be possible to map a User property to an email token. ... Exibir mais

We use the built-in Automatically deactivate inactive users feature, which currently runs after 90 days of inactivity. We’d like to have the option to shorten this threshold to 30 days for security compliance. ... Exibir mais

The new Projects feature is generally very good and promising. However, with the current limit of only 5 pipelines, it’s not feasible for us to use it effectively across all our HubSpot users. We would need the ability to create more than 5 project pipelines to make full use of this feature. ... Exibir mais

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.  ... Exibir mais

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.  ... Exibir mais

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. ... Exibir mais

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.  ... Exibir mais

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. ... Exibir mais

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. ... Exibir mais