Salesforce IdeaExchange

1810

Permissions To Merge Without Permissions To Delete

As it stands, we must give users permissions to DELETE records, if we want them to be able to MERGE records. While that may make sense from the back-end, it is far from ideal from an administration point of view. The problem is that when a user deletes a record, they also delete related things such as activity history. We may also have associated campaign information, etc, which we want to preserve under merging. A sales rep may think they don't need to merge, just by looking at the contact data, etc. So they delete it, and we lose valuable information.

jhbenter 02/27/07	Fully agree. From user perspective there is a clear difference in deleting due to merge vs. deleting as through delete. So merge should work without delete permission.
April 02/28/07	I agree - we do not allow our sales managers to delete and it would be helpful for them to have merge ability!!
ErikM 03/09/07	This probably is tricky, because you in fact delete at least one record when it is merged with another. It would make much more sense, though, if it was not physically deleted at all, but rather modified it in a way that only a sysadmin can see it afterwards, and maybe roll back any changes. This way, you would not have to grant delete permission to the merging user. Even better, merging should be hooked to the Approval Process: a user requests merging and already prepares the records accordingly. It is then up to the assigned approver (having delete permission) to confirm or reject the request.
hayli 05/15/07	Merged Idea originally posted 12/11/06 Ability to merge accounts owned by 2 different users Have the ability to give users permission to merge any items (whether or not they own them) without having to give them system administrator access. Accounts are assigned to an outside sales rep, but the inside sales reps will create additional leads/accounts/contacts. When they look for duplicates they will find them but one is owned by them and the other is owned by the outside sales rep. The only way to resolve this is to have the outside sales rep do more admin work or contact the system administrators to do it.
manu 05/15/07	Merged Comment originally posted 12/12/06 Is this possible with Delegated Admin?
msadler 05/30/07	Merged Idea originally posted 04/11/07 Edit, Create, or Merge Contacts on Others Accounts Currently only an account owner, or somebody higher than them in the role hierarchy, can create or edit a contact at that account (even if you enable sharing rules). This means that any telemarketers/assistants who work with sales executives cannot merge contacts on the sales executives account unless they are higher than them in the role hierarchy. This leads to lots of extra work for somebody who is supposed to be out selling, and frustration for others who are unable to effectively help their team member.
Scott_Jorgensen 05/30/07	Merged Comment originally posted 04/11/07 I think it's possible that your sharing rule isn't setup quite right. You should be able to create an Account Sharing Rule that allows your telemarketers to edit, create, and merge Contacts in the Accounts owned by the sales executives.
BenPirih 06/12/07	I have solved this by creating a custom scontrol that fires javascript to hide the delete button. send me an email at ben@bpirih.com for the solution if your interested. This way you can allow the merge or duplicate detection without users having the ability to delete..
Cappuccino 09/25/07	Merged Idea originally posted 09/19/07 Make "Merge Accounts/Contacts" Independent from Delete Permissions I would like the ability to give certain users/profiles the permissions to merge account and contacts but NO delete permissions. Today, in order to have "merge account/contact" you also need delete permissions. I know technically during a merge data gets deleted and therefore it's logical but in practice I find that there is a difference. We don't want to give a certain user group delete permissions because the possibility of intended and unintended misuse is too big but giving them "merge account" would be fine with us. It would allow them to clean their data but make it difficult to go on a deletion spree. Furthermore, most of them wouldn't be able to figure out that they can misuse this do delete data, plus it requires ways to much work to use it accidentally (compared to the delete button which is clicked quickly).
saariko 11/28/07	There is a solution in SF exactly that handles that. The user does not have the ability to delete (button is hidden) but he can merge accounts. In your search site look for: "Merge Accounts" The first solution comes is: "How to allow users to merge accounts without deleting accounts?" I have set it in my org this way, and it works.
JenCalvert 12/07/07	I would like my delegated administrators to be able to merge accounts within their business division without having to have the "View All Data" as an option selected on their profile. We have multiple public groups in one org and would like them to manage their accounts for their public group without seeing other public group records.
rao_arimilli 12/27/07	I would like to have merge and delete capabilities separate. And, in addition, I would like to be able to create a validation rule on the merge to give a warning to the user that a particular field contains data that must not be deleted. It would be nice to prevent merging/deleting and to provide the warning at the same time. I understand this is not currently available.
salessupportasr Jan 10	Currently I feel that merging access is only allow to very backend people in my company. I think sales rep should not merge but send a request to have 2 accounts merge and the request goes to the sales admins ( who have the access to do so) My suggestion is creating accounts should be done by Sales Admins and not by Sales Reps. They are not discipline enough to search for exsiting accounts or are not patient enough to try other searches. use Case tool to submit request to create an Account and stop providing access to Sales rep to create account themselves. I know SFDC is able to customise to their different customers and they should look more into this and give more optios to their customers.
jsmengel Jan 16	We removed the delete button from the page layout based on Account record type - Which will then allow them to still perform a merge but not perform a straight delete. However, I tested the abitlity of a user to merge an account record type that they cannot create or delete into a type they can create as a master and it allows them to do so which then deletes the record type they should not have been able to Delete. It would be helpful to limit merge access based on record type access to give you a bit more control. One problem still exists - they still can delete an account from a view!
ABSI Mar 19	Merged Idea originally posted Mar 19 Profile rights : Merge Account/Contact checkbox independently of Delete rights Lots of Companies would like to disable the DELETE rights on Account and/or Contacts. But it should be usefull to allow "Merge" even if DELETE is not allowed.
Gabe May 12	We would like to see a way for a NON-ADMIN user to merge accounts without necessarily owning the accounts. This would be a big help for helping to keep our data clean.
mwitherspo001 Jun 17	The solution offered in help and training is nice, but requires plenty of admin work. It implies that system admins must have their own page layout with the delete button on it. We've implemented this for clients and it's a bit cloodgey. A merge accounts permission on user profiles would be a better solution.
mg_cool Jun 29	Changed status to Large Enterprise Idea.
initsysadmin Jul 11	Gabe, I have the same problem. My Marketing deparment would like to take ownership of cleaning the data but cannot delete or merge records that they do not own.
caseyryback Aug 22	Hard to believe this hasn't made it to release. There are dozens of reason not to delete contacts and few good reasons. Even bad data is good data. Sales people tend to delete without care to "clean up" their data. This results in dumping valuable contacts which tell us who not to call again or who might want a product we'll sell in the future. Additionally, the security risk of an easy view delete button is very high. On leaving the company for another job, they can too easily wipe out a bunch of great contacts and farm them at the next job. Because we can't bear this corp risk, our contact database grows duplicates everyday since merge and delete are linked.
regman Oct 28	With a direct API integration to our customer db, dupicate records happen. So disabling the merge feature would create more work for an Admin and/or dirty data. But the only way to leave this feature on is to enable "Modify All Data". This one attribute on the Profile contains WAY TOO MUCH control. Please consider splitting the Merge function (and other functionality) out of the Modify All Data attribute. And split the Merge from the Delete functions... that is a good idea too.

