Account settings

The Account settings page allows admins to manage their Checkr account and individual users to manage their account settings. Use this page to:

• Define email addresses for notifications
• Set notification preferences
• Users
  • Add new users to the account
  • Add and edit user permissions
• View and configure SSO settings
• Add and manage API keys and account webhooks
• Review partner integration settings

Settings

Use the Account settings > Settings tab to edit account settings for your organization and select email notification preferences at the user level.

Define email addresses for notifications

As part of the background check process, Checkr issues multiple email notifications to candidates. If your organization has not enabled work locations for the account, use the Account settings section to define these email addresses.

Enter an address for the following fields:

• Support phone: Enter the phone number that candidates can use to contact you to submit evidence of rehabilitation or other context during the adverse action process.
• Support email: Enter the address for candidates to use to contact you to submit evidence of rehabilitation or other context during the adverse action process.
• Billing email: Enter the address that Checkr will use to contact you about invoices and other billing communications.
• Adverse action email: Enter the address that will send pre- and post-adverse action notices on your behalf to candidates. This address receives the undeliverable notices if an adverse action notice is undeliverable to a candidate, which happens if their email account has expired or the email address on file is inaccurate.
• Technical contact email: If your company uses the Checkr APIs for integration, enter your primary person to contact for technical communications. Checkr uses this email address to contact you about important issues or updates to the Checkr APIs.
• Compliance contact email: Enter the primary person to communicate with Checkr about compliance issues or updates. Checkr uses this email address to send updates to candidate disputes or notifications of changes to background check reports.

Adverse Action fallback

If your adverse action email address is invalid, Checkr will try to notify you using the following sequence of email addresses in the Account settings tab.

1. User email for the account that initiated the adverse action
2. Adverse action email
3. Support email
4. Billing email
5. Technical contact email

If no email address exists at the account level, the email notifying your company that the adverse action email is undeliverable will be sent to the listed email address for all users on the Checkr account with admin permission level or above. 

Set candidate notification preferences

Use the SMS invitations setting to enable SMS invitations to your candidates. These text messages will be sent in addition to the emailed invitation.

Set notification preferences

Use the Notifications section in the Account settings tab to select the content and frequency of your automated email notifications. This section of the page is available to all users of your Checkr account.

The notifications below are available:

• All report updates: Receive an email for any changes to report status.
• Report created: Receive an email each time a new background report is created.
• Report clear: Receive an email when a report completes with a Clear status.
• Report consider: Receive an email when a report completes with a Consider status, indicating that the report has something for you to review.
• Report suspended: Receive an email when a report is suspended, meaning that Checkr contacted the candidate to provide additional information, but the candidate hasn't responded yet.
• Report canceled: Receive an email when a report is canceled, meaning that all screenings in the report were canceled.
• Report disputed: Receive an email when a report is disputed, meaning a candidate has contacted Checkr to contest the report's accuracy. Checkr initiates a re-investigation for these candidates. At least 1 user must be subscribed at all times to receive these notices.
• All candidate updates: Receive an email when a candidate invitation is sent or expires.
• Candidate invitation expired: Receive an email when an invitation has expired because the candidate didn't complete the process within 7 days or the customer-specified period.
• Candidate invitation sent: Receive an email every time an invitation is sent to a candidate.
• All Candidate Stories: Receive an email every time a candidate story is submitted.
• Candidate stories submitted pre/post AA: Receive an email if a candidate story is submitted before an Adverse Action is initiated, or after the Pre-Adverse Action notice has been sent.

Customers with the Assess feature have the additional options below:

• All report assessment updates: Receive an email for all changes to any report assessment.
• Report assessment Eligible: Receive an email when a report assessment changes to Eligible.
• Report assessment Review: Receive an email when a report assessment changes to Review.
• Report assessment Escalated: Receive an email when a report assessment changes to Escalated.
• Report assessments (daily digest): Receive a daily email itemizing all changes to report assessments.

Users

Use the Users tab to view, edit, manage, or delete existing users, or to invite new users to your Checkr account.

Invite new users

To add a user, enter their email address in the Enter email field and click Add user. Checkr sends an invitation to the user to confirm the new account creation and set up a password.

After the invitation is confirmed, add a user role and work location.

Assign roles to users

Click Edit in the Roles column to assign roles to your users and grant them permissions within the Checkr Dashboard.

Individual users can have multiple roles, such as adjudicator and requester.

Available user roles

• Limited user: This user role can access the candidates list but can't access candidate or report details. All new users on an account automatically have this role.
• User: This user role can access reports. Assign this role to staff who provide candidates with updates on their background checks.
• Requester: This user role can access, send, monitor, and cancel invitations to initiate background checks. This role can add a screening to an existing package. Requesters can see the status of reports in the Candidates page but not the results of completed reports. Requesters can also access candidate documents and exceptions but not completed report details. Assign this role to recruiters who initiate background checks.
• Adjudicator: This user role can access candidate and report details. This role can adjudicate reports, engage candidates, and send pre-adverse action notices to candidates. Assign this role to adjudication staff.
• Restricted admin: This user role is available for Account Hierarchy-enabled accounts only. This role has all permissions of adjudicators and requesters for candidates in their Account Hierarchy node. This role can invite users to the account, add screenings, save packages, and assign non-admin user roles. This role can also view invoices and change developer settings. This role can't update billing or settings. Assign this role to administrators for sub-nodes on your account.
• Admin: This user role has full access to all functionality in the Checkr Dashboard. Admins can update account settings (including billing information), add screenings, save packages, and assign all roles to any users in the account. Admins aren't restricted by the nodes assigned to them. Limit this role to core members of your team.

