Overview

With its latest release Klear.ai introduces significant updates across multiple areas, aimed at improving functionality, streamlining workflows, and enhancing the user experience. 

Significant changes include a redefined claimant-to-coverage relationship and a revised Policy screen to meet the industry standards. Updates to the Claim and Occurrence-level screens streamline claim and occurrence management, while enhancements to the Communications, Incident Details, Payment, and Reserve screens within claims improve the handling of claims and transactions.

The introduction of the Occurrence module enables users to define and associate claims with specific occurrences, enhancing management of complex scenarios. Additionally, user security updates offer more control over access and permissions, ensuring data security.

These improvements will optimize workflows, efficiency, and security across the system.

Performance Improvements & Future Roadmap

Klear.ai placed a strong emphasis on enhancing platform speed and responsiveness across key modules. Load times have been significantly improved in several high-traffic areas, including:

• Claims Search
• Payment Screen
• Service Scheduler
• Policy Management
• Communication
• Time Tracking
• ISO Reporting
• Litigation Tracking
• Incident Only Reporting
• General Claim Screens

Additional reporting optimization has also been completed. Key real-time reporting fields such as AdjudicationStatusID, Examiner/Supervisor UserIDs, and important claim dates (Accepted, Denied, Delayed) are now stored directly in the Claim table. This eliminates the need for heavy sub-queries and significantly improves paginated report performance. 

• Story: I10079

Looking ahead, performance continues to be a top priority. Ongoing efforts are focused on further optimizing the following areas:

• To-Do List
• Inbox
• Financial Screens
• Approvals

Administration

Bank

• Bank Account(s) can now be linked to multiple entities without limitations. 

• Story: I1467

• The "Approvals" portlet on the Bank screen enables email-based check approvals with defined approval settings.

• Story: I6792

• The "Expiration Date" and "Low Threshold Funds" fields have been added to the Bank Account screen. Additionally, a new "Assignment" portlet is now available, enabling Admins to assign users to the Bank Account.

• Story: I6925

• A new approval mechanism has been introduced at the Bank Account level to support improved email-based approval workflows for check processing. Three new fields “Threshold Amount”, “Approval Email”, “Denial Email” are added at the Bank Account level.

• Story: I3860

Catastrophe  

• The "Event Management" screen is now "Catastrophe," showing only Occurrences classified as Catastrophes. It lists Catastrophes and their associated Claims.

• Story: I5041

Claim Number Generator

• Enhancements to the claim number generator to support dynamic conditions and fiscal year-based auto reset.
• Users can now select the date source for claim number generation. Added LOB Group and LOB filters under "Claim Creation". Both defaults to Select All. 

• Story ID: I4292 

• Enhanced claim sequencing logic by allowing clients to define custom date ranges and select the reference date field (either Incident Date or Claim Creation Date) for sequencing purposes.

• Story: I8741

Claimant to Coverages, 1-to-many

The underlying data model for Commercial Property, Auto and General Liability (e.g., non-Workers’ Comp) has been enhanced to allow multiple coverages (sometimes called “sub-coverages” or “sublimits”) to be associated to a single claimant.

In Klear.ai, a policy and policy period record is agnostic to Insurance Line/Line of Business.   Many combinations of Lines and Coverages (AL:PD, or GL:BI, or WC: Part A) can exist under the same policy record.  Groupings of coverage layers and subordinate Participation distributions are shared among coverages with the same Line of Business.

When a claim is created, it is related to a particular Line of Business under a selected Policy Period.  (Auto Liability, for example).  One or more valid coverage relating to the selected Line of Business (PD, BI, Med Pay, as examples) may be related to one or more claimants under the claim.  Payments may not be made to or on behalf of a claimant unless a valid coverage is selected (and it is not disclaimed).

Financials (Reserves, Payments, Recoveries) are siloed on the basis of a Claimant and his or her triggered coverage.  Thus, when a transaction is created, the examiner must select to which Coverage the monies are related.

Client

Client Hierarchy Changes

This release introduces major updates to support flexible client account hierarchies, many-to-many employer relationships, and a more robust data security model to maintain complex client structures within the Klear.ai system. 

Key highlights include:

• On the Client Details screen, the client structure accordion will now display client hierarchy in a searchable tree format. 
• The Employer screen has been moved out from within a client to the Administration’s left navigation panel.
• Member Hierarchy tables will be updated as the user saves changes to a policy. 

• Story: I4096

Employer

• Employers can now be flagged as “Public Entity” indicating whether they are private or public entities.

• Story: I3029

• Client Handling Instructions can now be added at Employer level via the respective portlet on the Employer screen.

• Story: I5454

• A new “Combine Payment” flag is added to the Employer screen. Activating this flag will combine the various payment transactions for the injured worker into a single check.

• Story: I8011

• Following new fields have been added to the Employer screen for visibility and maintenance: Employer ID (Read-Only), Employer Group, Occupation Group, and Fiscal Year.

• Story: 10172

Physical Property and Vehicle

• "Policy details, including Policy Number, Effective Date, Expiration Date, and Coverage Type, have been added to the Physical Property and Vehicles grid. The grid now also displays vehicles with duplicate entries based on the Policy and Policy Period."

• Story: I3998

Policy

• The Policy screen now supports Coverage Layers and Participants. The Vehicle and Physical Property section has been moved to Coverage. If Coverage Layers are associated with coverage, the Layer name will be displayed against the Coverage, Coverage Layer, and Participants.

• Story: I3998

• Selecting a Line of Business for a Coverage defaults to the Coverage Layer, restricting subsequent layers to the same LOB.

• Story: I5028

• A “Certificate Number” field has been added to the Policy Information section to capture certificate numbers associated with excess policies.
• The “Excess Reportable (%)” field has been relocated to the Coverage Layer section for improved context and usability.
• A new “Share Name” field has been added to the Participants section, allowing participants to optionally enter a reference name.

• Story: I7358

• A new feature adds a delete button on the Policy screen. Policies linked to any active or historical claims cannot be removed. This helps avoid accidental data loss and maintains data integrity.

• Story: I9130

• The policy screen ensures that all records are retrieved quicker, enhancing usability for clients managing large policy libraries.

• Story: I9625

• The "Insurance Name" field has been converted from free-text to a dropdown linked to a new master reference table to support policy grouping and reporting needs. Existing distinct values have been migrated, and related reports updated accordingly.

• Story: I10272

• A new Self-Insured field is added to the Policy Period UI, within the Policy Period panel.

• Story: I9595

• Enhancement to the Bank and Bank Account dropdowns in the Policy and Coverage Layer have been combined into a single fixed-width, searchable dropdown.

• Story: I10212

Client Defined Fields    

