Now that we've gone through the required permissions for each of
our four users, let's organize our thoughts by summarizing them in
the following table. In the rest of this chapter, we'll figure out
how we can use the platform to implement these rules in our Recruiting
app.
Table 1. Summary of Required Permissions
| Position |
Read Create Edit |
Read Create Edit* |
Read (No min/max pay) |
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
When implementing the
security and sharing rules for your own organization, it's often useful
to create a required permissions table like this to organize your
thoughts and make sure you don't forget to restrict or grant access
to a particular user. You'll see that we're going to refer back to
this table again and again as we go through this chapter.