Leon 216 released

We have recently initiated the deployment of a new version of Leon. Over the next coming days, customers will gradually transition to the updated version. If you encounter any functions that are not working as expected, please notify us via the Customer Portal.

Important Notices

• Starting July 1st, anonymous ticket submissions will no longer be supported in the Customer Portal. All users will be required to log in before submitting a support request. If you haven't registered yet, please create an account at Customer Portal.
  
  

Airport Directory

• We expanded the Recency configuration in Airport Directory with the option to specify validity in days - previously only months were available. This is particularly useful for airports that require qualification refreshes every few days.
• We added an option to lock airport category changes in Airport Directory. An administrator can now mark a category as read-only, preventing users from changing it through the interface.

Crew

• We added an indicator in Crew Calendar and Crew Timeline showing unpublished duties in draft mode. The indicator appears next to the PUBLISH button - planners can immediately see that there are pending changes in the current draft waiting to be published.
• The first version of the Pairings-based Crew Timeline is now available on request. If you would like early access, please reach out to our support team.

Crew Training

• We added crew member certificate validation when assigning a duty linked to a specific aircraft type. If the crew member does not have the required certificates for the selected aircraft, the system will display a warning. This allows qualification gaps to be caught at the duty planning stage, before they become an operational issue.

OPS

• We added new de-icing fields to Journey Log: the ability to select the type of fluid used (Type I, Type II, Type III, Type IV, Hot Water, Hot Air) and to enter the application time. This enables more accurate recording of de-icing operations directly in JL - benefiting both compliance and reporting.
• We introduced an option to display ARCID instead of the flight number on the flight bar in OPS Timeline. The toggle is available from the three-dot menu - for operators who primarily use the ARCID identifier in operational communication.
• We improved FTL Details editing in the OPS view on the crew panel. We unified the logic for displaying statuses and messages across sectors - FTL data is now presented consistently regardless of which sector is being viewed.
• We expanded the filtering options in Report Wizard with new filters for Journey Log columns. This allows for more precise narrowing of reports built on JL data.
• We changed how Shared reports in Report Wizard are stored and displayed. Shared reports are now retrieved directly from the common database instead of being copied to each operator separately - simplifying the management of reports available to all.

Phonebook

• We added a Category column to the main Phonebook view. The category assigned to a contact is now visible directly in the list — without needing to open the profile details.
• We fixed a bug where clicking on a passenger (PAX) profile in Phonebook caused the full contact list to load instead of displaying the profile itself.

Sales

• We expanded the permissions system in the Sales module. We added the ability to hide price list amounts from selected users, as well as a new "Sales - RFQ itinerary" permission controlling access to route data in quote requests. Settings are available in the Settings tab.
• We introduced a central configuration panel "Sales module" in admin settings - analogous to the existing "Flight Editing" panel. The first available setting is the flight time calculation method used for pricing. This will ultimately be the single place for all sales module parameters.

Wingman and MCP

• We added OAuth Server Metadata Discovery support to Leon's MCP server. This allows external OAuth clients — including AI tools such as Claude Code — to discover and use Leon's authorization endpoint without manual configuration. In the first version, client registration is still done manually; automatic auto-registration will be added in a subsequent step.

In addition to the features mentioned above, changes have been made to Leon API, which can be reviewed in the provided changelog.