function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Raghavendra ARaghavendra A 

Edit All and Restrict Delete Help

Hi All,

We have a requirement where a User should have access to all Contacts. He must be able to edit all Records, even the the record owned by others but should not be able to delete any Contact in system. This should be the same for all other custom objects.

How can we set this up? Any help would be highly appreciated.

Thanks,
Raghu
 
Sai Ram ASai Ram A
Hi Raghu

What is the OWD Setting of the Object?
If it is Public Read/Write then go to Profile and provide Create, Read, Edit & View All permission to the Object

If it is public then you have to write the Sharing rules to provide access
https://help.salesforce.com/htviewhelpdoc?err=1&id=security_sharing_rules_map.htm&siteLang=en_US (https://help.salesforce.com/htviewhelpdoc?err=1&id=security_sharing_rules_map.htm&siteLang=en_US)

Hope this Helps

Thanks
BLearn
SonamSonam (Salesforce Developers) 
You can keep the ORG wide security setting default for Contact as Public read write, however, you can remove the delete access from the user's profile such that he say see and edit all records but cannot delete any.

 
ndrannapareddyndrannapareddy
Change OWD settings and then assign permission set for the user giving view all rights if you wanted to give for individual user.
Else give that permissions to profile if you want to give same rights to all users with that profile.



 
Raghavendra ARaghavendra A
Hi All, 

Thanks for your reply. The method you all suggested works for Custom objects. But it is not working for Contact object. Is there anything am missing here?

Thanks,
Raghu
SonamSonam (Salesforce Developers) 
Raghavendra, the method should work for all object irrespective of it being the contact object - could you please share a screenshot of how you have setup the Org wide defaults for the objects to better understand your ORG config.