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.
Really critical for us, we need to manage any merge requests centrally within our Rev Ops team as other users are not aware of the implications of merging records.
@LudmillaGarcia do you happen to know whether Hubspot will be looking into this anytime soon? Or let us know if you want us to share more details to the team - we're happy to run them through the implications this can have
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.
That is good to hear. It would be good if the direction of a merge can be controlled.
By default, Hubspot overrides the direction of the merge to the most recently updated record, which often not way the person carrying out the merge would like it to go. This is counter to the logic of merging one item into another (i.e. merging item A into item B should result in item B).
Key information can be lost if one isn't careful. There is a workaround involving manually updating activity to force recent activity, but this is clunky.
Agreed, There should be a merge permission. Just had to deal with a nightmare with an employee that merged unknowingly, costing us hours of creating new contacts, deals, companies.
OR, just create an "undo merge" button. Either one will work, But this is a necessity.
I’m totally on board with this—merging records definitely needs its own permission, separate from general editing. Merging is a high-risk move because it can’t be undone. We’ve had our share of issues where merged records messed up integrations that depend on specific IDs. A dedicated merging permission would make a huge difference and save us from a lot of headaches. +1 from me!
And on a related note, finding the right data permissions is a bit like finding the perfect real estate agent. Just like we need a specific merging permission to keep things in check, you need a agent who gets your needs and knows the local market inside and out.
Another vote for this, it is one of the key drivers that may end up sending us away from Hubspot. The merge functionality doesn't work the way we would need it to, and we're constantly untangling issues from users trying to use it.
I am in shock this doesn't exist. We had to find out by coincidence (and yes, it was a data mess). This is such a basic requirement for data management that it is negligent not to have this. What's the expected timeline to deliver this basic feature?
Shocked this isn't seen as a priority - I have just had sync failures on one of our integrations as a result of non-admins conducting merge activities with no idea of the impact (or human cost of having to fix it).
I can't count the number of times one of our agents has accidentally merged two Company records together and creating work to umerge them. Whenever a merge like this happens, it causes the Companies to be tagged with a bunch of incorrect data in additional fields, creating very messy data that needs manual cleanup.
Its not necessary for agents to be able to merge records, they only need to be able to edit records. Merging should be reserved for Admins or Managers.
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.