• A new “Tags” field on to the Client Defined Fields screen enabling users to define fields as tags.  

• Story: I2172

Client Handling Rules

• The “Starting Date” dropdown now includes options for “Employer Knowledge Date,” “Adjusting Loc Received Date,” and “Decision Date.”

• Story: I3668

• The Trigger Field dropdown now includes Notes and Task Types, enabling rule configuration for specific types.

• Story: I3669

• Selecting a canned rule from the Condition Type dropdown locks Execution Type to Scheduled. Users can set the schedule via the Schedule button.

• Story: I3795

• The CHR screen now supports rule triggers with arithmetic operations for scheduled rules and enables configuring the Letter Approval process.

• Story: I3666, I6340

• The Field Adjustment section has been added to make fields required, read only, or to a certain value. 

• Story: I1632

CMS Reporting Entity

• The “CMS Reporting Entity (RRE)” screen introduced in the Administration panel allows you to maintain RREs across all layers from one screen.

• Story: I4241

Communication Setup 

• Admin users can now retrieve URLs for forms accessible to anonymous users directly from the DataBridge template pop-up on the Communication Setup screen.

• Story: I6765

Configuration 

Holiday Management

• The Holiday Management screen in the Administration module allows admins to define holidays with a Holiday name, Holiday date, and a move date to adjust scheduled payments falling on holidays.

• Story I2752

Inbox Saved Searches

• Standard Inbox Searches can be configured in the Administration section via the “Inbox Saved Searches” configuration screen.
• The Standard Inbox Searches created in the Admin section can be configured for a user via User Security.

• Story I4544

Packages

• A new Packages screen has been added under Administration> Configuration to allow users to create predefined communication packages. On the Communication screen within a claim, the Package button is now always enabled under the "All" filter:

• If no communication is selected, clicking the button opens a pop-up to select a predefined package.
• If communications are selected, the button retains its existing functionality.

• Story: I1746

Quick Links

• A new "Quick Links" screen has been added under System Configuration, enabling users to configure website URLs. These URLs will appear as child links under Quick Links on the initial left navigation panel and will open in a new tab when clicked.

• Story: I6729, 10241

System Configuration

• Admins can now configure the ribbon to include all elements from the claim and claimant tables for both WC and GL LOBs. The ribbon will now be associated with InsuranceLineGroup rather than Insurance Line. New additions are made for Group IDs including JPA and SuperPool. 

• Story: I6855 

• A "Vendor Lookup Configuration" portlet has been added to the System Configuration screen, allowing admin users to configure the Vendor Search to display only active vendors. 

• Story: I3253

• New dropdown options have been added including Compensability (formerly Adjudication), Organization 1, 2, 3, Job Title for WC Claims and Alternate Claim #1 for PLCA Claims.

• Story: I7081

• A new Claim Apportionment header has been added at the claim level, displayed when the Apportionment flag is checked in the Injury Information section. This allows apportionment tracking at the claim level instead of only at the body part level, providing greater flexibility without impacting existing configurations.

• Story: I10643 

To-Do List Configuration

• A new "To-Do List Configuration" screen has been added to the Administration section, allowing users to view and manage To-Do List Widgets.

• Key features:

• Create and edit custom widgets (system widgets remain uneditable).
• Define widget name, entity, LOB, and CHR trigger conditions.
• Custom widgets function like system widgets.
• Up to eight columns can be displayed on the To-Do List.
• Widgets can be linked to a specific screen via a hyperlink option.

• Story I3218

Insurance Group

• For improved clarity, the Insurance Group displayed throughout the application will now feature a concatenation of the Insurance Group Name and Insurance Group Type.

• Story: I7417 

Service Scheduler

• This release delivers a refreshed layout and improved functionality to the Service Scheduler screen, including enhanced grid columns and new job management options.
• New Grid Columns Added include: Is Linked, Is scheduled, Service information, service run details, run scheduler, service scheduler job history, Service Name, Status (should be showing just three options Success, Failure, Success with Errors), Schedule, Next Run Time, Last Run Time, Last Run By, Created By, and Service Status.
• The screen allows Admins to delete jobs directly from the main grid. Admins can now delete jobs directly from the main grid. 

• Story: I6873

• The Service Scheduler page experienced delays due to large datasets. This update improves backend performance and front-end responsiveness, allowing for a smoother user experience. 

• Story: I9998

Claim & Incident Search

• The Claim Search screen has been renamed to "Claim & Incident Search" to better reflect the expanded scope and inclusivity of the search functionality.

• Story: I7549

• A new column, 'Coverage Type', has been added by default to the Claim & Incident Search results grid. A claimant can have multiple coverage types (1: many relationship), the grid may display multiple entries for a single claimant each representing a different coverage

• Story: I7852

UI & Search Functionality

• Support added for multiple claim types per claimant. Users can now manage various claim relationships (e.g., Liability + WC) under one claimant, increasing flexibility for coverage mapping.

• Story: I8157

• The litigation screen was redesigned for better usability and to support complex legal relationships. Key changes:

• Many-to-Many Structure: Multiple claimants, attorneys, and parties can now be linked to one litigation.
• Simplified Layout: New portlets for Parties, Attorneys, and Litigation Status History.
• Court Fields: Court Name and Court Type now use MST tables.
• Auto Fields: Filed Date and Appealing Party populate based on party data.
• Claimant-Attorney Links: Adding a claimant under an attorney auto-creates representation.
• Status Tracking: Status history shows changes over time.

• Story: I8249

• Enhanced the query logic and backend indexing, reducing load time and enabling users to quickly locate claims across both WC and Liability types.

• Story: I9540

• Applicable to both WC and Liability Claims, this improvement streamlined how time logs are recorded and loaded. Database queries were optimized for performance and reduced memory use.

• Story: I9967

Claims

Claimant Details

• The formula for calculating the “Expected Years” value has been updated. Going forward, a claimant’s life expectancy will be determined based on their current age and the national average. 

• Story: I1367

• The "RRE" portlet has been moved from the Incident Details screen to the Claimant screen and renamed "Medicare" for WC Claims.
• Additionally, the "Organization" accordion and the "Represented" checkbox have been relocated to the Incident Details screen.

• Story: I6980

• The WCMSA fields—MSA Amount, MSA Period in Years, MSA Type, MSA Administrator FEIN, Initial Deposit, Annual Deposit, and Case Control Number—have been added to the Claimant Details screen for Medicare Reporting in the respective portlet.

• Story: I5936

• The Dependent Information, Guardian Information, and Emergency Contact details for a claimant can now be captured directly on the Claimant Details screen. As a result, the Dependent screen has been removed from the system.
• Email is relabeled as “Work Email” while a new “Personal Email” field is added to Claimant Details screen.

