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
Vigneshwaran LoganathanVigneshwaran Loganathan 

Hi,

I have a doubt on Permission set and Profile..

which  is applied to Object level and record level.. can you give example for what we can an cannot do in object and record level?

Thanks,
Best Answer chosen by Vigneshwaran Loganathan
sandeep sankhlasandeep sankhla
Hi Vigneshwaran,

Profile is object level, from profile you can give CRUD permission to objects not records...

Sharing setting and other things are applicable to record level..

 but permission sets extend users’ functional access without changing their profiles.
https://help.salesforce.com/apex/HTViewHelpDoc?id=perm_sets_overview.htm

Use permission sets to grant access among logical groupings of users, regardless of their primary job function. For example, let’s say you have an Inventory custom object in your organization. Many users need “Read” access to this object and a smaller number of users need “Edit” access. To address this requirement, you can create a permission set that grants “Read” access and assign it to the appropriate users. You can then create another permission set that gives “Edit” access to the Inventory object and assign it to the smaller group of users.

P.S. If my answer helps you to solve your problem please mark it as best answer. It will help other to find best answer.

Thanks,
Sandeep
Salesforce Certified Developer 


 

All Answers

sandeep sankhlasandeep sankhla
Hi Vigneshwaran,

Profile is object level, from profile you can give CRUD permission to objects not records...

Sharing setting and other things are applicable to record level..

 but permission sets extend users’ functional access without changing their profiles.
https://help.salesforce.com/apex/HTViewHelpDoc?id=perm_sets_overview.htm

Use permission sets to grant access among logical groupings of users, regardless of their primary job function. For example, let’s say you have an Inventory custom object in your organization. Many users need “Read” access to this object and a smaller number of users need “Edit” access. To address this requirement, you can create a permission set that grants “Read” access and assign it to the appropriate users. You can then create another permission set that gives “Edit” access to the Inventory object and assign it to the smaller group of users.

P.S. If my answer helps you to solve your problem please mark it as best answer. It will help other to find best answer.

Thanks,
Sandeep
Salesforce Certified Developer 


 
This was selected as the best answer
bob_buzzardbob_buzzard
Permission set and profile both define permissions on a per-object basis. So they can be used to give read or update access to a specific sobject type such as Opportunity.  If you want to control access to individual records, you need to use the available sharing configuration, such as org-wide defaults, or ownership/criteria based sharing rules.
MithunPMithunP
Hi Vigneshwaran,

Permission set and Profile, both are for object level and field level accessability. The idea behind permission set is to reduce number of Profiles in the org. Example is if there are two users with same Profile and you created a new custom object, now you need to provide different permissions for these two users on this new custom object. In this case we need to create different permission sets and assign to these two users without creating multiple Profiles. Roles is for data level accessibility.

Best Regards,
Mithun.