Profile
RoleProvides user with the ability to perform actions on a recordProvides user with visibility access to the recordMandatory for a User as it defines the most basic access
Non Mandatory for a user
A Profile Provides a user with the CRUD(Create, Read, Update,Delete) permission in order for the user to have access to records and its more like a template feature that can be provided to a group of users.So, one profile can be used to provide similar access to a group of users with same set of functions.
Permission set which are the additional set of access rights provided to a user can be more specific and can be assigned on an individual rep’s need.
for example a profile can be created for a group of Sales Rep’s with a common set of functions and a permission set can be used to provide additional set of edit, or tab visibility settings to individual Sales rep based on their day to day needs.
Both Profile and Permission set eat up License in the Org while a Role creation doesn’t require License to be mapped with it.
Role is mainly based on the Organisation’s hierarchy and usually setup to mimic a similar structue in salesforce. To setup Roles one has to have two things in place
Organisation Wide Default (OWD)- is the default record access provided for each Object (in salesforce Objects are nothing but tables). There are following values for objects in OWD
Private – Only the user which has created a record can view that record
Public Read Only – Visible to all
All user’s with Higher role can view records of user’s with a role directly lower to them through “Grant Access Using Hierarchies“.
Comments