Overview
This release delivers a series of targeted improvements across both the Broadbean and Idibu integrations, directly addressing customer-reported issues and extending the capabilities of two of Access Recruitment CRMs key third-party job posting tools.
What’s new?
Consultants and resource consultants can now benefit from expanded candidate matching options within both integrations, giving greater flexibility when identifying the right candidates for posted roles. Idibu users can create new sources directly within the integration, streamlining how job postings are attributed and tracked. Primary consultant assignment has been improved within Idibu, ensuring accurate ownership of postings and candidate activity. Additionally, amber flagged records can now be added to the Idibu review list via a feature toggle or system setting, giving compliance users and team leaders better visibility and control over flagged candidate data without disrupting standard workflows
How do I start using it?
Broadbean - Configurable Duplicate Checking
What's New
Administrators can now configure the duplicate checking criteria used when processing inbound Broadbean applications. A new Duplicate Checking section has been added to the Broadbean integration tab, replacing the previous hardcoded logic with fully configurable settings for communication-based and name-based matching.
How It Works
The new Duplicate Checking section appears below the existing Broadbean configuration fields and above the Broadbean User Mappings section, with the following fields:
Communication Types
Three checkboxes: Email, Mobile, Phone - all checked by default.
At least one option must always remain checked; the last remaining checked option cannot be unchecked.
Communication Types Logic
A dropdown with two options: Or and And - defaults to Or (matching existing behaviour for backwards compatibility).
An info tooltip explains: "Or: a duplicate is identified if the candidate matches any of the selected communication types. And: a duplicate is identified only if the candidate matches all of the selected communication types.".
At runtime, Or flags a match if any one selected type matches; And requires a match on all selected types (if only one type is selected, And behaves the same as Or).
Name-Based Check
Checkbox, checked by default. When unchecked, the Name Matching Method dropdown is hidden, and no name-based logic is applied; re-checking restores the previously selected method.
An info tooltip clarifies that this check is always applied in addition to the selected Communication Types.
Name Matching Method
(visible when Name-Based Check is enabled)
Dropdown with two options: File As and Name and Surname - defaults to File As.
'File As' matches against File As.
'Name and Surname' matches against the name/surname fields.
When a duplicate is detected, use:
Radio options of: Most Recently Modified (default) and Oldest Record.
Determines which candidate record is used as the target when two or more matches are found. This has no effect if only one match is found, and doesn't influence whether a duplicate is detected in the first place — only which record is acted on.
Combined logic:
When Name-Based Check is enabled, the system applies the AND logic between the name match and the communication type match — a candidate must satisfy both to be treated as a duplicate. A match on either alone is not sufficient.
User Benefits
Administrators can tailor duplicate detection to their agency's recruitment processes instead of relying on fixed, hardcoded rules.
Reduces the risk of both missed duplicates and false-positive matches by allowing precise control over matching criteria.
Default settings preserve current system behaviour, so existing customers see no change unless they actively reconfigure.
Clear control over which record is retained as the "master" when duplicates are found.
Where to Find It
Tools ; Integrations ; Broadbean (tab) ; Duplicate Checking section
Broadbean - Amber-Flagged Candidates in the Review List
What's New
Users can now choose whether Amber-flagged applicants sent from Broadbean are automatically added to the Jobs Review List. This gives recruitment consultants visibility of candidates who need further review, without having to leave the ARCRM workflow to action them.
How It Works
A new Add Amber Candidates to Review List checkbox has been added to the Broadbean User Mapping dialog:
Appears as the last field on the form, below Resp. for Jobs posted by oth. Users.
Unchecked by default.
Always visible, regardless of whether Multi-User View/Action is enabled.
The saved state reflects whatever the user last chose (checked = enabled, unchecked = disabled), and the dialog will show that same state the next time it's opened.
Runtime behaviour when Broadbean sends an inbound applicant webhook:
Candidate rank | Checkbox checked | Checkbox unchecked |
Amber | Added to the Review List (same handling as Green) | Not added (matches current behaviour) |
Green | Added to the Review List — no change | Added to the Review List — no change |
Red | Not added — no change | Not added — no change |
Broadbean User Mappings sub-list
An Add Amber Candidates to Review List column has been added to the grid as a default column, showing a checkbox per row reflecting that user mapping's saved value. The column remains visible even after selecting Restore Defaults.
User Benefits
Recruitment consultants can now track and action Amber-flagged applicants that require closer review, on a per-user basis, without any change to the existing Green or Red handling.
Where to Find It
Tools ; Integrations ; Broadbean (tab)
Jobs ; Contract/Permanent Jobs ; Broadbean (tab)
Idibu - Configurable Duplicate Checking
What's New
Administrators can now configure the duplicate checking criteria used when processing inbound Idibu applications. A new Duplicate Checking section has been added to the Idibu integration tab, replacing the previous hardcoded logic with fully configurable settings for communication-based and name-based matching.
How It Works
The new Duplicate Checking section appears on Tools ; Integrations ; Idibu, below the Show Webhook Credentials button, using the same dark grey full-width banner style as other config section headings.
Communication Types
Three checkboxes: Email, Mobile, Phone - all checked by default.
At least one option must always remain checked; attempting to uncheck the last remaining option is prevented, with an inline error: At least one communication type must be selected for duplicate checking.
Communication Types Logic
A dropdown beneath the checkboxes, with two options: Or and And - defaults to Or.
An info tooltip explains: Controls how the selected communication types are evaluated when detecting duplicates. Or: a duplicate is identified if the candidate matches any of the selected communication types. And: a duplicate is identified only if the candidate matches all of the selected communication types..
At runtime, Or flags a match if any one selected type matches; And requires a match on all selected types. This setting has no effect on the Name Based Check.
Name Based Check
Checkbox, checked by default, with an info tooltip.
Tooltip explains: This check is always applied in addition to your selected Communication Types. For example, if you have selected Email and Mobile with 'Or' logic, the system will look for records matching the Name Based Check and either of those communication types..
When unchecked, the Name Matching Method dropdown is hidden; re-checking it displays the dropdown again.
Name Matching Method
Dropdown shown only when Name Based Check is enabled.
Two options: File As and Name and Surname - defaults to File As.
When a Duplicate is Detected, Use:
Final field in the section, rendered as two radio buttons: Most Recently Modified and Oldest Record - defaults to Most Recently Modified.
Only one option can be selected at a time.
If two or more matching candidates are found, the system selects the record matching the configured preference. If only one match is found, this setting has no effect. It does not influence whether a duplicate is detected only which record is acted upon once one is confirmed.
User Benefits
Administrators now have full control over how Idibu duplicate checking behaves, rather than relying on hardcoded logic. Communication-type and name-based matching can be tuned to the organisation's needs, and the outcome of a duplicate match (which record is retained) is now explicit and configurable rather than assumed.
Where to Find It
Tools ; Integrations ; Idibu ; Duplicate Checking section
Idibu - Primary Consultant on the Applicant Record
What's New
Administrators can now control how the Primary Consultant field is populated on applicant records created via Idibu. Previously, the Primary Consultant on these records was left blank, which had been causing reporting issues for clients (including a specific case where applicants processed into the CRM showed the 'created by' user as 'admin admin'). A new configurable setting resolves this by letting admins choose the source of the Primary Consultant.
How It Works
A new App. Primary Consultant dropdown has been added to Tools ; Integrations ; Idibu
Sits within a new Applicant Record Configuration section, at the bottom of the page, beneath the Duplicate Checking Configuration fields.
Two options: Job Primary Consultant (selected by default) and User flags as Shortlist/Keep on File.
An information icon next to the label explains the setting on hover: This selection will set the selected primary consultant on applicant record (only if the applicant record does not exist). If 'Job Primary Consultant' option is selected, the applicant primary consultant will be the same as Job's primary consultant. If Idibu is accessed outside Access Recruitment CRM, then the Job's primary consultant will be added by default irrespective of the selection made here.
When 'User flags as Shortlist/Keep on File' is selected
For a new applicant record created via the Idibu tab card, the Primary Consultant is set to the user who performed the flagging action.
Applies to both the Shortlist and Keep on File flag actions.
If more than one user could be attributed, the most recently created user account is used (matched via the identity email field on the users table).
When 'Job Primary Consultant' is selected
The Primary Consultant on the new applicant record is set to the Primary Consultant of the job the applicant applied for.
If the job has no Primary Consultant assigned, no Primary Consultant is set on the new applicant record.
Existing applicant records
Regardless of which setting is selected, if an Idibu applicant matches an existing applicant record in Access Recruitment CRM, that record's existing Primary Consultant is never updated or overwritten.
Navigation
Tools ; Integrations ; Idibu ; Applicant Record Configuration
Broadbean/Idibu - Source Processing
What's New
Applicant records created via the Idibu or Broadbean job board integrations now resolve their Source automatically, without creating duplicate Source codes in the system.
How It Works
When an Idibu or Broadbean applicant is processed, the system follows a tiered lookup to determine the correct Source:
System code match: A system code is constructed from the source description sent by the job board, formatted as SRC_BOARD_ plus the description in uppercase with spaces replaced by underscores (e.g. 'Indeed' then SRC_BOARD_INDEED). This is matched against existing records in dbo.Sources; if found, the existing SourceId is reused.
Description match (Idibu only): If no system code match is found, the source description text is matched against the Description field of existing dbo.Sources records. A match reuses the existing SourceId without overwriting its system code.
New source creation: If neither lookup finds a match, a new dbo.Sources record is created using the constructed system code and the exact description sent by the job board (e.g. 'CV Library' then SRC_BOARD_CV_LIBRARY).
No source sent: If the job board sends no source description (NULL or absent), no lookup or new record creation occurs, and SourceId remains NULL.
In all cases, the resolved (or newly created) Source is applied to the applicant record on insert, the CV record, and the review list entry. Where an incoming payload matches an existing applicant (duplicate detected by name and communication detail), the existing applicant's Source is preserved so only the new CV record and review list entry pick up the Source from the incoming payload.
User Benefits
Keeps the Source list of values clean, by preventing duplicate Source codes from being created for the same job board.
Ensures Source reporting and filtering remain accurate and consistent for applicants brought in via Idibu or Broadbean.
Preserves existing applicant Source data on duplicate detection, avoiding unintended overwrites.
Where to Find It
Jobs ; Contract Jobs/Permanent Jobs ; Idibu (tab)
Jobs ; Contract Jobs/Permanent Jobs ; Broadbean (tab)
Applicants ; Details (tab) ; Source (field)