Try It Out: Check Field-Level Security in Permission Sets

But what about the permission sets we created?

Remember how we specified field permissions when we created the Hiring Manager and Interview permission sets? Now that we know more about field-level security, let’s double-check the most sensitive fields in our permission sets to make sure they are correct.

If any of these settings are incorrect, go ahead and edit them. Be sure to click Save each time you go to a different page. First, let’s check field permissions in the Interviewer permission set.

1. From Setup, click Manage Users | Permission Sets, and select the Interviewer permission set.
2. In the Find Settings... box, type pos, then select Positions.
3. Next to the Max Pay and Min Pay fields, both Read and Edit should be disabled.

Now let’s check the Hiring Manager permission set.

4. Open the Hiring Manager permission set and navigate to the Positions object.
5. Next to the Max Pay and Min Pay fields, both Read and Edit should be enabled.

Finally, we want to make sure hiring managers can see which candidate and position are associated with each job application, but prevent them from changing those lookup fields.

6. In the Find Settings... box, type job, then select Job Applications.
7. Next to the Candidate and Position fields, Read should be enabled and Edit should be disabled.

All done! We've just finished the second piece of our security and sharing puzzle by defining field-level security for the sensitive fields in our Recruiting app. Now, for the final piece of the puzzle, we need to specify the individual records to which each user needs access. We need to protect our data without compromising any employee's ability to perform his or her job.