• Story: I7638

• New IAIABC required fields “Alternate Employee Identification”, “Identification No.”, and “Jurisdiction Employee Security No.” are added to the screen for WC Claimants. These fields remain greyed out when the SSN is populated.

• Story: I8646

• Two additional data fields “Employee #” and “Occupation Code/Description” are added to the Liability Claimants Details screen.

• Story: I9559

• A new “CMS Representative” accordion is added to the Dependent section on the Claimant Details screen. 

• Story: I590

• A new checkbox field, CMS Non-Trauma Claim, has been added to the Medicare Claimant table to track non-trauma information. This field is now also available in the UI under both the Claimant Medicare section and the CMS section for user input and reference.

• Story #I9129

Communication

• Emails with large attachments, whether sent from within the claim system or the user's platform, will be transmitted via secure messaging. The system will conduct thorough scans of all inbound and archived emails to identify and address potential security threats.

• Story: I263

• The fields "Due Date," "Days Left," "Recipient Role," and "Recipient" have been removed from notes while a new "Attach Memo" button has been introduced to notes, which will remain accessible for saved notes as well.

• Story: I6684

• A new "Mark Incomplete" button has been added to completed tasks, enabling the functionality to mark completed tasks as incomplete.

• Story: I6685

• The “Recipient” dropdown in tasks is now a smart search wherein selecting a Recipient defaults the role for the selected user. However, the dropdown continues to limit results if the role is selected first.

• Story: I6686

• Emails can be replied to via the Communication screen within both WC and GL claims. Clicking on “+Add and Email” will automatically populate the claim number in the email subject line.

• Story: I6923

• When selecting communications on the Communication screen, the new "Package" button becomes available. Clicking "Package" opens a pop-up window displaying the selected communications, which can be rearranged and merged into a single PDF if they are mergeable.

• Users can define a Package name and choose to save it automatically, as a Draft, or download and email it. If all items are mergeable, the download will be a PDF; otherwise, it will be a zip file. The created package is saved as a separate communication type in the Communication grid.

• Story I1488

• Email functionality is enhanced to support automatic indexing of replied to the correct entity (for instance Claim) by appending the Entity ID and Entity Type ID to the email subject line in the format <current subject> ##<entityId>_<entityTypeId>##.

• Story: I9668

• Introduced pre-defined email templates for outbound messages (e.g., claims updates, reminders). These reduce manual typing and maintain communication consistency across departments.

• Story: I3967

• Optimized the rendering and load time for the WC Claim Communication page, especially in cases where large volumes of historical communications are stored.

• Story: I9545

• Added a “Quick View” (eye icon) in the Inbox and all communication grids for communication type “Document” only.

• Story: I9419

• Document Date and Export Date columns have been added to the Communication grid for Documents. These fields are now searchable and match the existing values from the Document View > Key Dates section.

• Story: I10888

Compliance

• Users can define the priority order of ICD codes through the Injury grid, ensuring that Body Parts are correctly associated with ICD codes to meet CMS 111 reporting standards.

• Story I4614

• To ensure compliance with the updated CMS111 requirements, a new functionality has been introduced to track additional data points, including the Workers’ Compensation Medicare Set-Aside (WCMSA) information.

• Story I5649

• ISO response tracking has been enhanced. Responses received post-ISO submissions are now displayed on the Compliancy screen within claims and also as Notes on the Communication screen. This eliminates the need for users to switch between screens.

• Story I3322

• FROI Eligibility and SROI Eligibility is shown on the Compliance screen

• Story I4251

• Enhancement to allow examiners to manually update the "FROI Eligible" checkbox, improving flexibility in state reporting scenarios. 
• "FROI Eligible" Checkbox Update 
  Now editable by examiners to handle ~30% of edge cases where FROI must be sent manually.  Becomes read-only once a FROI is triggered to maintain reporting integrity. 

• Story ID: I6016 

• Ability to add data elements specific to each MTC (Maintenance Type Code), enabling greater customization and control.

Enhanced workflow configuration for MTCs, including the ability to define how each MTC progresses from:

• Validation
• to State Submittal

      These updates improve flexibility and support more complex compliance scenarios.

This enhancement provides Admin users with greater control over MTC-specific configurations and workflow automation, streamlining the claims reporting process.

• Story: I8651    

• To improve usability and streamline workflows, CMS and FROI/SROI have been separated into two distinct screens within the Compliance module.
• Users now have the ability to create MTCs (Maintenance Type Codes) directly from the FROI/SROI screen.

• Story: I8650

This release introduces key updates to ensure accurate use of the Temporary Disability (TD) Rate for FroiSroi reporting and payment calculations.

Highlights:

• Accurate TD Rate Usage: The system now correctly references claimant.tdrate for payment calculations and UI display, ensuring reliable data for FroiSroi elements.
• Streamlined UI:

• Reinstated TD Rate in the Occupation and Compensation and Compensation portlets.
• Removed TD Rating and Total TD Amount fields, as they are no longer needed.
• Renamed the Compensation portlet to “Compensation Rates.”
• Removed the internal grid from the Compensation portlet; it remains only in Settlement with Commutation.
• Updated the Commutation portlet label to “Commutation Calculator.”

• Improved Payment Logic: All payment and scheduled payment calculations now use the correct TD Rate, replacing previous reliance on TotalTDAmount.
• Incident Detail Enhancement: Replaced the label “Unable to work at least one full day” with a clearer “Full Pay on Last Day” checkbox.

These changes improve data accuracy, enhance usability, and support consistent FroiSroi processing across the application.

• Story: I10053

Contact 

• CMS Representative added to the grid can be marked “Primary”. Once the “CMS Representative” checkbox is selected, the “CMS Representative Type” field appears on the screen.

• Story: I5905

Incident Details

• Waiting Period will be tracked on the Incident Detail screen instead of Work Status in the Initial Dates section. 
• A new read-only field labeled "SIR Amount" has been introduced in the Carrier Reporting Indicators section.

• Story: I4612

• The "Incident or Catastrophic" button is now relabeled and repurposed as "Occurrence," allowing users to associate or unassociate a claim with a specific occurrence. When associated, the claim appears as the first record in the pop-up grid, sorted by the latest occurrence. Users can also create new occurrences directly from the occurrence pop-up.

• Story: I5222

• The "Organization" and "Initial Treatment" accordions have been moved to the Incident Details screen from the Claimant and Injury screens, respectively. Additionally, a new "State Office" accordion has been added to the Incident Details screen.

• Story: I6980

• The “Incident Activity” field has been moved from Bodily Injury screen to the “Incident Details” screen and relabeled as “Incident Type”.

