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.
Today I received a user who needs to set the mandatory properties at the user level when moving the deals from a stage to another, which would be possible with more granular permissions
Hoje recebi um usuário que precisa definir as propriedades obrigatórias no nível do usuário ao mover os negócios de um estágio para outro, o que seria possível com permissões mais granulares e específicas
Agreed! Causes a lot of issues for me with our other system that's in sync with Hubspot, breaks the sycn data and causes errors I can't fix outside of completely deleting the contact and adding them again
This would be a really important addition that woud reduce the risk of inexperienced users merging contacts and thereby causing the loss of data which is not retrievable.
The ability to designate permissions for merging is critical as any records can currently be merged by anyone and impacts data quality and integrity. This is especially important for companies and contacts. The act of merging two records has more of an impact that if one was deleted (since there is no way to 'undo' a merge). Deleting can be restricted and deleted records can be restored. Two key items for merging:
1.Permissions to restrict who can merge (similar to delete)
2.History details for merged records. When merging two records, the only information provided is "<Record X was merged with <Record Y>". There is no reference to "who" completed the merge and which records were merged.
The ability to designate permissions for merging is critical as any records can currently be merged by anyone and impacts data quality and integrity. This is especially important for companies and contacts. The act of merging two records has more of an impact that if one was deleted (since there is no way to 'undo' a merge). Deleting can be restricted and deleted records can be restored. Two key items for merging:
1.Permissions to restrict who can merge (similar to delete)
2.History details for merged records. When merging two records, the only information provided is "<Record X was merged with <Record Y>". There is no reference to "who" completed the merge and which records were merged.
Seria ótimo essa funcionalidade da permissão e se possível também desfazer a mesclagem, pois uma vez realizada não é possivel reverter e para criar um novo contato de forma manual acaba infringindo a LGPD.
Absolutely agreed. We have an issue in our organization where HubSpot is integrated with our primary inventory app. Our issue is specifically with Users merging Deals. When this happens, it creates false data in our primary inventory app which necessitates manual workarounds that would not be necessary if we had the ability to prevent Users from merging Deals. The only option we have is to make company-wide posts imploring Users NOT to ever merge Deals. The impacts of Users merging Deals are fairly widespread - we see impacts in reporting, accounting, and other important areas.
I'm not sure why HubSpot simply doesn't just roll out the ability for Super Admins to DISABLE the merge feature; it would be a huge benefit and would save us tons of time having to do tedious manual workarounds as well as saving time having to make company-wide posts explaining to Users why this has a negative impact on our database.
Posting here because I just had correspondence with a support agent who recommended upvoting this post and posting myself because this feature is currently unavailable.
Debe ser un usuario registrado para añadir un comentario aquí. Si ya está registrado, inicie sesión. Si todavía no está registrado, hágalo e inicie sesión.
