Try It Out: Create More Users

To really put our Recruiting app through its paces, we'll first need to define the rest of our users and assign a couple of them to some of the recruiting records that we imported earlier.

If you're implementing the Recruiting app in a Developer Edition organization, you'll have only a few additional users to play with besides the System Administrator user. You can still try out all of the use cases that we describe here, but you'll have to update the user's profile, permission sets, and role for whatever use case you're working on.

Note

Table 1. Summary of Required Permissions: Recruiter and Standard Employee Profiles
	Recruiter	Standard Employee
Position	Read Create Edit	Read (No min/max pay)
Candidate	Read Create Edit
Job Application	Read Create Edit
Review	Read Create Edit
Job Posting	Read Create Edit Delete
Employment Website	Read Create Edit Delete

Let's walk through the creation of our recruiter: Mario Ruiz. Then you can finish the other users on your own.

From Setup, enter Users in the Quick Find box, then select Users.
Click New User.
Fill out the required fields in the User edit page.

Just as you did with Cynthia Capobianco, in the Email field enter a real email address that you have access to, and in the Username field enter a “fake” email address (for example, mario.ruiz@recruiting.com).

From the Profile drop-down list, select Recruiter.
Click Save.

Now that we've created the Mario Ruiz user, let's give him ownership of the DBA position and its associated job application and candidate records.

Click the Positions tab.
From the View drop-down list, select All and click Go.

If you want to see more than just the Position Title field in this view, click Edit next to the View drop-down list and add additional fields in the Select Fields to Display section.

Tip

Click DBA.
Next to the Owner field, click Change.
Click the lookup icon and choose Mario Ruiz.
Click Save.
In the Job Applications related list, click the name of the listed job application and repeat Steps 8-11.
Click the ID of the associated candidate on the Job Application detail page and repeat Steps 8-11.

When you imported records from Candidate, Job Application, and Position CSV files, you were probably logged in as a user other than a Recruiting Manager or subordinate. We created sharing rules that share the records that are owned by the role and subordinates of the Recruiting Manager, so now you should transfer ownership of the rest of these records to a Recruiting Manager or subordinate (Phil Katz or Mario Ruiz).

Note

Now create the other users in Summary of User Profile Assignments and assign them the profiles listed in the table. Since Mario is our only recruiter, he’s the only user we’ll assign the Recruiter profile to. Everyone else should have the Standard Employee profile.

Table 2. Summary of User Profile Assignments
User	Profile
Phil Katz	Standard Employee
Megan Smith	Standard Employee
Craig Kingman	Standard Employee
Tom Zales	Standard Employee
Melissa Lee	Standard Employee
Ben Stuart	Standard Employee
Andy Macrola	Standard Employee
Amy Lojack	Standard Employee
Frank Linstrom	Standard Employee
Andrew Goldberg	Standard Employee
Harry Potterham	Standard Employee
Flash Stevenson	Standard Employee
Clark Kentman	Standard Employee
Cynthia Capobianco	Standard Employee

Notice that most of our users have the same profile. With the Standard Employee profile, the only thing these users can do in our recruiting app is look at positions (not including certain fields). But what about the users who need to access more information, such as hiring manager Ben Stuart? Well, this is where our permission sets come in, which we created in Introducing Permission Sets. Here’s a recap of the permissions we gave the Hiring Manager and Interviewer permission sets.

Table 3. Summary of Required Permissions: Hiring Manager and Interviewer Permission Sets
	Hiring Manager	Interviewer
Position	Read Create Edit*	Read (No min/max pay)
Candidate	Read* (No SSN)	Read * (No SSN)
Job Application	Read Edit (No lookup fields)	Read *
Review	Read Create Edit	Read Create Edit
Job Posting	Read Create Edit *
Employment Website	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

Since Ben is a hiring manager for software development, he needs to be able to do things like creating new positions or looking at a candidate and her application. Let’s assign the Hiring Manager permission set to Ben so he can accomplish those tasks.

From Setup, enter Users in the Quick Find box, then select Users.
Click Ben Stuart’s name.
In the user detail page, scroll to the Permission Set Assignments related list and click Edit Assignments.
In the Available Permission Sets box, select Hiring Manager and use the arrows to move it to the Enabled Permission Sets box.
Click Save.

Repeat these steps for the other hiring managers: Andy Macrola, Amy Lojack, and Clark Kentman.

Now that we’ve assigned all of our hiring managers the right permission set, let’s focus on our interviewers. Mario has scheduled a candidate for an interview next week, and Ben has asked two of his developers to interview the candidate. Assign the Interviewer permission set to Melissa Lee and Craig Kingman, so that they can check out the position and application, as well as leave their reviews of the interview.

Beyond the Basics

Did you know you can control who sees whom in the organization?

Say you want to let recruiters, hiring managers, and interviewers see and collaborate with each other, but not with standard employees. You can set the organization-wide default for the user object to Private, and create sharing rules to enable recruiters, hiring managers, and interviewers to see and collaborate with each other in the Recruiting App, while preventing standard employees from viewing those users and vice versa.

To find out more, see “User Sharing” in the Salesforce Help.

Force.com Platform Fundamentals

Try It Out: Create More Users

Beyond the Basics