• Story: I6807

• Witness Statement Date, Primary Witness Name, Primary Witness Number, and Witness Statement fields are added after Incident Location for Liability claims.
• Fields associated with Risk Classification are moved to Carrier Reporting portlet. 

• Story: I7126

Indicators

• A new screen is introduced within claims to display both standard and CDF (Client Defined Fields) tags.

• Story: I2172

Injury Or Illness

• New fields including “Orientation”, “Body Part Digits”, “Status”, and an “Apportionment” checkbox are added to the Body Part/Nature of Injury section to record apportionment details. Claim’s meta data displays Apportionment as “Y” if any body part has an apportionment value set.

• Story: I359

• “Status”, “Status Date”, and “Comment” field added to the ICD accordion on the screen for the users to record ICD Status, ICD Status Date and ICD related comments.

• Story: I4332

• Two new dropdowns, “Body Part Direction” and “Body Part Identification” are added to the Injury Screen for WC Claims as a part of FROI requirement.

• Story: I6840

• “Date of Death” and “Time of Death” will be conditionally required if “Injury Caused Death” is true.

• Story: 4614

• “Injury Caused Death” is now a dropdown field
• “Body Part Orientation” field is repositioned. The “Body Part Digit- Fingers/Toes” field remains read only until the Body Part selected in the respective field are fingers or toes.
• A new cascading dropdown “Body Part Sub-Category-For Permanent Impairment” is added the options of which are restricted based on the Body Part selected.
• A new dropdown field “Permanent Impairment” has been added to record the if the required information.

• “Percentage of Injury” field is relabeled as “Permanant Impairment Rating”. The field will remain read-only unless “Permanent Impairment” is selected as “Yes”.

• Story: I8647

• Introduced a new P&S/MMI Date field on the Injury or Illness screen and in the claimantbodypart table to track individual P&S/MMI Dates for each injured body part.

• Story: I10141

ISO Claim Search

• A text field displaying “Match Found/ Match Not Found” is added for ISO Responses received.

• Story: I4083

• ISO Error Codes received will now be displayed on the ISO screen on one record per error basis.

• Story: I4086

• The “+Add” button displays an “Initial Request” option on claims with ISO Errors. The option is not available for claims with Match Found/Match Not Found ISO responses.

• Story: I4104

ISO Claim Search (PLCA)

• A new "Claim Administrator" dropdown has been added to the Employer, Insurance Group, and Insurance Company screens. The "External Code" field is now available on the Insurance Group and Insurance Company screens and tables, while both "External Code" and "NAICS Code" have been added to the Employer screens and tables.
• The "Claim Administrator" field pre-populates on the Policy screen based on the default UW Entity setting. The "ISO Loss Type" dropdown has been added to all PLCA Losses screens, preselected with the default value from the Coverage Type.

• ISO Search requests can either be added manually or can be automated via CHRs.

• Story: I6727

• Enhanced ISO Claim Search integration to support Property & Liability (P&L) workflow in addition to Workers' Compensation. New system settings to restrict searches to lead claimants, improved “Add” and “Discard” logic, and automatic handling of claimant replacements with configurable research options.

• Story: I10203

Left Navigation Changes

• The "Coverage" section in the left navigation is a parent category within both WC and GL claims. In WC claims, "Coverage" includes Employer and Policy screens. In GL claims, "Coverage" nests the Insured, Policy, and Triggered Coverage screens.

• Story: I5454

• The Financials section now includes the following screens: Reserves, Payments, Subrogation, Negotiated Liens, Withholding and Liens, and Direct Deposit.

• Story: I6980

• A collapsible Occurrence section is introduced within the left navigation of claims associated with an Occurrence. Upon expansion, the section displays all the Occurrence related screens.

• Story: I5223

Litigation

• “Pro Se” checkbox has been added to indicate if a claimant is representing themselves within the Litigation screen.

• Story: I2912

• A new "Attorney Survey" section has been added to the Litigation screen for ratable attorneys. Litigated claims with an Attorney Survey cannot be closed without providing attorney rating details.

• Story: I2549

• Litigation screen enhanced to support many-to-many relationships between claimants, attorneys/vendors, and litigation records. Added new fields along with “Litigation Status History” and “Parties” portlets to better track case details and progression

• Story: I8249

Treatment Authorization

• To support the storage of historical Utilization Review (UR) data, a new field, "Utilization Number", has been added to the Treatment Authorization screen and underlying data model.

• Story: #I9133

Loss Time & Work Status

• An “OSHA Information” accordion has been added at the end of the screen.

• Story: I6980

• The “Work Status” screen is renamed as “Lost Time and Work Status” allowing users to record and manage the lost time and work status information.
• Significant improvements have been made to how Lost Time information is managed between the Incident Details and Work Status screens. 
• The Loss Time values entered on the Incident Details screen will also be saved to a work status record. 

• Story: I8648

• RTW functionality enhanced in work status by adding a new standard status (-6, C, Continuing) and introduced Initial and Current RTW Dates in the Work Status section, derived from disability-related records. A new RTW Date field is added to transactions (auto-set as End Date +1 day), and Froi/Sroi logic now references this RTW Date instead of End Date.

• Story: I10012

• An "RTW with Full Pay" (Return to Work with Full Pay) field has been added to capture situations where the employee has returned to work without any loss in earnings. And a few existing fields in the Work Status section have been relabeled.

• Story: #I9166

• The 'RTW for Same Employer' field has been updated from a checkbox to a dropdown selection.

• Story: I10010

Occupation & Compensation

• The system auto-calculates the PD, Life Pension, Death Benefits, PTD and other disability benefits based on the claimant’s attributes. 

• Story: I2548

• The “Employer” field on the Occupation & Compensation screen for WC Claims now defaults to the Employer selected during claim creation.
• A new “Other Employers” portlet has been added to capture details of additional employer(s) the claimant is associated with. This portlet allows the users to record the Other Employers, Pay Type, Pay Rate, Hours Per Week, and any Comments. This functionality ensures Klear.ai clients can accurately determine the AWW.

• Story: I4540

• Users can now record the “Max Days Wage Continued” for the claimant. 
• “Sum Weekly Wage From Other Employers” and “Work Week Type and Schedule” for the claimant can now be recorded via the respective fields.

• Story: I8646

• The “TD Rating” and “Total TD Amount” fields have been removed from the Occupation and Compensation and Compensation portlets, as they are no longer relevant or used in calculations.

• Story: I10053  

• Enhancements were made to the UI to improve the display of supervisor contact information. A new 'Supervisor Cell Phone' column was added, and the existing 'Phone' field was renamed to 'Work Phone' for better clarity.

• Story: I7854

