What is Sharing Rule in Salesforce?

Hello Satykam,

Salesforce sharing rules are put into force when records and other data requires to be shared among the employees or multiple users in an organization. Sharing the records using Salesforce therefore becomes the option to be used by the organization. However, sharing of this data can be risky especially when it involves sharing of sensitive data. This creates necessity for regulations to monitor the sharing process as well as monitor the recipients of the data.

There are two types of methods for sharing:

1. Manual Sharing

2. Automatic Sharing

For more details about Sharing rule go to this link:-

http://rainforce.walkme.com/salesforce-sharing-rules-overview

https://developer.salesforce.com/docs/atlas.en-us.workbook_security.meta/workbook_security/record_level_access_3.htm

Hi Satyakam,

Sharing rules can be based on who owns the record or on the values of fields in the record. For example, use sharing rules to extend sharing access to users in public groups or roles. As with role hierarchies, sharing rules can never be stricter than your org-wide default settings. They just allow greater access for particular users.

Each sharing rule has three components.Share which records?
You can share records owned by certain users or meeting certain criteria. Criteria-based sharing rules determine what records to share based on field values other than ownership.
With which users?
You can define groups of users by role or by defining a public group. A public group is an admin-defined grouping of users that can be used to simplify the creation of sharing rules. Each public group can be a combination of:individual users
roles
roles and subordinates
other public groups
What kind of access?
You can assign either Read-Only or Read/Write access.
Sharing rules work best when they're defined for a particular group of users that you can determine or predict in advance, rather than a set of users that frequently changes. For example, in the Recruiting app, it’s important to share every position, candidate, job application, and review with every recruiter. Since recruiters all belong to either the Recruiting Manager or Recruiter roles in the role hierarchy, we can easily use a sharing rule to share those objects with the Recruiting Manager role and its subordinates.

Alternatively, consider another use case from the Recruiting app: interviewers need read access on the candidates and job applications for people they're interviewing. In this case, the set of interviewers is a lot harder to predict in advance—hiring managers might use different sets of interviewers depending on the position for which they're hiring, and the interviewers might come from different groups in the role hierarchy. So, this use case probably shouldn't be handled with sharing rules—the team of interviewers for any given manager is just too hard to predict.
Thanks

Hello,

If we have to hide records from one person, one user in the organization,  in a private model.  We have to lock everything down to hide records from somebody and then use things like sharing rules to grant access back to the rest of the organization.  So, if we have to put one person in the penalty box and make sure they can’t see their neighbors stuff, whatever that object might be, and then use sharing rules to grant access back.

Thanks.