Helipass Users - Login Security Enhancements & Microsoft Entra Transition
Helipass continues to make progress toward a more secure and modern login experience through its transition to Microsoft Entra. In last month’s newsletter, users were informed of new email verification requirements to ensure every account has a validated, accessible email address. This month, additional security-focused updates were released to further prepare the system for the upcoming switch away from username-based logins. As part of this effort, Helipass is now enforcing a single user profile per unique email address. Accounts that shared the same primary email were reviewed, and older or inactive profiles were deactivated to remove duplicates and reduce security risk.

What's new?

• Accounts sharing the same email address were deactivated based on last login activity.
• The most recently used account remained active; older duplicates were deactivated.
• Users can contact Helipass Support to reactivate a deactivated account if needed.

Why it matters?

These changes significantly strengthen account security and simplify identity management. Enforcing one account per email reduces confusion, improves auditing, and prepares the system for modern authentication standards. Moving to email-based login aligns Helipass with industry best practices and improves compatibility with enterprise identity providers like Microsoft Entra.

What is next?

A transition period will begin where users can sign in using either their Username + Password, or Email Address + Password. During this transitional period, users can login using their current username and they will be provided their accounts email address to be used for signing in in the future. During this period, users are encouraged to update their email addresses if necessary.

Over the coming weeks, usernames will be fully phased out and users will sign in exclusively with their email address and password. These updates ensure a smoother, safer transition to Helipass’ next-generation authentication model.

____________________________________________________________________________________________

Manifest Users - Enhanced First Time Flyer (FTF) Tracking & Management
Helipass has introduced major improvements to how First Time Flyers (FTFs) are tracked and managed across the platform. Previously, FTF designation was based solely on whether a passenger had appeared on a manifested trip before, which did not account for incomplete trips, non‑rotor wing travel, or tenant‑specific safety requirements. With the latest updates, tenants who choose to track FTFs now have significantly more control and flexibility in how this status is defined and enforced.

What's new?

• Tenants can configure how many completed trips are required before a passenger is no longer considered an FTF.
• Only rotor‑wing trips marked as departed or complete count toward completed trips.
• FTF status can be viewed and updated from the Miscellaneous tab of a passenger’s Personnel Profile.
• Optional evaluation requirements can be enforced before removing FTF status.
• FTF indicators are now shown on the Trip Plan page, Printed manifest, and Boarding passes.

Why it matters?

First Time Flyers often require additional oversight, training, or evaluation. These updates give tenants better tools to align Helipass with their operational and safety policies, ensuring that FTFs are clearly identified at every stage of travel. This improves situational awareness for base teams, flight crews, and offshore personnel alike.

With expanded configuration options and clearer visibility, tenants tracking First Time Flyers now have a more accurate, reliable, and customizable system for managing passenger readiness.

____________________________________________________________________________________________

Travel Portal Users - Travel Portal Management - Approvals & Manifest Integration
The Travel Portal Management project continues to evolve, bringing Helipass closer to a fully integrated travel request and planning experience. This phase of updates focuses on strengthening approval workflows, improving travel team efficiency, and expanding passenger self‑service capabilities through the web portal.

What's new?

• Tenants can now configure approval workflows for submitted travel requests.
• Approved Travel Requests can be added directly to trip manifests from the Left Planning Panel.
• Travel teams can manage requests, approvals, and trip creation from the new Travel Portal area.
• Passengers can log in via a web browser to view upcoming and historical trips, submit and manage travel requests, and see travel information tied to other  tenant profiles.

Why it matters?

These updates reduce manual work and improve communication between passengers and travel teams. Travel coordinators gain a centralized workflow for approvals and manifesting, while passengers benefit from increased visibility and self‑service access. Over time, this will create a more connected travel ecosystem across tenants and regions.

As development continues, the Travel Portal is quickly becoming a powerful hub for managing travel requests, approvals, and passenger engagement across Helipass.

____________________________________________________________________________________________