Assign work locations to users

Use geos (work locations) to manage access to candidate information for your team by geographic location.

For example, if your primary hiring locations are New York, Chicago, and Los Angeles, you might want to group both your candidates and your recruiters by location for the different positions. Create work locations that reflect these three cities, then assign them to both the users managing the hiring process and the programs used to issue invitations to prospective candidates.

Click the menu icon at the far right of the user's name, and select Edit geos to manage the locations assigned to a specific user. Then, choose the locations that user will be subscribed to. After users subscribe to a specific location, they can access and manage candidates only in those locations.

Delete users

To delete existing users from your account, click the menu icon at the far right of the user's name and select Delete User. Checkr issues a confirmation and then deletes the user from your account.

Unlock user accounts

Users with too many failed login attempts will be locked out of their accounts. To send a user a password-reset email, click Unlock User from the menu next to their name.

Single Sign On

Use the Checkr Dashboard to view and update your SSO settings. Log into your account as a user with the Checkr admin role. Then, go to Account settings > Single Sign On.

Copy your Checkr info into your IdP SAML config

Paste the listed values into your IdP endpoint setup.

• Strategy: SAML
• Single Sign On URL: Paste in the ACS URL field in your IdP’s SAML config. 
• Audience: Paste in the SP Entity ID field in your IdP’s SAML config. 
• Attributes: `email` Configure your IdP to send the email address for a user as the SAML Subject. (If you are setting up SP-initiated SSO, you must make sure that all emails sent via this attribute match the domain specified on the Checkr Dashboard under Email Domain.) 
• Subject:NameID: Your IdP’s UUID or GUID.

Copy your SAML information into your Checkr setup

Use the following section to enter the required information.

• Sign in URL: The IdP callback endpoint (IdP URL) from your IdP platform’s SAML configuration. (Required for both IdP-initiated and SP-initiated SSO.) 
• Email domain: Enter your email domain. All traffic within Checkr for users with this email domain will be directed to your SSO endpoint. This setting disables Checkr direct login. (Required only for Service Provider initiated SSO.) 

• Important

  Enabling this forces SP-Initiated SSO. Make sure that you’ve tested IdP-initiated SSO and make sure you meet the criteria to enable SP-enabled SSO before enabling!

• Signing certificate: Click Choose File to upload a signing certificate from your SAML provider to your Checkr account. Your IdP will use this public certificate to sign the assertion. (Your IdP Public Key (IdP Certificate) from your IdP platform’s SAML configuration.)

Developer settings

The Developer settings page provides access to your account’s API keys and webhooks. API keys are used to enable API access to the Checkr service for customized interfaces. Webhooks provide account-level webhooks to which any Checkr-generated events will be posted.

API and webhook logs appear in the Logs section of the Checkr Dashboard.

For more information about webhooks, refer to the Checkr API Guide. 

API Keys

The API Keys pane lists all active API keys for the account:

• Click Show key to see the selected key in plain text.
• Click Expire key to set an expiration date for the selected key.
• Click Create new key to create new Live Secrets, and Live Publishable Tokens.

Use your Secret key in the Staging environment provided when your account is created. You will not gain access to production keys until Checkr credentials your account for production API access. Once your account is credentialed, go to Account settings > Developer settings to create and manage your API keys.

Use Secret Keys and Tokens while testing your integration. Staging environment API calls are free, and will return fake data. When you’re ready, work with Checkr Customer Success to generate production Keys and Tokens, and go live with your integration.

Account Webhooks

Use account webhooks to receive updates on objects created with the API. You must create webhook endpoints and add them in the Checkr dashboard to get status updates. You may create 2 endpoints within your staging or live environments.

Attempts to create more than 2 endpoints within either environment will result in a "Quota limit exceeded" error.

The Account Webhooks section lists existing and allows you to create new webhooks.

To add a new webhook for your account:

1. Enter a URL.

• HTTP, HTTPS, and AWS SNS schemes are supported.
• HTTP can be added only for Test environment webhooks.
• HTTP and HTTPS endpoints must be publicly accessible.
• AWS SNS endpoint must follow the format:
  `sns://<key_id>:<access_key>@<region>/<topic_owner>/<topic_name>`

2. Select the Live environment.
3. Select a jurisdiction: US or CA.
4. Choose to Include related object in payload, if desired.
5. Click Add to create the new webhook.

To acknowledge receipt of a webhook, your endpoint should return a 2xx HTTP status code. Any other information returned in the response headers or response body is ignored.

If a webhook is not successfully received for any reason, Checkr will continue trying to send it every minute for 10 minutes, then every hour for 24 hours.

Monitor webhook logs in the Logs page, under the Webhook Logs tab.

After you create webhooks, you can subscribe to the updates you want.

Integrations

Use the Integrations page to view and manage your partner integrations.

Partner integrations you have enabled for your account appear on this tab. To disable the integration for your account, click Turn off. For more information, contact your Checkr Customer Success Manager.