Payment

• Scheduled Payments falling on a holiday can now be manually moved to an earlier date.

• Story: I2752

• The “Transaction Type” dropdown now displays the Payment Type, Reserve Bucket, Sub-Reserve Type, and Recovery in the same dropdown in the mentioned order.

• Story: I4826

• Enhanced the refund process to ensure funds are correctly transferred back to the customer's bank account balance. This functionality is managed as a scheduler job, ensuring timely and automated execution.

• Story: I6346

• The system effectively calculates Penalties for late/missed TD payments and Interest for late payments.

• Story: I3029

• The system now auto-populates the days and weeks based on the From and Through dates and the selected Transaction Type. Additionally, the payment amount is automatically calculated and populated according to the Compensation Rates based on the specified Transaction Type.

• Story: I6814

• PLCA allows expense payments up to $5,000 on closed claims, with a message displayed: "For PLCA Closed Claims, the Expense Payment limit is $5,000, and the Loss Payment limit is $0." Expense payments can only be made for the lead claimant, and attempting to make a payment for a non-lead claimant will trigger a message: "Expense Payments are only allowed on the Lead Claimant."

• Story: I6900

• The new "Adjustment" payment method enables users with the "Ledger Adjustment" profile to create positive or negative transactions for single payments. Adjustments are processed immediately and affect the bank account balance and claim ledger. Recovery transactions impact the total recovered amount, not reserves.

• Story: I5076

• The Billed Amount and Payment Amount calculations now include Discount Amount and Discount Percentage details, with fields adjusting dynamically when the discount accordion is expanded.  
• The Applied Bank Account field now display the Bank Account, Associated Coverage Layer Description, and Current Balance. Additionally, all check action buttons have been moved to the "Check Accounting" window, accessible via a hyperlink that opens detailed check information.

• Story: I5293

• Checks will not be generated for payments without a payee address. Payments missing a payee address will not be processed.

• Story: I5969

• The system has been enhanced to automatically split check payments when the payment amount exceeds the threshold limit of the associated coverage layer.

• Story: I7773

• The "Adjustments" modal on the Payment screen has been reworked to improve usability and clarity when handling ACRs (Adjustment Correction Requests). This update enhances the user experience by streamlining the layout, improving field labels, and ensuring smoother data entry and review.

• The “Adjustment Amount” field can hold both positive and negative values. Users can add up to 3 ACH records via the “Add ACR” button.

• Story: I8656

• New validations have been implemented on the Payment screen to ensure accuracy and consistency when entering Lump Sum amounts and selecting Work Status.

• Story: I8649

• Enhanced integration on the Payment screen to automatically initiate the FroiSroi process upon adding a payment, supporting a more streamlined workflow.

• Story: 10122

• Enhanced handling of ACR entries used in FroiSroi data element calculations, including Net Weekly Wage. This includes following updates to the payment screen:

• Two new columns have been added to the BenefitAdjustment table- one to classify the entry as an Adjustment (A), Credit (C), or Redistribution (R), and another to define its financial impact (positive, negative, or neutral) on the billed amount.
• Implemented logic to automatically calculate the payment amount based on the selected benefit amount (1, 2, or 3) and the corresponding ACR reason’s impact classification. Entry of a reason is now required when an ACR amount is provided to ensure accurate calculation.
• Two new fields “Settlement Commutation Amount” and “Employer Paid Amount to Calculate TPD” are introduced in the “Adjustment” section on the Payment screen. These fields do not impact the billed amount at this time but has been added to support future functionality related to reduced earnings calculations in FroiSroi.

• Story: 10113

• A new field labeled “Account#” has been added to the Payment screen.

• Story: #I9164

• The Alternate Payee field is now retained when converting a Scheduled Payment to a Single Payment. This enhancement ensures both existing and future payments preserve the alternate payee designation during the conversion.

• Story: #I9172

• Performance enhancements ensure faster loading of payment screens, especially useful when many transactions or ACH records are present. The Klear team is aware of the performance issues on save and is actively investigating.

• Story: I9547

• New functionality allows users to manually select a bank account during payment processing when permitted by the LOB configuration. 
• Key changes:

• Manual Override: Users can choose from a dropdown of bank accounts across all LOB layers, if the LOB allows overrides.
• Workflow Impact:

• If bankaccountid is manually selected, it is preserved and not overwritten by the payment job.
• These payments are excluded from auto-layer logic, RRE assignments, and future auto-adjustments.

• Adjustments Portlet:

• Supports negative amounts
• Freezes “Adjustments” and “Billed” fields as read-only

• Allows broader account selection during adjustment entries

• Story: I10011

Reserve

• For Reserve transactions exceeding a user's approval limit, hovering over the "Approve" button shows a warning that the transaction is beyond their authority and will be queued for approval.

• Story: I3938

• A "Draft" button allows users to save reserves in a pending state for later review and updates, providing greater flexibility in reserve management.

• The "Deny" button has been added for WC and GL claims, enabling users to easily correct or deny reserve worksheets. This button, available in the Approvals portlet, allows users to select either "Deny with Corrections" or "Deny Entire Worksheet."

• Story: I6922

• A new "Created By" column has been added to the Reserve Worksheet grid to display the user who created each worksheet. This allows for easier tracking and follow-up with the specific user responsible for the entry.

• Story: #I9381

Settlement

• "Settled By" fields have been added to both the Litigation and Subrogation Settlement sections.

• Story: I2911

• A "Commutation" calculator has been added to the Settlement screen, which calculates and displays the Weeks Elapsed, Remaining Weeks, PV of Weeks, and other essential commutation attributes.

• Story: 2548

• The final settlement amount for both WC and GL Claims can now be recorded in the new “Settlement Amount” field.

• Story: I7055

• A new configurable logic has been added to the Settlement screen for specific Settlement Types. If the “RequireSettlementDate” is true for the selected Settlement Type the default Settlement Amount is set to $0 and Settlement Date becomes a required field.

• Story: I10638

Status & Assignment

• A "Delayed Reason" dropdown has been added, allowing users to specify a reason for the delay, which will be used for FROI/SROI reporting.

• Story: I2434

• Claims with the latest status as "Open" can only be marked as "Closed". Claims marked as "Closed" can only be marked as "Reopen" and claims with the latest status as "Reopen" can only be marked as "Closed".
• Either the Claim Status or the Current Adjudication Status must be populated. Updating one will make the other field non-mandatory.

• "Partially Suspended" and "Suspended" have been introduced as adjudication status options. Selecting either of these statuses will add the "Suspension Reason" and "Suspension Narrative" fields to provide the necessary details for IAIABC reporting requirements.

• Story: I4767

