Great minds think alike

Thought it'd be useful if we had the following features to help secure orgnizational data on hubspot, by easing the deactivation process of employees leaving an organization: 1. Upload a list of offboarded employees and deactivate them in one shot. 2. Automatically identify and alert when a user's email address is no longer valid, and prompt to bulk deactivate such users.  ...read more

A senior member of staff has regular meetings with a director of one of the companies - he does not want this to be shown on HubSpot.    This meeting was set up in Teams, not in HubSpot. As he doesn't use HubSpot, but need access to review deals. The meeting comes up under the companies/contact information for the whole business to see.    It would be nice to have a feature to opt out of HubSpot calendar syncing.   ...read more

Currently there is permission to access all contact properties or not possible at all, can we have it such that  we have one field in contact property that needs to restrict other users from editing. ...read more

We've had many clients who have asked for the ability to retrieve Object schema history. I am not referring to version history for specific records, which I'm aware can be accomplished through some of the older v1 APIs.  For example, a user changes/deletes a few properties on the Contact schema. We want to find the user_id of the person that made these changes. I don't know of a way to do this currently through either the UI or APIs.  Changes of this nature can have a significant impact on a company's HubSpot instance, so it's important that we're able to retrieve data surrounding these kind of events to have as full a view as possible of what occurred.  There appears to be an account history report you can export via the UI, described in the doc HERE The feature described above seems to provide a history of just about everything except what I'm looking for. Building on top of this would seem like the way to go. Or better yet, allow us to track this kind of thing through the APIs as well.  ...read more

This idea is for Super Admins and would provide the ability to run a list of references to a terminated Super Admin user (or their email address) within HubSpot in order to transfer to a new, active email address. When people leave, especially if they've actively developed many workflows and forms, automated emails and communiucations will continue to come from that user's email until the user is removed. However, for fear of breaking these flows and having Leads fall through the cracks, I do not want to remove this account until all references to the person's email are updated to mine or another heavily monitored email box. Even if this is possible on the back end to be done by HubSpot Support, I feel there is value in having the ability to run this sort of list to cleanup after a Super Admin leaves. ...read more

Hubspot only allows users on Primary teams to be mentioned in the Comments of an Inbox. Those who are on Additional teams can view the Inbox but cannot be mentioned. We have Super Admins and managers who need to be able to be mentioned across multiple inboxes.   This limitation did not used to be the case. It's hard to see what this change helps. If a user has an Additional Team that has Inbox permissions, this user is grayed out in the Inboxes Access settings, so there is no way to allow for mentions without changing the user's Primary team or the entire system of team permissions we had set. Neither can a user be added to multiple Primary teams.  ...read more

Hi,   May I know if we could provide users with access to contacts and companies but not allow them access to view or edit any emails or attachments that were logged? These users would still be able to see the emails but not the email exchanges or activities.   Thank you! ...read more

Hi, We are currently in the process to set up various Marketing processes (DOI, downloads, newsletter subscpritions etc). In this process we test a lot. However once an e-mail-adress was used, for example to test DOI, you can never use it again for testing-purposes.   This is quite impractical because you need quite a lot of email addresses in the course of a project set-up. It would be useful if Hubspot would provide a kind of test user with which such functionalities could be tested without having to constantly create new email addresses. ...read more

Currently, in case a user has permission to edit something (i.e. information on a Deal), this user has the ability to change these infos at any given point of the deal stage. For example, the deal owner is allowed to update the amount of the deal even after it's closed.   New proposed feature: after a given stage of the deal (in this case when it closes), the deal owner edit rights is changed, so he/she is not allowed to edit any further information (the amount, for example). This would allow for a better "gatekeeping" of crucial information while still maintaining the initial owner for reporting/analyses (as opposed to creating a Workflow to change the owner of the deal once it closes). ...read more