The following lists the updates which have been included in the May 2025 Borealis release.

Note: The Site Calendar, Site Lock/Site Unlock and Operator Audit features are no longer controlled by a feature flag. These new features will now be enabled by default for all new systems.

New Features

Single Active Credential Per Cardholder

Borealis now has a system-wide feature that allows you to enforce a 'one-active credential policy' so that a cardholder can still have multiple assigned credentials but only one of the credentials can be active at a given time.

Note: This setting cannot be enable while there are existing cardholders in the system with
multiple active credentials.

Doors32 to Borealis Conversions

We are in the final stages of testing and verifying the ability to convert Doors32 PXL/Entraguard systems to Borealis. Keri Systems will be able to directly convert a Doors32 system to Borealis and the conversion will include all cardholders - including cardholder access rights, PXL and Entraguard controller and reader information and settings, plus holidays and time schedules.

Multiple Doors32 sites can optionally be imported into separate sites or separate systems in Borealis. This is scheduled to be available in early-mid June 2025.

Bug Fixes and User Interface Improvements

• Corrected one of the Message Type descriptions in live events to display Site Lock/Unlock instead of Global Lock/Unlock.
• Prevented the operator from changing an assigned auto-unlock schedule while Site Lock/Unlock is active. An auto-unlock change is now only permitted when the site status is Normal.
• Implemented a fix that prevents an invalid Entraguard credential from being enrolled by
  disabling the Save button until the required number of digits has been entered.
• Corrected an issue with systems that use multiple hubs where the subscription could show as inactive even though the initial cloud subscription had been paid.
• Enforced identical Entraguard PIN and Directory Code settings for systems with multiple sites - both using Entraguard controllers. The number of digits for Directory Code and Entraguard PINs must be the same for all sites.
• Prevented an operator from decreasing the # of Entraguard PIN digits in site settings to a lesser value. For a single-site system with existing Entraguard credentials the # of PIN digits can only be increased, not decreased.
• Prevented an operator from mass-editing access rights for multiple Entraguard credentials.
• Implemented the option to allow an operator to manually enroll a specific Entraguard ID instead of a randomly generated one. When saving the manually-entered credential, a check will be performed to prevent an existing Entraguard ID from being duplicated.
• Corrected an error that was generated after modifying an existing Entraguard credential's assigned access rights.
• Corrected a display issue after enabling Advanced Permission. The feature was showing as Enabled before the feature had been paid for.
• Added a tool-tip to elevator reader settings to explain the use of Elevator Override Schedules.
• Corrected an issue where the
• Corrected an issue where the Site Lock/Unlock status was not displayed correctly when triggered from a hardware input/monitor point.
• Corrected a cardholder filtering issue in transaction reports when transaction results would not be returned after entering a cardholder's full name.

P/N: 02426-001 Rev L