• A "Claim Adjusting Office" dropdown has been added to the Assignment and Adjudication screen, allowing users to record the adjusting office location associated with the claim.

• Story: I5063

• A new 'Void Claim' checkbox has been added to the Status & Adjudication screen. This flag can only be selected if the net sum of payments and reserves on the claim is $0. If it is not, the system will display a warning message. 

• Story: I5763

• The 'Pay and Close' checkbox has been introduced to enable automated claim closure after processing all unprocessed payments.
• A scheduled job will be created to monitor and close claims once payments are completed.
• This functionality applies to both Line of Business (LOBs) PLCA and WC.

• Story I6437 

• The 'Assignment & Adjudication' screen has been renamed to 'Status & Assignment.
• The 'Days to Decision' and 'Decision Date' fields have been moved from the 'Incident Details' screen to the 'Status & Assignment' screen.
• A new 'OSHA' accordion has been added to the 'Status & Assignment' screen.

• Story: I6980

• A "Coverage Type" dropdown has been added to the Status & Assignment screen for Liability claims.

• Story: I7126

• The “Claim & Adjudication” accordion is relabeled as “Claim & Compensability Status”
• The “Current Adjudication Status” field is relabeled as “Compensability”
• “Compensability Reason” and “Compensability Narrative” fields will be displayed only when the “Compensability” status selected is Denied or Partially Denied

• A new “Benefit Suspension Status” field is added. If the user selects “Suspended” or “Partially Suspended” the “Benefit Suspension Reason” and “Benefit Suspension Narrative” fields will be displayed.

• Story: I8645

• “Days to Decision” is now a configurable dropdown field.

• Story: I10571

Subrogation

• The Subrogation screen has been moved to the Financials section in the left navigation within a claim.
• Two new date fields, "Lien Notice Sent" and "Closed Date", have been added to the Subrogation screen.

• Story: I4333

Time Tracking

• The Time Tracking screen, available at both the Home and Claim levels, allows for accurate tracking of time-based activities.
• Klear.ai integrates the entire process, from entry and invoicing to reminders throughout.
• The Time Tracking pop-up can be enabled at the role management level. For roles with this feature enabled, users attempting to close a claim without accessing the Time Tracking screen will receive an alert to log their activities before proceeding.
• The Fees screen (in Administration) will derive its data from the Time Tracking screen. Fees marked as inactive will no longer appear on the Time Tracking screen.

• Story: I252

• Note on Time Tracking screen is not created, it will be a dashboard level, WC and GL.

• Story: I7372

Treatment

• The "NPI", "SSN/TIN/EIN", and "Network" fields have been added to the Physician Information section, with values fetched from the Vendor Management section
• Two new sections, "Referral Summary" and "Referral Details", have been introduced to the Treatment Screen.

• Story: I4615

Withholdings and Lien

• The "Withheld Payment Method" dropdown has been added to record the resulting payment method.
• A new "Auto Apply" checkbox has been introduced.

• A new multi-select "Transaction Type" dropdown has been added. If Auto Apply is selected, this field becomes required.
• "Schedule Start" and "Schedule End" have been relabeled to "Effective Date" and "Expiration Date", respectively.
• A "Withholding and Liens" portlet has been added to the Vendor and Sub-Vendor sections on the Vendor Detail screen.

• Story: I2458

• For payments that are already linked and split, the Linked checkboxes and the ‘Link Payment’ button will remain disabled.

• Story: I6329

Vocational Rehabilitation

• Voucher information for WC claims can now be tracked on the new Vocational Rehabilitation screen within the Incident section.

• Story: I6920

Dashboard

Claim Intake 

• Intake Form Auto-Population Enhancement. To align with standard behavior, the Intake Form now auto-populates AWW and Compensation Rates when Gross Wage and Frequency are selected. Additionally, Location Description will auto-fill from location.locationname when "On Employer's Premises" is checked. This enhancement resolves FroiSroi validation errors caused by missing data during claim intake, reducing the need for manual field toggling.

• Story: I10067

• The system now accepts and processes information that may not be directly tied to a Line of Business (LOB) or policy, enabling better tracking of pre-claim events.
• LOB selection on the claim intake screen is now optional, though recommended.

• If not selected, the system will assign default values 
• No policy selection is required for incident-only records
• “Incident Only” options will appear in the LOB dropdown only when no other LOB is selected

• If a claim is not yet linked to a policy (i.e., Claim ID not present in the ClaimPolicy table), a “Pending Coverage” warning will be prominently displayed.
• The “New” button for adding Payments and Reserves will remain disabled until the claim is associated with a policy.
• A “Select Policy” button will now be available on claims not linked to a policy. This enables users to attach a policy after selecting the appropriate LOB.
• Clicking the “Select Policy” buttons allow the user to select Line of Business, Policy, and Claims Made Date. 

• Story: I7369

• For claims created as "Incident Only" (for WC and PLCA) or "Near Miss" (for PLCA), pending coverage is prominently indicated. The Line of Business (LOB) description for these claims is displayed in bold red as: "Incident Only – Pending Coverage (WC/PL)".

• Story: I10065 

• An Occupation dropdown has been added to the WC Claim Intake screen, with options filtered based on the selected Employer.

• Story: I9112

Claim Search 

• Caseload transfer using the "Replace" button will occur only for original and replacement users with the same role.

• Story: I1325

• The Recent List will display the 15 most recently accessed records by the user, formatted as Claimant Last Name, Claimant First Name, and Entity ID.

• Story: I4650

• Claims and documents can now be filtered based on Assignment Role and Insurance Group.
• The Insurance Group will display both the Insurance Group Type and Insurance Group Name.
• Selecting an LOB group will impact certain search fields, making them cascade based on the selected LOB Group.
• For the LOB Group WC, the Claim Type, Incident Cause, and Injury Type will be cascading search fields. 
• For the LOB Group GL, the Coverage, Claim Type, and Folder will be the cascading search fields.
• When no LOB Group is selected, the following fields will act as standalone search fields for both Claim Search and Inbox Search.

• Story: I6817

DataBridge

• Creating forms with “No Login Required” will display disclaimer message for users to proceed with caution.
• The “Copy URL” button facilitates copying the form URL to clipboard.

• Story: I3508

• DataBridge form layouts can now be customized as per the form designer’s requirements. Form designer can now define the field width and the space between the fields in the form.

• Story: I7944

• While designing a DataBridge form fields can now be set as read-only.

• Story: I8797

• A new email functionality has been added to DataBridge, allowing automatic email notifications upon form (claim) submission. This is available when configuring new DataBridge Type Templates in Administration’s Communication screen, the following are now available on the Design Form page.  

• Story: I7889

