Merging permissions

[JoaoDemarchi]

We'd like to restrict record merging separetely with a specific merging permission.

Currently the merging functionality is enabled within the editing privileges, but sometimes we want to restrict merging even though the user can edit a record.

Today, we have that capability with importing records. A user can import records if they have editing permissions, but only if they also have the specific importing permission set.

It also would be good to define a specific merging permission within the object settings:

[LudmillaGarcia]

I believe this would be a great feature to have!

[ThaisCampbell]

+1

[Jnix284]

This would be really helpful, especially since merged records can't be unmerged

[Josh_Berman_8]

Because editing permissions enable you to merge, the only way to not allow HubSpot users to not merge is to take away their editing rights.

Dependent on how you use Hubspot, as @Jnix284 stated...merging cannot be undone. So because merges are non-reversible, it should have its own level of permissions and not tied to "editing".

We have an unspoken rule to not merge, however that doesn't mean it doesn't happen.

[TWallen]

Upvoting this idea. It's important to us for permission sets to allow us to disable the ability to merge certain objects.

We have an integration that relies on Deal IDs. Merging two Deals in HubSpot assigns a new record ID to the remaining record. It's causing issues.

[lukecullimoreBi]

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.

[BennyP]

+1 @lukecullimoreBi!

@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

[SNHernandez]

+1

[JChlostaGS]

Having this permission set would be very valuable! Def need this +1

[Sibiz34]

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. 

[UlrikeB]

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?

Thanks

[cdcolbeck]

This would be incredibly helpful.

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.

[VCunningham]

This is much needed for our team.