Skip to main content

Grow your business with Salesforce Starter

Deepen customer relationships with sales, service, and marketing in one app.

Start your free 30-day trial
Time Estimate

Define Sharing Rules

Learning Objectives

After completing this unit, you'll be able to:

  • Use sharing rules to extend access beyond the role hierarchy structure.
  • Create a public group that includes users with different profiles and roles.

Extend Access with Sharing Rules

Your org-wide default sharing settings give you a (relatively restrictive) baseline level of access for each object. If you have org-wide sharing defaults of Public Read Only or Private, you can open access back up for some users with sharing rules. This enables you to make automatic exceptions to your org-wide sharing settings for selected sets of users.

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, by territory, 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. Depending on the group member types available in your org, public groups can be a combination of:

  • individual users
  • roles
  • roles and subordinates (you can choose whether to include Experience Cloud site and portal users or only internal users)
  • territories
  • territories 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.

Should we use a sharing rule?

Let's go through the set of required permissions we still want to implement and pick out the ones that work best with sharing rules.

Recruiters need read and update access on every position, candidate, job application, and review record that exists in the app.

Yes. As we discussed previously, it's easy to pick out the group of recruiters in our role hierarchy.

Hiring managers need read and update access on position and job posting records on which they're the hiring manager.

No. It's too hard to predict which positions will be assigned to which hiring manager. We'll need to handle this use case some other way, such as sharing each job posting record via a manual sharing rule.

Hiring managers need read access on candidate records on which they're the hiring manager.

No. Again, it's too hard to predict which positions will be assigned to which hiring manager.

Hiring managers need read and update access on every job application and review record.

Yes. Since we're not restricting which job applications and reviews a hiring manager gets to read and update, we can easily pick out all of the hiring managers from our role hierarchy and define a sharing rule for them.

Interviewers need read access on the candidate and job application records for people they're interviewing.

No. As we discussed previously, it's hard to predict who will be a member of an interview team for a particular position.

To summarize, here are the key sharing rules we define for the Recruiting app.


Rule Label

Owned by...

Share with...

Access Level


Edit Reviews

Entire Organization

Recruiters and Hiring Managers



Edit Candidates

Entire Organization

The role and subordinates of the Recruiting Manager



Edit Positions

The role and subordinates of the Recruiting Manager

The role and subordinates of the Recruiting Manager


In the rest of this unit, you'll learn how to create public groups and sharing rules to implement these permissions.

Define a Public Group

Before creating a sharing rule, it’s important to set up the appropriate public group. A public group is a collection of individual users, other groups, individual roles or territories, and/or roles or territories with their subordinates that all have a function in common. For example, users with the Recruiter profile as well as users in the SW Dev Manager role both review job applications. 

Using a public group when defining a sharing rule makes the rule easier to create and, more importantly, easier to understand later, especially if it's one of many sharing rules that you're trying to maintain in a large organization. Create a public group if you want to define a sharing rule that encompasses more than one or two groups or roles, or any individual.

  1. From Setup, in the Quick Find, enter Public Groups, and then select Public Groups.
  2. Click New
  3. Give your group a label. The Group Name text box populates automatically when you click it. This is the unique name used by the API and managed packages.
  4. In the Search drop-down list, choose from which individual users, other groups, or roles you’ll select users, and whether their subordinates are included. You can include a combination of member types in your public groups.
  5. In the Available Members list, select users, then click Add.
  6. Click Save.

Once you’ve defined your group, you can use it to define sharing rules.

Public Groups for the Recruiting App

Looking at the required permissions that we want to implement for our Recruiting app, there are just two objects that need a public group for their sharing rules: Job Application and Review. The good news is that we can cover these objects in a single group because the Review object is on the detail side of a master-detail relationship, so it inherits the sharing settings we apply to the Job Application object. 

Since both recruiters and hiring managers need read and update access to job applications and reviews, we can define a public group called Reviewers that includes both recruiters and hiring managers. In this group, we add the SW Dev Manager, Director Product Management, and Director QA roles, and the role and subordinates of the Recruiting Manager.

Define a Sharing Rule

You can define a sharing rule for a single public group, role, or territory. You can also define a sharing rule for a role plus its subordinates or for a territory plus its subordinates.

  1. From Setup, in the Quick Find box, enter Sharing Settings, and then select Sharing Settings. This is the same page used to define org-wide defaults.
  2. In the Manage sharing settings for drop-down list, choose the object for which to create the sharing rule. Choosing an object in this drop-down list allows you to focus in on the org-wide defaults and sharing rules for a single object at a time rather than looking at all of them in a long page—a useful thing if you've got a large org with multiple custom objects.
  3. In the Sharing Rules area, click New and give your rule a label. The Rule Name text box populates automatically when you click it.
  4. For the rule type, you can choose whether the sharing rule is based on the owner or based on criteria that records must match to be included. For this sharing rule, select Based on record owner.
  5. For Select which records to be shared, select a category from the first dropdown list, and a set of users from the second dropdown list or lookup field.
  6. For Select users to share with, specify the users who get access to the data.
  7. Select a sharing access setting.
  8. Click Save.

Sharing Rules for the Recruiting App

For the Recruiting app, we need a rule that shares reviews written and owned by any member of the org with all recruiters and hiring managers. We’ll create a sharing rule that applies to both the Job Application and the Review objects.

We create a Job Application owner-based sharing rule with the label Review Records. For Select which records to be shared, select Public Groups, then choose All Internal Users. We specify that these records are shared with the Reviewers public group that we created, and set the level of access to Read/Write.

Since reviewers and hiring managers all need to read and update reviews, we handled everyone with a single sharing rule and a public group.


Keep learning for
Sign up for an account to continue.
What’s in it for you?
  • Get personalized recommendations for your career goals
  • Practice your skills with hands-on challenges and quizzes
  • Track and share your progress with employers
  • Connect to mentorship and career opportunities