• Selecting “Screen” in Record Type hides Login Type and Letter Template settings ensuring a cleaner, more intuitive configuration experience based on the selected Record Type.

• Story: I7939

• In DataBridge forms configured as screens, the 'Print', 'Attach External Document', and 'Save for Later' buttons have been removed from the top-right corner.

• Story: I7940

• A new data type has been added to the left navigation of the DataBridge form editor, allowing admin users to upload documents. Once saved, the attached documents will be stored as paperclips on the corresponding dynamic screen, similar to memo functionality.

• Story: I7941

• A new screen has been introduced to allow Admins to easily place DataBridge forms into specific components. This streamlined interface enables form selection, entity assignment, and precise component placement.

• Story: I7945

• DataBridge Forms will be available for the end users in the left navigation panel based on the placement configured by the Administration users within the component layout. End users will now be able to view, enter, and save all relevant form details directly from this interface.

• Story: I7946

• When duplicating an existing form, designers can now select a new Record Type during the duplication process. This enhancement allows for easier transformation of forms—for example, duplicating an 'Add' form as an 'Update' form—streamlining the design workflow.

• Story: I8798

• Implemented cascading dropdown functionality in the DataBridge Intake form, where Location and Location Sub Type fields dynamically filter based on the selected parent value.

• Story: I10114

• Introduced a Collaborate option in the DataBridge Form Designer to support multi-user form submission. This enhancement allows a single form to be divided into sections, each assigned to different users for sequential input.

• Assign specific sections to different users (by role or email)
• Each section has: Custom display rules, Individual submission handling, Configurable email notifications.
• Submitted sections are locked; only assigned users can edit their part
• Supports step-by-step form completion via anonymous links

• Story: I10331

• The visual design of the Employee Lookup form has been updated to align with the standard UI styles used across the application. Employee lookup buttons updated to standard style (white with blue text). Fonts, field sizes, labels, grids, and button styles standardized to match Back Office UI.

• Story: #I10273

• Enhancements have been implemented to support an approval workflow for Data Bridge forms and improve user access and submission tracking.

• Story: I8845

• DataBridge now supports configurable email notifications upon completion. Admins can customize the email using variables like Claim Number, Incident Date, Claimant Name, Examiner Name, and Reported By.

• Story: I10056

Inbox

• Documents in the Inbox can now be indexed to various entities beyond claims, such as Leave, UR, Vendor, and more, enhancing the robustness of the Document Management System.

• Story: I2448

• Selecting documents via the grid checkbox will only select the documents visible on the search result grid. 

• Story: I3948

• Send all treatments to UR when a new RFA is created by default

• Story: I4028

• Enhance document retrieval by supporting dynamic source locations

• Story: I3117

• The Claim Search button is replaced with a Search icon next to the Claim Number.
• Claim Associations can now be removed via the “Unidentified” icon next to the Claim Search icon.
• The “Bill Paid” button has been removed.
• The “Create Payment” button now redirects to the Payment screen, allowing you to create a new payment record. A memo linking the source document to the payment record will be created and saved as the payment record is saved.
• The “Create RFA” button opens a New RFA pop-up to record Physician and Treatment Information. The system will create a memo linking the source document to the treatment record, which is saved when the treatment record is saved.
• A ‘toggle’ icon is provided to Hide Keywords.
• Documents can now be downloaded via the “Download” icon.
• The History icon replaces the “History” button.
• The Key Dates and Instructions sections will remain collapsed by default.
• Document Status and Document Priority are added as fields in the Primary Keywords section, with configurable dropdown values.

• Story: I1213

• The "Document Inbox" dashboard has been relabeled to "Inbox" to better reflect its inclusivity. 
• Inbox searches can now be saved for future reference. The "Saved Searches" section on the screen displays all standard and custom searches saved by the user.

• Story: I4544

• Document Status dropdown values will be restricted by the value selected in the Document Type.

• Story: I6234

• A new "Assignment Status" dropdown has replaced the "Unassigned" checkbox, allowing users to select documents based on their assignment status: All, Assigned, or Unassigned.

• Story: I6761

• "Kind" has been replaced by "Category." Additionally, "Category" is now available as a search criterion in the Inbox and the Admin section for saved searches.

• Story: I6826

• When a user changes a folder, the document type field will be reset to blank.
• Document Priority has been added as a Document Type attribute, tied to the Document Type level (not mandatory), and it will update when the Document Type changes.

• Story: I7204

• A new "Inbox Queue" dropdown has been added to the Document screen.
• Inbox Queue is now available as a search filter in Saved Searches for both Admin and End users.
• If the claimant is an individual, the First Name and Last Name will be displayed. 
• If the claimant is a business, the Full Business Name will be displayed. 
• Inbox Queue has also been added as a column in the Inbox grid.

• Story: I6917 

• New validation rules have been implemented to ensure required fields are completed before saving or acknowledging documents

• Story: I7508

• Document Type on document viewer is now a smart search.

• Story: I5171

• Acknowledgement enhancements have been made to the Inbox screen. The key highlights include:

• Added "Unacknowledge" option: When an email or document is acknowledged, the button now toggles to "Unacknowledge" in both the Inbox and Document Viewer, allowing users to undo acknowledgement.
• Introduced an "Acknowledge" flag for Emails in the database to track acknowledgement status.
• Added "Unacknowledged Emails" widget in the standard To-Do List, similar to "Unacknowledged Documents," but specific to emails.
• Replaced browser alert with an in-application message confirming acknowledgement actions.

• Story: I9804

• Introduced a new QR code-based document separation functionality to automate splitting of large PDF/TIF files during document import. Three standard QR separator sheets are now available for download via System Administration > Document Inbox: Single Page Separator, Double Page Separator, Multi-Page Separator.

• Story: I8410

Occurrence Search

• Occurrence Search lets you search for existing occurrences in the system using basic and advanced filters.
• The screen also allows you to create new occurrences.
• Each Occurrence Number in the resulting grid is a hyperlink that, when clicked, opens a detailed view of the occurrence in a new tab.

• Story: I5220

• Added "Catastrophe" as a searchable field in the Occurrence Advanced Search, allowing users to filter Occurrences by Catastrophic events.

• Story: I10248

Quick Links

• A new Quick Links section has been added to the Dashboard/Landing Page left navigation. This allows users to access external systems, without being within a specific claim. Quick Links and their sub-items are configurable through the Administration section.

• Story: I10241

Reports

• Variable Mapping for items with minimum and maximum values will no longer create separate variables.
• The system will retain the PowerBI RDL file name for easier template identification.

• Story: I1879

• Access to buttons on the Reports screen can now be managed from User Security 

• Story: I4460

• Reports can now be successfully generated with the "All" option selected in multi-select dropdown filters.

