Skip to main content

OAuth 2.0 authentication for LexisNexis

LexisNexis is withdrawing Basic Authentication from its Bridger Insight XG screening APIs by 31 December 2026. Fenergo SaaS now supports OAuth 2.0 client credentials, and each client moves its own connection across from the LexisNexis Credentials tab.

Advanced Reporting - Report Scheduling Permission and Access Layers

Managing scheduled reports now has its own permission, and scheduled report results respect the access layers of the sender.

  • Reporting Schedule Edit permission: users need the 'Reporting Schedule Edit' permission to create, edit, pause, resume, reset (reactivate) and delete scheduled reports. KYRA:Report's schedule actions (create, update, reactivate and delete) also require it.
  • Scheduled reports run with the access of the schedule creator: each scheduled report runs as the user who created the schedule. The report contains only the data that user is permitted to see, based on their permissions and access layers at the time the report runs.

Please note that Reporting Schedule Edit is not granted automatically. An administrator must grant it to users who need to manage scheduled reports.

Additional Sources in Related Party Scoping Rules

This feature is currently in Beta and is available on request for client lower level tenants.

Additional sources have been added to Related Party Scoping Rules, allowing rules to be configured using further conditions. The Is Client field is now available under the Current Entity Metadata source, with a value of Yes or No, to include or exclude related parties based on whether they are clients. The In Scope Jurisdiction field is now available under the new Related Client Metadata source, allowing rules to be defined per jurisdiction based on the in-scope jurisdictions of the entity in journey.

User Guide Reference: Related Party Management Related Party Adapted Experience

KYRA:Docs: Reasons for Resolution Decisions and Extraction Rationale

KYRA:Docs now gives reviewers more control over the reasons recorded against resolution decisions, and shows the extraction rationale for every extraction. Reviewers can record an optional reason when they accept an extracted value or enter a custom value, configurators can choose whether a reason is mandatory when a reviewer discards, and the KYRA:Docs rationale is now shown for Match outcomes and for data groups after they have been actioned. No configuration is required to use the optional reasons and the rationale.

Agency Offboarding: Offboard Managed Relationships, Products and Funds

A new Agency Offboarding journey enables users to end 1, many or all agency relationships, from a single fund's relationship up to a full Investment Manager exit. The journey will offboard the selected Managed Relationships and their Managed Products, offboard each Underlying Principal that has no active agency relationship left, and create Data Deletion Processes so that data is retained in line with the configured Data Protection Regimes.

KYRA:Docs: Tenant-Level and Document Type Instructions

KYRA:Docs Managed Knowledge Base Instructions can now apply more broadly than a single Data Group or Field. Select Tenant (all documents) to write one Instruction that applies to every document in your tenant, or select Document Type to write one Instruction that applies to a specific Document Type, such as Passport, instead of repeating the same rule against each field. For example, a tenant-level Entity Data Extraction Instruction can tell KYRA:Docs to read all dates as DD/MM/YYYY, and a Passport Instruction can tell it to return the full four-digit year wherever the expiry date shows only two digits.