vID 18 updates

The mobile and web app applicants use to scan an ID and take a selfie for identity verification.

FIXED

• Corrected reversed on-screen guidance during ID scanning — "move left" and "move right" prompts now point the way that actually centers the ID.

• Fixed the ID scanner occasionally getting stuck in a loading state after a failed capture, which had forced some users to restart the app.

• Smoothed the camera's autofocus during ID capture so it settles on the document instead of pulsing in and out of focus.

• Reduced false rejections during selfie capture caused by the system misreading open eyes as closed — a problem that disproportionately affected users wearing glasses or in uneven lighting.

• Stopped brief lighting changes, like a passing shadow, from resetting an in-progress selfie capture.

• Fixed some valid invite links failing to open correctly on Android.

• Fixed a crash that occurred when a form included a hidden field with a pre-set value.

• Fixed failed photo uploads sending users all the way back to redo their entire ID scan, instead of simply retrying the upload.

• Fixed a glitch on employment forms where entering a date would unexpectedly pop open the next field's dropdown menu.

IMPROVED

• Sharpened the accuracy of on-screen positioning guidance during ID capture, so instructions better match what the camera actually sees.

• Fixed inconsistent auto-capture behavior during ID scans caused by the app comparing mismatched camera frames.

• Manual entry forms now automatically scroll to the first field with an error, so mistakes are easier to spot and fix.

BEHIND THE SCENES

• Added diagnostic tracking to the selfie capture flow, developer tooling improvements, and new automated test coverage for the ID scan, login and sign-up flows — no visible change, but fewer issues should slip through in future releases.

Backend 8 updates

The core platform that powers order processing, permissions, and Cortex's data behind the scenes.

FIXED

• Fixed completed county-level criminal searches not appearing when looking up an order's search history through the API.

• Recovered an order that had stalled after a brief service interruption, without duplicating any vendor work or charges.

• Processors can now edit an applicant's SSN from the Edit Applicant screen — a permissions bug had been blocking this.

IMPROVED

• Strengthened how order-processing steps are saved and tracked internally, cutting down the chance an order silently stalls without anyone knowing.

• Tightened security around how report and document links are handled, closing a gap that could have exposed sensitive file links.

BEHIND THE SCENES

• Internal data-consistency safeguard for how version numbers are recorded — no visible change.

Frontend 25 updates

Cognition and Cortex — the web apps CRA staff and clients use to manage orders, disputes, and accounts.

NEW

• CRA compliance teams can now submit a dispute on an applicant's behalf directly in Cortex, replacing a manual workaround.

• Added a simple on/off toggle for enabling CRA-submitted disputes in an organization's settings, instead of requiring a manual backend change.

• Applicants on a slow connection now see a warning during ID/selfie capture explaining why things might be slow, instead of a silent failure.

FIXED

• Fixed an apartment/unit number not saving correctly when editing an applicant's address.

• Restored quick access to "Reorder" and other common order actions that had been buried in a menu.

• Fixed order-detail buttons crowding or overlapping on smaller screens.

• Fixed webhook-failure notification emails linking to the wrong organization.

• Fixed the "Delete Organization" confirmation button staying greyed out even after correctly typing the confirmation text.

• Replaced a confusing error shown when logging into Cortex while a two-factor login was already in progress in another tab.

• Applicants who land on an error page mid-verification are now offered a way to resume, instead of getting stuck.

IMPROVED

• Added checkbox and row selection to data tables across the app.

• Added per-row loading indicators to data tables for clearer feedback while information loads.

• Improved column alignment, width, and text styling across data tables for better readability.

• Restored the row options menu in the redesigned table component.

• Sped up and improved the accuracy of organization search.

• Added pagination to the API keys list so accounts with many keys load faster.

• Polished tooltip styling to match the rest of the design system.

• Standardized fonts across the dispute center and its emails for a more consistent, on-brand look.

• Set up new intake forms as part of onboarding a new corporate client.

BEHIND THE SCENES

• Component documentation, form-autofill hardening, and internal code cleanup across the design system — no visible change.

Synapse 41 updates

The automation engine that reviews search results and criminal records to help build accurate background check reports.

FIXED

• Fixed certain background check orders getting stuck mid-process and never completing.

• Fixed a bug where a guilty criminal disposition was incorrectly withheld from a report as if it were a non-conviction.

• Fixed valid, reportable criminal charges occasionally going missing from a report when part of a case needed manual review.

• Fixed a timing issue where an order could finalize before all of its automated checks had actually finished.

• Fixed criminal-record review outcomes being mislabeled as "automation failed" instead of showing the correct review result.

• Fixed a failed county-level search dispatch caused by a jurisdiction naming mismatch.

• Fixed an error that could occur while processing person-search results during case formation.

• Fixed a data-entry issue where a client's ID and name fields could be swapped, which had caused searches to fail.

• Fixed staff working across multiple organizations occasionally seeing automation data from an organization other than the one selected.

• Fixed a mismatch that could cause background processing to run under the wrong organization.

• Resolved several case-formation issues reported by a client, including search-jurisdiction handling and review routing.

IMPROVED

• Improved matching for alias names with swapped first and last names, now based on how often the pattern actually occurs rather than a strict rule.

• Reduced unnecessary manual reviews triggered when an alias's last name legitimately differs from the name an applicant provided.

• Nickname matching now works both ways — recognizing "Nicholas" as a match for "Nick," not just the reverse.

• Added an extra safeguard that routes unusual or uncertain name variations to a human reviewer instead of processing them automatically.

• Expanded nickname recognition (e.g. "Peggy" for "Margaret") for a partner's criminal-record automation.

• Completed a multi-part rebuild of the case-formation matching engine, improving the reliability and consistency of automated identity, address, and alias evaluation.

• Tightened rules for classifying incomplete criminal-record outcomes, so ambiguous records aren't mistakenly treated as clear.

• Added full support for recognizing "expunged" as its own criminal-record outcome, rather than a generic catch-all.

• Strengthened internal data-integrity checks for how criminal-record outcomes are cataloged.

• Improved separation between legal-status classification and reporting policy, for more consistent record handling.

• Added configurable rules for when to automatically run deeper county-level searches on criminal records.

• Background processing now skips and logs any client missing a required setup, instead of failing an entire processing batch.

• Tightened security on Synapse's API to block requests from untrusted sources.

BEHIND THE SCENES

• Migrated the disposition classifier to a newer AI engine with no change to how decisions are made, plus investigation of a processing error message — no visible change.

• Database and deployment infrastructure improvements — no visible change.

• Configured and onboarded several new clients and packages onto the automation platform — no visible change for existing users.

Integrations 2 updates

Connections between Cerebrum and outside systems — client platforms, screening vendors, and background check providers.

FIXED

• Fixed an incorrect account-routing setting that had been affecting order flow for a client account.

BEHIND THE SCENES

• Added automated test coverage confirming that decisions made by our screening partner correctly sync back to update an order's score — no visible change.