• Story: I7122

• The grid columns can now be sorted and filtered. “Published” button is now relabeled as “My Reports” and “Unpublished” is relabeled as “Unpublished Templates”

• Story: I6701

To-Do List

• Enable sorting on all custom and non-custom To-Do List widgets for improved usability.
• Non-custom widgets now support up to 12 columns, providing a more comprehensive data view.
• Each column is filterable and sortable, allowing users to quickly find relevant data in the grid. 
• Horizontal scrolling ensures all necessary fields are accessible without clutter.

• Story: I6851

• Optimized how to-do list tasks are fetched and rendered. Users with large task queues now experience reduced lag and better interaction flow. The Klear team is still optimizing performance on the To-Do List. 

• Story: I9551

Vendor Management

• “1099”, “1099 Type”, “Do Not Pay”, “NPI”, and “License Number” fields are added to the Vendor Management and Vendor Details screen for the user to record the respective vendor details.
• A new “W9 Requests” accordion is added to the Vendor Management screen allowing the user to record “W9 Requested” and “W9 Received” dates. The grid in the accordion displays Vendor Description, W9 Requested, and W9 Received Dates.

• Story: I4330

• A new field, "Vendor Number", has been introduced to enhance vendor identification and tracking

• Story: #I9114

Vendor Details

• Selecting “Pending” as Vendor Status enables the “Pending Status Reason” dropdown to define a vendor’s pending status reason.

• Story: I3253

• New “Vendor Contacts” and “Sub-Vendor Contacts” accordions have been added to display associated contacts within their respective sections.

• Story: I6808

• Added a new "Doing Business As (DBA)" field on the Vendor Details screen.

• Story: #I9378

• A new Vendor Name 2 field has been added for vendors, displayed next to Vendor Name on the UI; vendor search now matches results by either Vendor Name or Vendor Name 2 across all applicable screens.

• Story: I10086

• A new flag, “Exclude from Bill Review”, has been added to the Vendor details screen to support more precise control over vendor eligibility for Medical Bill Review (MBR) processing.

• Story: #I9184

Vendor Search

• The Vendor Search and Vendor Lookup grids can now be configured to display vendors with "Pending Status" and "Do Not Pay" flags, alongside Active Vendors, with the Vendor Lookup grid also showing the "Pending Status Reason" to assist users in the vendor approval process.

• Story: I3253

• The Vendor Lookup on the Treatment and Attorney screen will only display vendors related to that screen.

• Story: I1895

Occurrence Management

The Occurrence Management Module by Klear.ai allows users to define occurrences, associate claims, and view associated claim details. It supports creating new occurrences and searching for existing ones and also to track contacts, communications, and financials at occurrence level.

Occurrence Details

• The Occurrence Details screen provides users with the ability to review and edit the details of an existing occurrence. Additionally, users can assign new individuals to an occurrence and designate primary users.

• Story: I5221

Associated Claims

• The Associated Claims screen within an Occurrence is mostly read-only, with editable CT Start Date and CT End Date fields. It displays details of claims associated with the Occurrence. Users can associate new claims, unassign existing ones, and designate the Master Claim. The grid also allows users to set the Contribution Percent for Continuous Trauma claims.

• Story: I5225

Contacts

• The Contact screen within an Occurrence allows users to add, delete, or update contact details at the occurrence level. It also enables viewing contacts associated with claims linked to the Occurrence.

• Story: I5229

Financials

• "Financials" is a left navigation action item within an Occurrence. The Financials screen features a filterable, sortable grid displaying associated claim numbers, policy details, and financial for associated claims within the Occurrence.

• Story: I5228

Communication

• The Communication screen within an Occurrence allows users to add new communications and view communications for claims linked to the Occurrence.

• Story: I5226

• For catastrophes or incidents with multiple associated claims, letters now support variable mapping and integrate information from various claims.

• Story: I3002

Client Defined Field

• Custom fields for the Occurrence Module can now be configured in the Client Defined Fields screen within the Administration section and will be displayed in the Occurrence's Client Defined Fields screen.

• Story: I5231

User Security

External User Management 

Klear.ai introduced the new External User Management screen within the User Security module, allowing authorized users to efficiently manage external access to DataBridge and the Claimant App.

Key Features of the External User Management screen includes:

• User Search: Quickly find users using basic and advanced search filters.
• Activation/Deactivation: Enable or disable DataBridge and Claimant App access for selected users.
• User Deletion: Remove users and restrict their access to both applications.
• DataBridge Management: Control external user permissions for Form Groups by enabling or disabling access.
• Claimant App Management: Manage access to specific cards within the Claimant App by adjusting individual permissions.
• This feature enhances flexibility and control over external user access to key applications.

• Story: I3320

Role Management

• Admin users can now set the "Reserve Type Limit" and "Reserve Total Per Claim Limit" at both the User and Role levels. The "Reserve Type Limit" defines authority over each reserve bucket, while the "Reserve Total Per Claim Limit" governs authority to create or approve reserves at the claim level.

• Story: I3072

• Confidentiality settings can now be configured at the role level. The system will prioritize user-level settings, defaulting to system-level settings if no user-level configurations are specified.

• Story: I6856

User Management

• Fields can now be relabeled and set as “Required” at the user level for various WC and GL Claim screens, including Claim Intake, Assignment & Adjudication, Injury, Treatment, Litigation, Settlement, and more.

• Story: I5031, I5034, I5035, I4768

• A new 'Data Security Profile' column has been added to the User Security grid.

• Story: I9679

Communication Security

• User access to communications within claims is now controlled through Communication Security permissions. Selecting a specific Communication Type within a Communication Group grants access only to that type, while selecting the Communication Group grants access to all communication types within it.

• Story: I4368

Inbox

• A “Delete” button is added allowing the Admin user to delete the admin saved search. Deleting an admin saved search will delete it from all the assigned users. 

• Story: I6899

User Details

• SSO Authentication integrated enabling users to authenticate their organization’s central authentication services.

• Story: I2020

• When the Inactive box is unchecked in the user details section, the user expiry date will be cleared automatically, ensuring that the user can log in without encountering any issues related to expired access. 

• Story: I6816

• “Email Signature” field is added to User Details for users to upload their email signature which can be used when sending an outbound email.

• Story: I7022

• Expanded admin privileges to manage field-level behavior for General Liability (GL) and Vendor Management screens, aligning them with existing Workers’ Comp (WC) configurations. 

• Story: I6700 

Report Template

• Report Security Needs to work at Template Level

• Story: I7579

Template Management 

• The “Organization” field on the Claim Search and Employee Search screens, within a template, is now multi-select dropdown.

• Story: I7445