track comments for this idea

Please log in to post a comment

last 100 promotions:

laurabeth
regman
ATT
msofia
miluscher
mthomas1980
bradcurrier
blewis
sausalitoadmin
happygirl
initsysadmin
dhubbard
alliforce
mwitherspo001
robertcrav
craskulinecz
Gabe
paddyslacker
rsunderland_gtsi
dtilton
cgeraci
ncurham
ABSI
ftdeby
jddc
francina
sdunham
Letty
echampine
anthonyz
mary.annjoy
jsmengel
marketforce
salessupportasr
justmy2cents
cpayne
Faun
lkh
cbrown58
cdeb
Bas
sea_admin
tdarwm
jdev
smichael@algorithmics.com
ShannonJohnson
JohanLiljegren
JenCalvert
LarryT
JoAnnCulbertson
wshortt
GoSeattleMariners
LisaBailey
fritz_brusch
SueHall
RK
Kringo
barbs
ta_invisible
manu
Smarks
ldm
Kevin_Wee
Franchise35
thephoenix
sshar
brightideas
Suz
jtasaki1
cerijones
carolina.santamaria@idealistas.org
02/21/2007_7:58
ejw
dropsy
lucschweitzer
juanwang
wireless009
onecoldcanadian
BWMoon
TDP314
Teixeira
reederd
mda_tera
kprice@sunlandgroup.com.au
beckas
davewallis
sfer
mar10br0
Amu
rpr2
Kimby
Cappuccino
bcoe
steve.lee
rak8k
LizJordan
SAlvarez
jross
jessica_walas
MMayo

Resources

Successforce.com

Permissions To Merge Without Permissions To Delete - Salesforce IdeaExchange

Salesforce IdeaExchange

Permissions To Merge Without Permissions To Delete

Search Community

Categories

1-800-NO-SOFTWARE | Privacy Statement | Security Statement