February 2026 Release Notes

Release 2/10/2026

Enhanced

• Client Side - User Tracking: This ticket implemented updates to the User Tracking feature to log and report all CRUD capabilities on the Client Side.
• Location Template List Page - Delete Template: The release ticket outlines enhancements to the Location Template Management feature. Users can now delete closed templates that are not linked to any locations, with the Action column providing a link for deletion when applicable. The delete option is hidden for linked templates, and only Compliance Admins can perform deletions, which require a confirmation prompt. Additionally, a soft delete mechanism has been implemented, allowing for restoration of deleted templates, and user activity is tracked on the page.
• Bulk Assigning a Template to Multiple Locations: The new feature allows users to bulk assign or un-assign a Template to multiple Locations from the Location Template list, accessible only to those with Compliance Admin or Implementation roles. An Action column link facilitates the assignment process, which opens a modal showing currently assigned Locations. Users can de-select Locations to disassociate them and can choose additional Locations through a filtering system based on Company, Regulator, or State. The assignment process updates Template Associations by removing de-selected Locations and adding new ones, with all user activities tracked for auditing purposes.
• Bulk Re-assigning a Template to Locations: The ticket introduced a new feature allowing users to bulk re-assign a Template to multiple Locations from the Location Template list. A link to re-assign the Template appears in the Action column, but only if the Template is currently assigned to one or more Locations. This action is restricted to users with Compliance Admin or Implementation roles, who will be prompted to select a Replacement Template via a modal. Additionally, a table displays all Locations associated with the Current Template for user reference, and the re-assignment process updates the Template Associations while logging user activity for actions taken on the page.
• Assign Admin Restrictions by Default when Creating a Kipu Admin: New logic introduced when creating Kipu Compliance Admins to enhance security by assigning User Restrictions by default. When a Kipu Compliance Admin is enabled, they will automatically have access limited to Companies & Locations and Users, while additional access to Billing Data, Location Compliance Settings, and Location Templates must be configured manually. Users seeking full system access will need to manually remove the default restrictions. Future User Restrictions will be unassigned by default unless specified otherwise, ensuring that the default settings are applied during the creation of new Kipu Admins without affecting existing assignments.
• Enhance KCOM to Support Multiple EMR Account IDs per Location & Provide Atlas APIs: The Kipu Compliance (KCOM) data model is set to be extended to support the upcoming Atlas integration, with several key enhancements being implemented. Firstly, the data model will now allow multiple EMR Account IDs for each KCOM location instance. Additionally, the existing Atlas API will be updated to provide detailed company and location information in JSON format, including various fields such as address and level of care, along with new EMR Account IDs. Lastly, a new API endpoint will be introduced to list or count active users per company, excluding system and KCOM admin users. These updates are crucial for fulfilling integration requirements with Atlas.

Fixed

