Gute Ideen sollten geteilt werden

Hi HubSpot Community,   WHO: Companies/Organizations that may communicate with clients that have sensitive or confidential information/material that needs to be tracked, but not seen by others in the organization.   Goal: Allow multiple teams to have access to the the same contact records, but have restrictions implemented based on "Users & Teams" to restrict access to see emails from seeing them.    Example: Sales & Tech Support (two separate Teams) are able to communicate with the same contact via email, but Sales can't see Tech Support's emails and Tech Support can't see Sales' emails.   Value: This addition will allow organizations to continue to maximize HubSpot's capabilities in tracking/logging emails for organizations, while also assuring there is a layer of added security/protection.   No examples or screenshots at this moment. ... Mehr anzeigen

One common challenge faced across business units and teams is the limitation of having only one default value for properties in HubSpot.   Essential properties such as names and [object] owners are shared among various teams within an organization. However, assigning a single default value for these properties poses significant constraints and inefficiencies.   HubSpot Enterprise Account with Business Units still has only one Default value for properties used across teams   Our current workaround: Currently, teams often resort to reaching a consensus on generic default values for shared properties. While this works in some cases, it becomes problematic when teams have divergent needs.   For instance, the "Contact Owner" property might require different default values for different business units. This forces teams to create custom properties for each unit, duplicating efforts and complicating data management. To address this challenge, I propose expanding HubSpot's property management capabilities to allow for customizable default values on a per-business-unit and -team basis. This improvement would empower teams to tailor default property values according to their unique requirements without resorting to creating redundant custom properties. ... Mehr anzeigen

As a super user of HubSpot working within a marketing agency, each time we set up a new client I have to go through the motions of the guided tutorials of "how to use HubSpot" can we add a checkbox at the user creation that disables these initial walk throughs of the platform? ... Mehr anzeigen

So to keep users in both HubSpot and Salesforce in sync you need to match on both email and full name of the user. This is not ideal for my organization (email only or at least customizable match settings here would be better), but I can speculate as to why HubSpot set it up that way and I can work with it for now.  However, can we please at least make the user match case-insensitive? Currently, the below example will not sync these 2 users.  HubSpot User: John Smith, john.smith@test.com Salesforce User: JOHN SMITH, john.smith@test.com ... Mehr anzeigen

Whilst it's possible to add an alias to a user email but this doesn't help in call cases. It would be really useful if the actual user email address, linked to that user could be amended for cases where it has been entered incorrectly or doesn't match associated, linked accounts. Currently, if this happens, we have to follow a long process of creating a new account, moving everything across from the incorrect account and then removing that account. It would be great if we could just correct the main account and then add an alias to it if necessary.     ... Mehr anzeigen

We really need the ability to completely disable the file manager via permission sets. Please make this a feature! ... Mehr anzeigen

I operate in a regulated industry. Outgoing communications need to be reviewed and approved by our Compliance team. We need to be able to take away the sales team's ability to create unapproved templates and sequences. ... Mehr anzeigen

Currently, you can only do asset partitioning for marketing emails. We would love if we could also do this for sales emails. Here is our use case: Our Accounting team will periodically need to send payment reminder emails to a client including past-due notices. These (potentially embarassing) emails do not need to be seen by EVERYONE. If all emails sent by the accounting department could be "hidden" from other teams, but still be attached to the applicable contact/company/deal, it would greatly help our workflow and communication. ... Mehr anzeigen

Exclua ou desabilite quaisquer contas inativas após um período de 45 dias de inatividade, onde for suportado. ... Mehr anzeigen