Salesforce is Point & Click

Profiles define how users access objects and data, and what they can do within the application. When you create users, you assign a profile to each one. Reference: Salesforce   And my recommendation is that, before you start and create a Profile for each Role in the Role Hierarchy , you should read carefully what a Permission Set is, how it defines too how users access objects,  and get a good understanding of what is the difference between a Profile and a Permission Set . Check the table at the end of this post The Fall of the Profile Empire  to see what you can do only with profiles. The Profile Minimum Access - Salesforce  proposed approach I will use the example Hiring Application proposed in the Data Security Trailhead Module to develop the approach. Regarding data security, the module deals with permissions at 4 levels: Org, Object, Field, and Record. But I will work with only two levels: Object and Field. The required permissions are: ...

Salesforce is on the path to removing or reducing the need for Profiles. They are almost there ... Since 1999 the Profile has been the king when settings and permissions are needed. In 2011, the Permission Set was introduced with strong recommendations as a good practice and in the hope that it would help reduce the huge number of profiles per org. In 2019, Permission Set Groups were introduced, not only to group Permission Sets but to relate to functional roles (what was a proposed idea with Permission Sets, is now a point & click configuration). In 2020, the Minimum Access - Salesforce profile was introduced ( Summer'20 ), and in less ...