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
Introducing Profiles
Standard Profiles
Introducing Permission Sets
Profiles and Permission Sets in Our Recruiting App
Try It Out: Create the Recruiter Profile
Try It Out: Create the Standard Employee Profile
Try It Out: Create the Hiring Manager Permission Set
Try It Out: Create the Interviewer Permission Set
Controlling Access to Fields
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
Using Custom Workflow and Approval 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: Create the Interviewer Permission Set

Now we’re ready to create the Interviewer permission set.

Using the steps that we discussed in the last section, create a permission set with the following settings:

  • Name this permission set Interviewer and assign the Salesforce user license.
  • Under Assigned Apps, make the Recruiting app visible.
  • Enable the following tab settings and object permissions:
    Table 1. Tab Settings and Object Permissions for Interviewers
    Object Name Tab Settings Object Permissions Field Permissions
    Positions
    • Available
    • Visible
    • Read
    • No access on Min Pay and Max Pay
    • Read on all others
    Candidates
    • Available
    • Visible
    • Read
    • No access on SSN
    • Read on all others
    Job Applications
    • Available
    • Visible
    • Read
    • Read on all
    Reviews -
    • Read
    • Create
    • Edit
    • Read on Candidate and Position
    • Read and Edit on Assessment
Let’s review the required permissions for hiring managers, interviewers, and standard employees.
Table 2. Summary of Required Permissions: Hiring Manager, Interviewer, and Standard Employee
Positions Candidates Job Applications Reviews Job Postings Employment Websites
Hiring Manager
  • Read
  • Create
  • Edit*
  • Read* (No SSN)
  • Read
  • Edit (No lookup fields)
  • Read
  • Create
  • Edit
  • Read*
  • Create*
  • Edit*
  • Read
Interviewer
  • Read (No min/max pay)
  • Read* (No SSN)
  • Read*
  • Read**
  • Create
  • Edit**
 - -
Standard Employee
  • Read (No min/max pay)
 - - - - -

* 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

Great, but what about those asterisks? Do we need to take those into account when we set our object permissions?

Not at all. Those asterisks represent record-level security settings that we're going to specify shortly. The only things we need to care about here are the permissions that these users will need to have access to at least some of the time—that's the whole point of object permissions.

However, we do need to make sure that sensitive data on these objects is protected from users who don't need access, and then we need to drill down on the actual records that each user should be allowed to view and edit.