Force.com Platform Fundamentals

Preface
Introducing the Force.com Platform
About the Sample Recruiting App
Reviewing Database Concepts
Building a Simple App
Enhancing the Simple App with Advanced Fields, Data Validation, and Page Layouts
Expanding the Simple App Using Relationships
Securing and Sharing Data
Controlling Access to Data in Our App
Data Access Concepts
Controlling Access to Objects
Controlling Access to Fields
Controlling Access to Records
Introducing Organization-Wide Defaults
Org-Wide Defaults in Our Recruiting App
Try It Out: Set Org-Wide Defaults
Introducing Role Hierarchies
Comparing Roles, Profiles, and Permission Sets
Role Hierarchies in Our Recruiting App
Try It Out: Create a User
Try It Out: Define a Role Hierarchy
What's Left to be Shared?
Introducing Sharing Rules
Sharing Rules in Our Recruiting App
Try It Out: Define a Public Group
Try It Out: Define Sharing Rules
Introducing Manual Sharing
Try It Out: Define a Manual Sharing Rule
Displaying Field Values and Page Layouts According to Profiles
Putting It All Together
Delegating Data Administration
Summing Up
Collaborating with Chatter
Automating Business Processes
Analyzing Data with Reports and Dashboards
Moving Beyond Point-and-Click App Development
Learning More
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Try It Out: Define a Manual Sharing Rule

Let's pretend that we're a recruiter like Mario and we need to share a particular candidate record that we own with another role, group, or user:

  1. On the detail page for the candidate, click Sharing.
Sharing Detail Page The Sharing Detail page for the CA-00002 object

Since we own this candidate record, we get to see details about who else can see the record and why. If we didn't own this record, there would be a message about not having sufficient privileges.

If we wanted to view the names of each user who has access to the record rather than just the names of the roles and public groups, we could click Expand List in this page. Although the operation can take some time depending on the number of users in our organization, it's helpful to determine whether we need to define a manual sharing rule for a particular user or if he or she already has access.

Tip

  1. Click Add.
  2. In the Search drop-down list, choose whether we want to manually share the record with a user, public group, role, or role and subordinates.
  3. In the Available list, select the user, public group, or role that should have access to the record, and click Add.
  4. In the Access Level drop-down list, specify whether the user, public group, or role should have read or read/write access to the record.
  5. Click Save.

Not too hard! When we roll out our Recruiting app to users, we'll have to train our recruiters to take these steps for the position, candidate, and job application records that their hiring managers and interviewers need to access. Once this training is complete, we will have implemented all of the required sharing and security settings that we discussed at the beginning of the chapter—well done!

Make sure you are logged in as the candidate record owner, Mario Ruiz, to share the candidate via the Sharing button. You might not see the button if you’re not logged in as the candidate record owner or system administrator. The button is available when your organization-wide default for candidates is set to Private or Public Read Only.

Note