Users who can't delete companies can still merge them

Smart CRM & Sales Hub CRM
1

We’ve limited the admin rights of our users so that they can’t delete companies.

That way we can make sure that nobody’s messing up the database.

However, we still want them to have the ability to edit and input information.

So they can edit but not delete companies.

HubSpot includes the “merging” of companies into the EDIT.

So actually, the users can merge companies… and therefore delete them. Right? That makes no sense.

If they can’t delete, they should not be able to merge companies.

2

Hi @jeremypatay,

You’re correct and I agree. Other users have requested this before: https://community.hubspot.com/t5/HubSpot-Ideas/Separate-user-setting-permission-for-contact-merges/idi-p/260141

I’d recommend commenting and upvoting to follow the request. The product team reviews these requests based on their popularity.

You can also help other users find this request more easily by accepting my reply as a solution. I’d appreciate it, too.

Best regards!

3

thanks. i’ve searched but could not find any. !

4

Hi @jeremypatay,

Good news! This is now in private beta:

Account Settings

Merge permissions for Contacts, Companies, Deals, Tickets, and Custom Objects

December 12, 2024

What is it?

We’ve added new permissions enabling admins to control who can merge Contact, Company, Deal, Ticket, and Custom Objects.

Why does it matter?

Admins can now better maintain data hygiene as they gain more control over who can merge records. This resolves the concern of needing to grant broad editing permissions, allowing them to fine-tune access specifically for merging, ensuring data integrity while meeting users’ job requirements.

How does it work?

Admins can easily manage user permissions by navigating to “Users & Teams” in settings. Here, they can set appropriate access levels for merging records, such as Contacts, Companies, Deals, Tickets, and Custom Objects, ensuring users have suitable access (e.g., all contacts, their contacts, team’s contacts, none).

By default, a user’s merge permission for each object type will match their edit permissions for that object type.

Known limitations:

Merge permissions check is not enforced on some pages clearly in the UI, including merge pop-up window in record page, Help Desk and Manage Duplicates feature. However, the permission is enforced on the backend so it will still block the user from completing the merge.

Who gets it?

All Hubs and Editions

You can find the private beta here:

736×470 114 KB

If it’s now showing up there, you’ll have to be patient for a bit longer or reach out to your customer success manager.

Best regards!