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
Displaying Field Values and Page Layouts According to Profiles
Putting It All Together
Try It Out: Create More Users
Try It Out: Verify that Everything Works
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: Verify that Everything Works

Now that we've got data assigned to actual users, let's go through our Recruiting app and see how the security and sharing permissions that we defined in this chapter play out:

  1. First log in as Mario Ruiz—verify that he can see and edit all positions, all candidates, and all job applications. Verify that the New buttons are there for all objects in the Recruiting app. Verify that he can create positions using either position record type.
  2. Log in as Melissa Lee—verify that she can view positions but that there's no New button. Verify that she can't see any candidates, job applications, reviews, or employment websites.
  3. Log in as Ben Stuart—verify that he can view positions and that there's a New button. Verify that he can view but not edit employment websites. Verify that he can't see any candidates. Verify that he can view job applications, but not edit their lookup fields. Verify that he can view reviews and that there's a New button. (What do reviews look like? Can he see the names of the candidates and job applications on them?)
  4. Log in again as Mario Ruiz—have him manually share read/write access on the DBA position with Ben. Have him manually share read access on the candidate with Melissa and Ben. Have him manually share read/write access on the job application with Melissa and Ben.
  5. Log in again as Melissa Lee—verify that she can now see the candidate and job application that Mario just shared with her but that she can't see the candidate's social security number. Have her create a review for that candidate.
  6. Log in again as Ben Stuart—verify that he can edit the DBA position. Verify that he can read and update Melissa's review. Verify that he can update the job application Status to Extend an Offer.

How did we do? If all of these use cases worked correctly, you've just successfully set up security and sharing for our Recruiting app! If a use case didn’t work, check the role, profile, permission set, and sharing rules of each user against the information in the Summary of Required Permissions: Recruiter and Standard Employee Profiles table.

There is one critical security-related issue that we have yet to address: who will be responsible for overseeing the operation of the Recruiting app and its related data when the app goes live?