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
Introducing Field-Level Security
Field-Level Security in Our Recruiting App
Try It Out: Limit Access to Fields in the Standard Employee Profile
Try It Out: Check Field-Level Security in Permission Sets
Controlling Access to Records
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

Field-Level Security in Our Recruiting App

Just to refresh our memories about what field-level security settings we need for our Recruiting app, let’s take another look at our required permissions in the following table. We’ll keep them organized by recruiter, hiring manager, and standard employee, because it turns out that (surprise!) field-level security settings are closely related to profiles and permission sets:

Table 1. Revised Summary of Required Permissions
Recruiter Hiring Manager Standard Employee
Position Read Create Edit Read Create Edit* Read (No min/max pay)
Candidate Read Create Edit Read* (No SSN) Read* (No SSN)
Job Application Read Create Edit Read Edit (No lookup fields) Read*
Review Read Create Edit Read Create Edit Read** Create Edit**
Job Posting Read Create Edit Delete Read*Create*Edit*
Employment Website Read Create Edit Delete Read

* Only for those records that are associated with a position to which the hiring manager/interviewer has been assigned

** Only for those records that the interviewer owns

For field-level security settings, we’ll first zero in on those rules that include field restrictions in parentheses, specifically:
  • On the Position object, hide minimum and maximum pay from standard employees and interviewers
  • On the Candidate object, hide social security numbers from hiring managers and interviewers
  • On the Job Application object, make the Position and Candidate lookup fields read-only for hiring managers

So let’s get down to it!