Helipass Users - Email Validation & Login Security Enhancements
Helipass is in the middle of a major, multi‑phase security initiative to modernize and strengthen the login process. As part of our transition toward Microsoft Entra authentication, the team has introduced new requirements ensuring all users have a validated email address tied to their Helipass account. This foundational step is crucial for the long‑term move away from usernames and toward email‑based login. To support this, several backend and UI updates were released that improve how email addresses are managed and verified within the system.

What's New?

• Users without a previously validated email are now required to verify their email before gaining access.
• A verification workflow has been added to allow users to resend a validation code or update their email if they no longer have access to the old one.
• Preparations are underway for a future update where only one Helipass account per email will be allowed, with duplicates deactivated.
• These changes are foundational steps toward replacing username/password login with email address + password authentication.

Why It Matters?

This security enhancement greatly improves account integrity and prepares the system for modern authentication standards. Ensuring every user has a validated email protects against unauthorized access, simplifies account recovery, and makes it easier to integrate with enterprise identity platforms like Microsoft Entra. By consolidating accounts around a single email identity, tenants will experience more secure logins, fewer duplicate accounts, and improved support workflows.

These updates set the groundwork for a much more secure and modern login experience. Users should expect additional authentication improvements as Helipass continues the transition toward industry-standard identity management.

____________________________________________________________________________________________

Helipass Users - Platform Upgrade to .NET 10
To ensure Helipass remains secure, fast, and aligned with the latest web technology standards, the team completed a major upgrade to .NET 10. This upgrade was a large behind‑the‑scenes effort requiring updates across multiple components of the platform. Although these improvements are mostly invisible to end users, this work was essential to maintain platform stability and long‑term support.

What's New?

• Core backend services upgraded to .NET 10.
• System libraries and dependencies updated to match modern standards.
• Performance and security optimizations applied where relevant.

Why It Matters?

Keeping Helipass current with major framework releases is critical for long‑term reliability. This upgrade ensures ongoing support from Microsoft, strengthens security, and provides improved performance foundations for future features. It also opens the door for more efficient development, allowing the team to continue innovating without technical constraints.

While this update does not introduce new UI features, it plays a vital role in keeping Helipass secure and future‑ready. Users benefit from a more stable and scale-able system designed to support upcoming enhancements.

____________________________________________________________________________________________

Travel Portal Users - New Travel Portal and Travel Management Features
The Helipass team has made significant progress in building out the brand‑new Travel Portal, a major enhancement designed to modernize how travel requests are submitted, processed, and managed. This improvement includes an entirely new passenger-facing experience and a robust administrative interface for travel coordinators. Over the last several months, major milestones have been reached, bringing the portal close to release for Travel Management subscribers.

What's New?

Passenger Portal:

• Passengers can log in through a browser and manage their own travel needs.
• Travelers can view their profiles across all subscribing tenants.
• Users can request new travel, update existing plans, and view compliance details.

Travel Team Admin Portal:

• A new management area for reviewing and processing travel requests.
• Tools to update request details, communicate with passengers, and make adjustments.
• Ability to create trips directly from approved travel requests.
• Significant UI and workflow improvements to streamline travel management.

Why It Matters?

This represents a major expansion of Helipass’ capabilities beyond manifesting and POB tracking. The Travel Portal modernizes how travel is managed, increases transparency for passengers, and significantly reduces manual work for travel coordinators. Passengers gain a self‑service experience similar to consumer travel platforms, while travel teams benefit from centralized request handling and simplified trip creation. This will ultimately lead to fewer errors, faster processing, and a more cohesive ecosystem for managing travel operations.

Most of the Travel Portal’s core functionality is nearing completion, with ongoing refinements planned as the launch approaches. This update marks one of Helipass’s largest user‑experience enhancements to date and will play a major role in improving the future of travel management across the platform.

____________________________________________________________________________________________

Travel Management Users - Enhanced Date Range Option for Arriving and Departing Travel Request
Travel management teams rely heavily on the Travel Request page to monitor incoming and outgoing passengers across their operations. Previously, users could only export arriving or departing passengers one day at a time, making it cumbersome to generate comprehensive views of upcoming travel activity. This limitation was especially challenging for teams managing high volumes of travelers or coordinating multi-day travel windows.

What's New?

• Travel Request exports now support custom multi‑day date ranges, not just single days.
• Users can generate broader datasets for arrivals and departures in a single export.
• Export tools were redesigned to provide more flexibility for planning and reporting.

Why It Matters?

This enhancement dramatically improves visibility for teams planning travel logistics. Instead of downloading multiple single‑day reports and manually stitching them together, users can now view all relevant arrivals and departures in one streamlined export. This saves time, reduces operational friction, and makes it far easier to manage complex travel schedules.

Travel management teams can now take advantage of more robust export capabilities, making trip planning and oversight far more efficient than before.

____________________________________________________________________________________________

____________________________________________________________________________________________

