Las grandes mentes piensan igual

Hi there,   We need the bility to restrict certain Contacts/Companys/Deals to certain uses only, for the purposes of Insider Information.   We already utilise the Team permissions but need the ability to restrict specific Contacts/Company/Deals that may be subject to Insider Information/Marklet Abuse etc.   Another option (if feesable) would be a 'restricted list' where the deals/contacts/companys on that list were restricted to certian users that we could determine. That would also require the ability to have mulitple restricted lists.   An urgent fix to this is desperately needed please! ... Mostrar más

HubSpot offers similar functionalities with restricting access to contact and deals. Having the same control over permissions to the lead object is necessary. ... Mostrar más

When exporting the list of users from your settings ("user table"), there are several properties that are available as filters, but are not included in the exported file.   Specifically, I would like to request that the "Invite Status" user property be included in the user export file.   We are a large organization with many HubSpot users, and therefore automate our user provisioning. Due to variable onboarding schedules, we often have many users at once who are in the "invite pending" status. This becomes a problem, of course, when a user is in a pending status for more than a few weeks.   As part of our adoption metrics, we look to determine the percentage of weekly/monthly/etc. active users. Since the user analytics tools cannot do this in the UI (yet!), we export the user list and report via Excel.    There are two key problems with the export function, as it doesn't behave in the way a list or index page export does:   1. All records will be exported, even if you have filters applied. For example, when you export a filtered index page, you can export just those records in your filtered view. So if I apply a filter to only show users with an "Invite Status = pending," that will not be reflected in the export. This is problematic for us because it will falsely inflate our total number of users when I'd like to only report on accepted users.   2. There is a lack of consistency between the properties shown in the UI filters and the properties being exported. The following properties are not included in the exported file:   Invite status (ironically, this is the very first filter listed on the page, and yet it's not included in the export) Access (this is included, but in the export it's called "Permissions") Calendar status Calendar sync Email status Extra teams (this is included, but in the export it's called "Additional teams") Main team (this is included, but in the export it's called "Primary team") Partner Scheduling pages Seat (the export does include a "Paid seat" property, but it does not specify which paid seat the user holds - it simply says "yes/no")   Additionally, when you generate an export, the shown properties are the same each time (and not comprehensive). It should beave similar to an index page or list export where you're asked if you'd like to include all properties or just those in your current view.   While gaining export acess to the "invite status" property is my primary objective here, I imagine it is quite frustrating for other customers to not have access to properties like "Scheduling pages" or "Seat" in their exports as well.   Please update the user table to behave more like an object index page, and more specifically, update the file export to align with the properties shown in the UI filters.       ... Mostrar más

Whenever a user is deactivated, the current best practice is to go through all assets individually and pinpoint where the deactivated user may be present (such as 'assign as contact owner' action in workflows). While it's easy to filter for objects deactivated users owned and bulk re-assign them, the deactivated user management for views, reports, lists, workflows, sequences, etc. is seriously lacking. It would be great if we had the ability to view/export all assets where a deactivated user is present! ... Mostrar más

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. ... Mostrar más

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. ... Mostrar más

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? ... Mostrar más

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 ... Mostrar más

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.     ... Mostrar más