Record Level Security in Salesforce

After you've finished configuring access rights at the object and field levels, you can go on to configuring access permissions for individual records. You can provide users with access to some records of an object but not to others using record level security. A person or a queue is the owner of each record. The record's owner has complete control over it. If the organization has a role hierarchy set up, people higher in the hierarchy always have the same access as users lower in the hierarchy. This access is granted to records held by individuals as well as records shared with them. 

To carefully regulate data access, you may provide certain users access to specific fields in a single object while restricting the individual records they can see.   

It's simple to change a profile or permission set in Salesforce Org using roles. The user's objects, as well as field level access authorization, are controlled by the profile or permission set. Through role hierarchy and sharing rules, the roles essentially manage the user's record-level security. 

Don't forget to check out: Maintaining Org Security with the Salesforce Health Check

How Many Different Methods are There to Share? 

• Organization-Wide Default. 
• Role Hierarchy. 
• Sharing Rules. 
• Manual Sharing. 

Organization-Wide Default

The default degree of access for all records of an item is determined by the Organization-Wide default or Organization-Wide sharing settings. Defaults set at the organization level can never provide users more access than they already have based on their object permissions.
Because other record-level security solutions can only allow extra accesses, Organization-Wide defaults should be the most restrictive in terms of record level security.
Organization-Wide defaults can be adjusted to any of the three options below: 

• Public Read/Write: 
• Public Read Only 
• Private 

Role Hierarchy (Grant Access Using Hierarchies)

Managers have access to the same records as their subordinates thanks to role hierarchies. Each degree of data access required by a person or group of users is represented by a position in the hierarchy.

Check out another amazing blog by Shivam here: Formula Fields and Roll-up Summary Fields Usage in Salesforce

Sharing rules

Sharing rules are automatic exceptions to org-wide defaults for specific groups of users, allowing them access to records they don't own or have access to normally.

Sharing Rules are divided into two categories:

• Based on record owner: you may provide access to which user's records to whom, and to what level of access, such as read only or read/write. 
• Based on criterion: You may use the object's properties to establish a criterion, such as Merchandise Stock > 10000 or Opportunity Name includes given text (phone) 

Manual Sharing

Manual sharing allows record owners to provide read and modify permissions to persons who would otherwise be unable to access the data.

• To the record owners, their function hierarchy managers, and administrators. 
• In organization-wide defaults, for objects designated as public read-only or private.