Helipass Users - Incorrect Days On Board being Calculated on Personnel Page and Passenger Profile
A passenger’s “days on board” calculation is an important metric displayed on their personnel tile and profile. After the UTC conversion updates, some passengers incorrectly displayed an extra day on board (or one fewer) when their arrival or departure time crossed over into the next day after conversion. This caused inaccurate POB tracking and confusion when reviewing personnel history.

What was Happening?

• UTC conversion shifted some arrival/departure timestamps to the next day.
• The system incorrectly counted these UTC-shifted dates instead of using the Worksite’s local time zone.

What was Fixed?

• The day count now uses the location’s configured time zone, ensuring accurate POB tracking.

Personnel profiles now show correct day counts regardless of UTC offsets, giving Worksite teams confidence in their POB data.

____________________________________________________________________________________________

Worksite Users - Passengers Not Displaying in the Arrival Presets Area After Prior Day Departure
Worksite users depend on the Arrival Presets area to assign bunks and mustering details to passengers arriving the next day. However, in the Australia region, some passengers who departed in the afternoon and returned the following morning were not appearing in the Arrival Presets list. This issue stemmed from UTC conversions causing the system to treat both events as if they happened on the same calendar day.

What was Happening?

• Late afternoon departures and early next‑day arrivals were both seen as occurring on the same day due to UTC shifts.
• Passengers did not appear in Arrival Presets even though they were arriving again.

What was Fixed?

• Arrival Presets now respects the Worksite’s local time zone, correctly distinguishing between calendar days.

Passengers will once again appear in Arrival Presets whenever their arrival truly falls on a different local day than their prior departure, ensuring accurate assignment workflows for offshore teams.

____________________________________________________________________________________________

Helipass Users - Page and Report Crashes Following .NET 10 Migration
Following the system-wide upgrade to .NET 10, several users began reporting unexpected crashes when loading certain Helipass pages or generating reports containing large amounts of data. Though these same pages and reports had previously worked without issue, the updated .NET 10 framework introduced a new and previously unknown data-size limitation. This created disruptions in areas that commonly handle heavy datasets, impacting users who depend on these views for planning and operational oversight.

What was Happening?

• Large datasets triggered crashes on pages such as Schedule View and the Schedule Gantt.
• Reports using wide date ranges (e.g., Waiver page, Check‑In History) failed to load or export.
• Trip Summary reports generated from the Manifest page were failing more frequently than before.

What was Fixed?

• The Helipass team identified and resolved the majority of data‑related issues across affected pages and reports.
• Additional improvements were made to reduce the risk of memory overloads caused by large filters or complex report structures.
• Work is ongoing to fully resolve export limitations on Trip Summary PDFs and CSVs, which still face size-related restrictions.

Most reports and pages are now functioning normally again, restoring reliability for users who work with large datasets and wide date ranges. The Helipass development team will continue to monitor performance and address remaining limitations to ensure the .NET 10 platform runs smoothly across all areas of the system.

____________________________________________________________________________________________

Kiosk Users - Kiosk Freezing when Canceling Fingerprint Scan
Fingerprint scanning is a secure check-in method offered across various tenant kiosks. However, some users encountered a critical issue: when a passenger selected the fingerprint option and then hit Cancel, the kiosk would freeze entirely. This required a full restart of the kiosk before passengers could continue checking in — causing delays, dissatisfaction, and added workload for kiosk attendants.

What was Happening?

• Pressing “Cancel” during fingerprint scanning caused the kiosk to lock up.
• A reboot was required before the kiosk could process another passenger.
• This created bottlenecks during peak check-in times.

What was Fixed?

• The kiosk code was updated to properly handle the Cancel action.
• Passengers who cancel fingerprint scanning are now properly taken back to the check‑in method selection screen.
• No reboot or manual intervention is needed.

This fix restores a smooth, predictable check‑in experience for passengers and kiosk teams. The fingerprint workflow now behaves as intended, preventing unnecessary downtime and keeping the line moving efficiently.

____________________________________________________________________________________________

Mobile App Users - Mobile App Users Unable to Verify Email Addresses
As part of Helipass’ ongoing authentication and security enhancements, mobile app users are increasingly being asked to verify or update the email addresses tied to their accounts. However, several users recently reported issues when attempting to add a new email or resend a verification link from within the app. Instead of completing the action, the system returned an error, leaving users unable to validate their accounts or modify outdated email addresses. This created significant friction, especially for passengers who rely on mobile notifications or who needed to correct invalid profile information.

What was Happening?

• Attempts to add a new email resulted in an error and no email being saved.
• Resending the verification email also failed, with no verification link being delivered.
• Users were unable to complete required email validation steps.

What was Fixed?

• The team identified and corrected an issue in the verification workflow affecting mobile app users.
• Email updates and verification requests now process correctly without errors.
• Users can once again validate or update their email addresses through the app and website.

With this fix in place, mobile app users can smoothly update and verify their account emails—an important step for future login improvements and system security initiatives. This ensures passengers stay connected, receive important notifications, and maintain accurate profile information without interruption.

____________________________________________________________________________________________