The SmartRecruiters integration has been upgraded to give customers a choice on how background checks are selected for candidates.
With CheckIntelligence, SmartRecruiters can now send a generic assessment order and rely on CheckWorkRights to determine which checks are required based on employee metadata such as business unit, location and job role.
Key changes:
The SmartRecruiters Integration will support either model as chosen by the customer:
Package driven (existing behaviour)
CheckIntelligence (new behaviour)
Dynamic check determination with CheckIntelligence:
In CheckIntelligence mode, the set of required checks is determined by CheckWorkRights and could change over time. SmartRecruiters will not need to know the individual checks in advance.
When using CheckIntelligence all relevant checks are returned, this includes one off checks that may need to be manually enabled.
Step 1: Activate the CheckWorkRights Integration in SmartRecruiters
To start using CheckWorkRights with SmartRecruiters, you first need to connect the integration follow these steps to complete the connection:
Step 2: Chose the Check Creation Model
CheckWorkRights now supports two models for determining which checks are run for candidates.
You can only choose one model per SmartRecruiters integration.
Option 1: Packages (Original Method)
This is the original SmartRecruiters integration model.
In this approach, recruiters select a package of checks, and CheckWorkRights runs the checks that belong to that package.
Option 2: CheckIntelligence (Automated)
CheckIntelligence allows CheckWorkRights to automatically determine which checks are required.
Instead of SmartRecruiters selecting a predefined package, SmartRecruiters sends a generic request, and CheckWorkRights evaluates the candidate using configured rules. This removes the need to create and maintain large numbers of packages.
How to switch your package driven model to CheckIntelligence Automation:
Contact CheckWorkRights team to enable and configure CheckIntelligence Packages.
Enable CheckIntelligence Package selection for SmartRecruiters.
Once CheckIntelligence is enabled by the CheckWorkRights team, admin users with the ‘Administrators’ profile in CheckWorkRights can choose the Check Creation Model, this is by default the original package driven model.
To change this to CheckIntelligence:
CheckWorkRights → Admin → Integrations → SmartRecruiters → Configure
At the top of the configuration screen you will see Check Creation.
Choose one of the following:
Use Packages (Original method)
Use CheckIntelligence (New Automated Rule-based Method)
Name your package, this will appear in the drop down list in SmartRecruiters and can be used with automation flows.
Click ‘Save Details’
Your Automated Package selection is ready for use.
How it works:
SmartRecruiters sends a generic assessment request.
Candidate metadata is passed to CheckWorkRights (for example job role, location, business unit).
CheckIntelligence configured rules evaluate the candidate.
The appropriate checks are automatically created.
SmartRecruiters receives results for all relevant checks.
Example rule:
IF: Job Role = Store Manager AND Location = NSW
THEN assign the following checks:
Work Entitlement Check
Police Check
SmartRecruiters behaviour in CheckIntelligence mode
When CheckIntelligence is enabled:
SmartRecruiters will see only a single ‘CheckIntelligence’ package
Customer-created packages are hidden
SmartRecruiters sends a generic order to CheckWorkRights
CheckWorkRights determines the required checks
Existing SmartRecruiters packages remain stored in CheckWorkRights and customers can choose to switch back to Option 1: Package Driven.
Candidates with background checks in progress will not have any changes or updates to their checks applied retrospectively.
Configure Field Mapping for CheckIntelligence
When using CheckIntelligence, SmartRecruiters must send relevant Job Fields from the candidate profile so that rules can be evaluated.
These fields are mapped during integration configuration.
Go to:
SmartRecruiters → CheckWorkRights Integration → Configuration
You will see Field Mapping for Package Selection.
Here you map SmartRecruiters custom fields to the fields used by CheckWorkRights.
Example mapping:
SmartRecruiters Field | CheckWorkRights Field |
Job Title | Job Role |
Work Location | Location |
Business Unit | Business Unit |
This mapping tells CheckWorkRights how to interpret the data sent from SmartRecruiters.
Example:
SmartRecruiters sends:
Job Title = Store Manager
CheckWorkRights maps to: Job Role = Store Manager
CheckIntelligence rules will then evaluate that value.
Checklist for enabling Option 2: CheckIntelligence
Review and Align naming conventions between SmartRecruiters and CheckWorkRights:
Business Units
Locations
Job Roles
Avoid multiple variations of the same value (for example ‘Store Mgr’, ‘Store Manager’, ‘Store Manager – FT’)
Contact CheckWorkRights team to configure CheckIntelligence
Tips for successful package automation:
For CheckIntelligence rules to work correctly, the values sent from SmartRecruiters must exist in the corresponding datasets within CheckWorkRights.
Example Successful automation:
SmartRecruiters sends: Job Title = 'Store Manager'
CheckWorkRights CheckIntelligence looks for mapping of Job Title to ‘Job Role’
The Job Title ‘Store Manager’ exists as a Job Role value in CheckWorkRights.
CheckIntelligence rules exist for Job Title: Store Manager
CheckIntelligence rules assign:
Work Entitlement Check
Police Check
Example Failed Automation:
If values do not match or are inconsistent, rules may not trigger as expected.
SmartRecruiters sends: Job Title = 'Stores Managers'
CheckWorkRights CheckIntelligence looks for mapping of Job Title to ‘Job Role’
The Job Title ‘Store Managers’ does not exist as a Job Role value in CheckWorkRights.
CheckIntelligence rules can’t find matching values for Store Managers
No checks triggered
Interactive demo on how this works.