• Administration Office - Revert Function Produces HTTP 500 Error When Restoring Earlier Form Version: This update addresses a significant bug in the HR document reversion process that led to a 500 error due to un-serialization issues, which posed a risk of data corruption in revisions. Testing indicated that some documents had corrupted or truncated revisions, affecting version control. A command was executed to identify and rectify the affected records, confirming that correcting byte mismatches restored reversion for certain revisions. The root causes identified include missing and truncated data, with proposed solutions focusing on updating GEDMO preview logic, normalizing data storage, and implementing validation measures to reduce future data loss. Ongoing testing is being conducted in both QA and production environments.
• Client Side - Compliance Consultant - Cannot Impersonate: Addressed an issue reported by a Compliance Consultant, who experienced a 403 Error when attempting to impersonate users. The root cause was identified as an incorrect reading of location context in the impersonation authorization, which has been resolved by updating the method to use Symfony's route parameters.
• Client Side - Impersonation - Users Configured as Consultants get Error Code when Impersonating: Resolved an error that occurred when users configured as Consultants attempted to impersonate another user. Consultants with the Human Resources role can now impersonate users at the locations they are assigned to without seeing an error.
• Admin Office - HR Docs - Force Log Out: Resolved an issue where a pop-up message disrupts the creation of the employee handbook, causing unexpected logouts and loss of work. Users experience this problem while adding data in the Employee Handbook Table of Contents. The issue is not replicable in the test location but has occurred twice in the Admin Office. To address this, a solution has been implemented where user activity will now trigger a session check every five minutes of inactivity, preventing session expiration during long editing sessions.
• Admin Office - HR Documents Tab Not Appearing: This ticket resolves an issue where the HR Docs tab is not displayed for some locations, despite being active. This problem arose after the re-enabling of some HR Docs during implementation, with no workarounds available. The root cause was identified as checkboxes not functioning correctly, which has been addressed by updating the fields to the proper Checkbox Type, ensuring accurate display in the UI. 
• Training Center - Employee Summary - Duplicate Filters: Addressed an issue where using 'ctrl-p' to print or save a PDF of the 'Training Center: Employee Summary' results in duplicated status filters on the page. The root cause is identified in the buildDataTable() function, which improperly clones the filter row, and a solution was implemented to remove existing filter rows before cloning a new one, ensuring only one filter row displays in the table header.
• Client Side - View Charts - 500 Error Code: Resolved a 500 error that occurred when opening View Charts on forms, HR documents, and competencies. The View Charts page now loads as expected and displays the underlying chart data.
• Move Assign Trainings to Locations Back to Locations List: Addressed an issue where Kipu Admins could not bulk assign training to multiple locations due to the feature being incorrectly tagged to the feature flag for Location Templates. The "Assign Trainings to Locations" action is currently blocked, and the associated modal is no longer accessible. This ticket resolves linking the modal to the Location List feature. The root cause was identified as duplicate functionality in the Location Templates code, which has now been resolved by removing the blocking code.
• BHT - Cross viewable Access - Competencies - Despite Company Admin Permissions: Resolved an issue where users in a non-admin role could view competencies belonging to other users despite not having cross-view permissions. Competency visibility now correctly respects the configured role permissions.
• Anonymous User - Cross viewable Access - Grievances (and other forms that allow Anonymous creation): Resolved a security issue where users without the 'grievance officer role' can view grievances submitted by anonymous users. The root cause was identified in the findUserOrAnonymousAnswers method, which improperly allowed access to anonymous entries without proper permission checks. The solution involved modifying this method to restrict access to anonymous entries only for specific roles and removing a fallback that bypassed permissions.

Release 2/17/2026

Enhanced

• Location Compliance Settings User Tracking Problem: An update has been implemented in the User Tracking system of Location Compliance Settings to improve clarity. Previously, all regulations were logged when users made changes, which caused confusion; the new system now only logs the specific regulations that were added or removed. Users will find a clear distinction between added and removed regulations, enhancing their understanding of changes made. The update addresses a root cause identified in the code, ensuring that only the relevant changes are tracked without affecting existing functionalities. Overall, this enhancement aims to provide a better user experience in managing compliance settings.
• Allow Customers to Export a List of Their Users: Enhanced the Company Admin > Users that allows Company Admin users to generate a CSV export of the users across their Locations.

Fixed

