Force.com Platform Fundamentals

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
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!