How can we help you?

CareerBuilder Employment Screening

CareerBuilder Employment Screening (CBES) provides background screening, drug testing, I-9 and occupational health services to help employers gain confidence in matching the right candidate to the right position at the right time.

Greenhouse Recruiting’s integration with CBES allows your organization to add a CBES background check to a job's interview pipeline. In this article, we will cover how to:

 

Configure User Setup Permissions in Greenhouse Recruiting

In order to enable the Greenhouse/CBES integration, you will need the developer permissions:

  • Can manage ALL organization’s API Credentials
  • Can manage and configure web hooks

Contact a Greenhouse user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions to apply the API credential management permission to your account. Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon configure.png > Users > Your Name.

1.png

The user with Site Admin level permissions should navigate to the Permissions panel on your user page and expand the Developer Permissions dropdown menu.

Select Can manage ALL organization’s API Credentials and Can manage and configure web hooks so that a check is in the checkboxes. When finished, click Save.

Screen_Shot_2019-05-16_at_10.59.48_AM.png

 

Create a Harvest API Key for the Greenhouse/CBES Integration

To create a Harvest API key for the integration, click on the Configure icon configure.png in the upper right-hand corner. Navigate to Dev Center on the left-hand panel.

From the Dev Center page, click API Credential Management.

3.png

From the API Credential Management page, click Create New API Key to generate the API key for CBES.

4.png

From the Create new credential dialog box, name your API key CBES and select Harvest from the Type dropdown menu. When finished, click Create.

Screen_Shot_2019-05-16_at_11.13.14_AM.png

On the Manage API Key Permissions page, expand the Candidate section and select POST: Add Note.

When finished, click Update.

Your Harvest API key for the Greenhouse/CBES integration is created and configured. Provide your Harvest API key to your CBES Account Manager so they can set up the integration.

 

Create Web Hook for Greenhouse/CBES

Click the Configure icon configure.png in the upper right-hand corner and navigate to Dev Center on the left-hand panel.

2.png

From the Dev Center page, click Web Hooks. Click Web Hooks from the subsequent page.

4.png

You will be directed to a new page where you Create a New Web Hook. From this page provide the following details:

When finished, click Create Web hook.

Screen_Shot_2019-05-16_at_11.32.04_AM.png

 

Configure Candidate Custom Field

Note: Candidate custom fields can only be configured by either users with the Site Admin permission level, or Job Admin permission level with the additional user-specific permission to Can manage custom fields

Custom candidate fields are used to store location information, package information and client codes.

Click on the Configure icon configure.png in the upper right-hand corner and navigate to Custom Options on the left-hand panel.

Screen_Shot_2019-01-03_at_3.53.30_PM.png

Click Candidates under Company Custom Fields

Screen_Shot_2019-01-03_at_3.57.29_PM.png

Click + Add Field.

Screen_Shot_2019-01-03_at_4.05.55_PM.png

You will need to create 3 different candidate custom fields:

  • CBES Location
  • CBES Package
  • Client Codes

Once you have finished creating one candidate custom field, click + Add Field to create the subsequent custom fields:

  CBES Location CBES Package Client Codes
Field CBES Location CBES Package Client code
Description Location in WebACE Package in WebACE optional
Type Single select Single select Single select
Options

LocationID|Location Name

(e.g. 12345|Aurico Package Name)

*input each option on a separate line

PackageID|Package Name

(e.g. 12345|Aurico Package Name)

*input each option on a separate line

Field MUST be labeled: “Client Code”. Subsequent client codes MUST be labeled “Client Code2”, “Client Code3”, etc. (There is space between “Client” and “Code”, but there is no space between “Code” and the number after it.)
Create New Email Token unchecked unchecked unchecked
Mark Private unchecked unchecked unchecked 

 

Place Order

To place a CBES order, navigate to the candidate's profile and click the Details tab. Confirm the following information is complete:

  • Candidate Email Address
  • CBES Location
  • CBES Package
  • Client Code(s) (Optional; Max of 4)
  • Recruiter
    • Note: If the recruiter email address is not a valid user in the CBES Platform the order will fail

Next, click the On Job tab and navigate to Offer Details on the left-hand side.

Click Mark Candidate as Hired.

Fill in the necessary fields from the Offer Accepted dialog box. Click Save.

 

Statuses will post back to the candidate’s Activity Feed tab.

The status will say SUCCESS when CBES first receives the order from Greenhouse. 

  

For more information on the configuration, packages and locations contact your CBES Account Manager.

The following set of slides displays the candidate’s user experience on the WebACE® Platform.

  • Once the invitation email has been received, the candidate clicks the link, which redirects to CBES’s “Candidate” Interface
  • The candidate logs into WebACE® by using the credentials provided via email

These images display the candidate’s user experience on the WebACE® Platform.

“In Progress” & “Complete” Statuses with Result URLs

  • Subsequent statuses will update into the candidate’s Activity Feed tab as the order progresses through WebACE®.
  • In Progress” will post when the invitation is completed by the candidate and the order is being worked on in WebACE®. This is accompanied by a ResultURL to view the order in WebACE as it is being worked on.
  • Complete” will post when the order is completed in WebACE® and is ready to view. This status will be accompanied by either a “Clear” or “Review” adjudication with a ResultURL to view the completed order results.