• Dashboard - Compliance To Do's: "For Others" appears: Fixed an issue where marking a Compliance To Do item as "Not For Me" would not persist after navigating away from the dashboard or refreshing the page. Items now correctly remain in the "For Others" tab once reassigned. Additionally, the To Dos widget UI has been streamlined for clarity - the requirement type (e.g., recurring, date of hire) now displays as a label rather than an icon, making the "Not For Me" action easier to identify and use.
• Fix Data Tables on Form Cat Page (Sign In: Error Message Received): Fixed an issue where some users could encounter an error message when navigating to a form category page that contained no records. The error did not block system access but could cause confusion. This has been resolved and the page now loads cleanly regardless of whether records are present.
• Company Admin: Notifications: Inactive Form and Notifications populating: This ticket resolves an issue where notifications for the inactive override form “Incident Reports Duplicate 76” appeared in the Company Admin. The portal should show notifications only for active forms. The root cause was a notification index template that didn't check the forms' active status. A check for form activity status was added in the template, ensuring notifications for inactive or soft-deleted forms are filtered out.
• Administration Office - Notifications - When "Is Employee Secondary Sign Off" is Checked, Creator is Not Being Notified: This ticket resolves a bug in the Disciplinary Action Form workflow where the document creator does not receive notifications upon the completion of secondary sign-off by the assigned employee when "Is Employee Secondary Sign Off" is checked. To address this, a fix was implemented that when the document status changes from Awaiting Approval to Completed, the document creator should automatically receive a notification. 
• Email Communication - Reset Password: This ticket resolves and issue where users were not receiving the reset password emails. This fix implements a solution both to ensuring that users receive the reset password email, as well as logs those emails in the User Profile Communication Log.
• Department Manager - Permissions Review: Resolved a problem where BHT supervisors with multiple roles received an "Unauthorized Access" error when trying to edit user profiles for their team members. The issue was due to missing permissions in certain areas of the system. To fix this, we added a new method that allows Department Managers to access and edit user profiles for users they manage. 
• Task Issue Not Properly Sending Notification to User Assigned to: This ticket addresses a notification issue reported where users were not receiving alerts for assigned tasks and encountered a 500 error when reviewing communications. The resolution involved fixing a bug that affected task alerts where dt_to_alert was set incorrectly. Correctly setting this value ensuring that notifications are now visible immediately after tasks are created or completed. 
• 500 Error Prevents Viewing Location Compliance Score History: Addressed an application error preventing access to the Location Compliance Score History, resulting in an HTTP 500 error due to a permissions mismatch. This issue was first identified in a recovery location and confirmed through testing. Root cause analysis revealed serialization and legacy data issues affecting historical compliance records, which have been addressed with data restoration improvements. 
• Username - Updated/Changed: Completed a data fix to a username that was inadvertently edited and implemented a fix to prevent this for occurring again. While the username field is read only, there was a specific workflow that opened this field to edit by users. This has been resolved to prevent edits to this field by any means. 

Release 2/24/2026

Fixed

• Location Compliance Report - Inaccurate Compliance Score: Resolved an issue where the Location Compliance Report (LCR) inaccurately displays a compliance score, despite all forms being completed. The report should reflect a 100% compliance status when all forms are Compliant, as the Upcoming Requirements do not affect the LCR score. A root cause analysis revealed that shift-aware forms were initialized with a score of 0, which has now been corrected by implementing a new method to ensure accurate scoring. This update allows completed shift-aware forms to contribute correctly to the total compliance score.
• Notifications: 30 Day Expiration: Resolved a notification issue affecting users who received incorrect alerts about their CEU Tracker expiring within 30 days despite compliance. The problem arose from a Notification Service method, which generated alerts without correctly setting the expiration date. To resolve this, a tracking variable was added to ensure accurate expiration dates for user alerts, and adjustments were made in the Notification Service. This update improves user experience by ensuring alerts accurately reflect CEU compliance status.
• Competency Settings - Competency Manager: Resolved an issue where certain roles could access and input data on operational manager competencies without proper authorization, leading to confusion and errors in the system. Users can create and save competencies, but the system fails to recognize these actions. To address this, authorization checks have been adjusted to occur before form creation, preventing unauthorized access and improving user experience.
• Error when Filtering Answer Index Page: Resolved an error in the filtering logic when attempting to view a HR Document Answer List Page. The root cause analysis identifies the fundamental issue as the query's return type, which leads to the malfunction in the filter logic.
• User Compliance Report - HTTP Status Code 500: Resolved an issue where users experienced a HTTP 500 error when opening and editing PSV forms. This was caused by configuration that changed a field from single to multi-select with required dependencies caused data evaluation mismatch. The fix wraps legacy string values into arrays before evaluation, preserving data and restoring function. 
• User Activity - User Showing Access Manager View on Themselves: Resolved issues with the User Activity log, where users saw incorrect entries indicating they viewed their own profile and encountered "Unhandled User Activity" messages. The root cause was linked to auto-populated parameters logging every page visit inaccurately, and a debug-style error message was displayed for unhandled activities. Solutions include adjusting the logging mechanism to only record meaningful actions and improving error messaging to provide clearer notifications.