TWIC Checks - TWIC Card Database Integration & Reporting
TWIC cards are federally issued credentials required for access to certain vessels and facilities. While Helipass has long supported TWIC card scanning at kiosks, the system previously relied only on expiration dates — meaning revoked cards could still be used if they had not technically expired. With this update, Helipass introduces an optional TWIC database integration that verifies card status directly against the official TWIC records.

What's new?

• TWIC cards can now be validated against the national TWIC database.
• Passengers with revoked or inactive cards are flagged as non‑compliant.
• Tenants can opt into this integration based on their compliance needs.
• A new TWIC report is available in the Custom Reporting area to identify issues.

Why it matters?

This integration provides a much higher level of compliance assurance. Tenants can prevent revoked TWIC holders from checking in or traveling, reducing regulatory risk and improving safety. Automated validation also removes the need for manual checks and outdated assumptions.

With real‑time TWIC verification and reporting, Helipass now offers a more reliable and proactive approach to managing federally required credentials.

____________________________________________________________________________________________

Worksite Users - Mass Editing of Arrival Presets Not Working
The Arrival Presets section on the Worksite page allows users to efficiently manage assignments for future arriving passengers. One of its most valuable tools is the ability to select multiple passengers and apply changes in bulk. Recently, users reported that this mass edit functionality was no longer working, preventing updates from being saved and forcing users to make changes one passenger at a time.

What was happening?

• The mass edit modal would open correctly, but changes were not being saved.
• Users had no indication that the update failed until returning to the list.

What was fixed?

• The edit modal logic was corrected to ensure bulk updates save successfully.
• Mass edits now apply correctly across all selected passengers.

Worksite users can once again rely on mass editing in Arrival Presets to quickly assign bunks, lifeboats, and other details—restoring a major time‑saving workflow.

____________________________________________________________________________________________

Worksite Users - POB Passengers Disappearing Due to Arrival Date Being Deleted
Arrival Dates are a critical part of a passenger’s POB record, defining when a person is officially on board a facility. A rare issue allowed POB passengers to have their Arrival Date removed, placing their record into an invalid state. When this occurred, the passenger disappeared from the POB list while still remaining associated with the location in the database.

What was happening?

• Arrival Dates could be removed from POB records through a missed workflow path.
• Passengers would disappear from the POB list but remain flagged as on location without a start date.

What was fixed?

• The remaining gap allowing Arrival Dates to be removed was identified and closed.
• POB passengers can no longer exist without a valid Arrival Date.

This fix protects data integrity across the Worksite page, ensuring all POB records remain complete, visible, and accurate.

____________________________________________________________________________________________

Position Competency Users - Incorrect Date Format for Position Competency Records
Tenants can configure Helipass to display dates using either MM/DD/YYYY or DD/MM/YYYY formats. Users reported that while adding position competencies initially showed dates correctly, those same dates were displayed in the wrong format after saving. This mismatch caused confusion for tenants using the DD/MM/YYYY standard.

What was happening?

• Competency dates initially displayed correctly during entry.
• After saving, dates reverted to MM/DD/YYYY regardless of tenant settings.

What was fixed?

• Date formatting logic was corrected to consistently respect tenant date preferences.
• Position competency dates now display correctly at all times.

Competency records now display dates consistently and correctly, reducing confusion and ensuring alignment with tenant‑specific regional standards.

____________________________________________________________________________________________

Cargo Approver Users - Cargo Updates Blocked when Approval Workflow Enabled
Tenants using the Cargo Approval workflow reported issues when attempting to update cargo reservation statuses on the manifest. In certain configurations, cargo items could not be checked in or added to a manifest—even after meeting approval and check‑in requirements—causing confusion and blocking normal operations.

What was happening?

• Cargo statuses could not be updated to Checked In without re‑approval.
• Requested cargo that had already been checked in could not be added to the manifest if certain settings were enabled.

What was fixed?

• Cargo statuses can now be updated without triggering unnecessary re‑approval.
• Properly checked‑in cargo items can be added to the manifest through the Checked In Cargo field, even when approval workflows are enforced.

This fix restores flexibility and clarity to cargo workflows, ensuring approval rules are enforced correctly without blocking valid operational actions.