AS admin in companies with more than 50 users, we should be able to manage permissions to merge contacts since it implies "manipulating" the database by anyone who can edit contacts even if he is not aware of the impact merges could have.
Hi all - thank you for your feedback on merge permissions! I'm happy to report that merge permissions for Contacts, Companies, Deals, Tickets, and Custom Objects is now in private beta. You can request accesshere.
Hi everyone, thank you so much for the feedback! I wanted to share that we are currently working on Merge permissions for Contacts, Companies, Deals, Tickets, and Custom Objects. These permissions will be delivered by the end of 2024.
This is one of the few remaining sources we have our salespeople being able to muck up our attribution reporting :-(. This would be a welcome addition merge is as powerful as delete.
HubSpot team -- the inability to restrict end users' ability to merge records is causing MASSIVE issues for us. Especially because you cannot fine-tune workflow unenrollment behavior for ticket- and custom object-based workflows, meaning we have records being unenrolled left and right without any ability to control it.
As other users have said above, it's hard to belive that we're able to restrict an end user's ability to EDIT and to DELETE records, but MERGE -- in some ways, a far more destructive action, is somehow left open to anyone's whim. Of course in an ideal world, we would tell our end users "Please, do not merge records!" and they would listen. But you know as well as I do that this isn't how things work in reality.
I'm not joking when I say that this has created HUNDREDS of hours of additional work for our engineering team to clean up the wake that merged records leave in our data lake. It completely breaks our ability to sync these HubSpot records with the data in our other systems, removes them from vital workflows.....the list goes on and on.
PLEASE. I am begging you -- provide admins the ability to restrict or at least better control this activity. This is ludicrous.
I completely agree with this. Although our permissions team we want to limit is less than 50 users, so I wouldnt want to put a limit on the number of users within the permissions team in order to get this feature.
Is is extremely hard to manage the companies within HubSpot and keep track using the Record ID as the unique identifier when the users have the ability to merge. Not to mention, once the company is merged, there is no way to undo the merge.
It looks like this was mentioned years ago, but I hope that this is still top of mind to implement.
Our company is in need of restricting merge permissions based on the object type. For example, we cannot have users merge companies, but they can merge deals (for example of different object types).
We know that we can limit this by turning off "Editing" for company records, however, our team needs to be able to edit properties but NOT merge accounts together. We really need merging to be a separate permission outside of the overarching "Edit" permission.
HubSpot has added a property "Merged Contact IDs" that you can use in a workflow to provide notifications or create reporting for it, but there's still no way to limit the usage of this feature.
I'm joining the growing number of voices here chiming in. It's absolutely astounding that something as fundamental as being able to enable/disable merging records on its own hasn't yet arrived for HubSpot.
I've also faced recent situations where users are merging records that they have no business merging, but I can't remove their edit access without preventing them from doing other legitimate CRM work. HubSpot is making strides to narrow the gap separating them from Salesforce when it comes to reporting, lists, and views, but user permissions are still sorely lagging behind.
HubSpot, if you're listening, please address this huge feature gap!
@KNickolay@EHanratty Please consider following and upvoting this idea, which covers exactly the issue you're reporting. It already has 50+ upvotes, so let's add more to it so that the HubSpot product team notices!
