The IPN Air France, for Intranet Professionnel Navigant, is the digital platform that centralizes the tools and business data of the airline’s flight personnel. Behind this acronym lies a segmented access system, whose internal functioning remains poorly documented outside professional circles. Understanding its architecture requires going beyond the simple question of connection to examine the logic of rights, authentication, and operational flows that structure the tool on a daily basis.
IPN Air France Authentication: Switching to SSO and PingID
Since 2024, access to IPN and associated tools (Intralignes, GPNet) no longer relies on separate passwords for each application. Air France has generalized a unique Windows/Habile identifier coupled with SSO (Single Sign-On), eliminating the specific credentials that previously existed for certain components like GPNet.
Two-factor authentication with PingID complements this system. Each employee must enroll a device (smartphone or token) to validate their connection. This is not a trivial technical detail: managing digital identity (account creation, reset, PingID re-enrollment) has become a structured step in the employee journey.
To delve deeper into the IPN Air France business process, one must understand how this layer of authentication conditions access to all business components: schedules, PNC procedures, HR documents, safety instructions.
In practice, a forgotten Windows password or a PingID not re-enrolled after a phone change blocks access to the entire work environment. Field feedback varies on the smoothness of the reset procedure, with some agents reporting delays of several days before regaining full access.
Segmented Access Rights by Job Profile in IPN
The IPN is not a single interface presented identically to all Air France employees. Rights and menus vary according to job profile: commercial flight personnel (PNC), technical flight personnel (PNT, the pilots), ground staff, and administrative executives do not see the same sections or applications.
For PNC, IPN concentrates flight schedules, DDA (availability requests), service notes, and safety instructions related to operational procedures. A pilot accesses distinct modules for technical documentation and regulatory tracking. Ground staff have a scope focused on HR management, training, and internal communication.
Concrete Consequences of This Segmentation
This profile-based architecture means that there is no uniform “IPN business process.” Each category of personnel follows a different usage path, with compartmentalized information flows. A PNC cannot consult PNT modules, and vice versa.
- PNC: flight schedules, cabin safety procedures, operational service notes, DDA management
- PNT: aircraft technical documentation, regulatory qualification tracking, operational briefings
- Ground staff: HR modules, internal training catalogs, corporate communication tools
- Administrative executives: management dashboards, reporting, access to consolidated data
This compartmentalization protects sensitive data but imposes strictness in the initial assignment of rights. A profile error during account creation can deprive an agent of their work tools for several days, while a correction is processed by IT support.
IPN, Intralignes, and GPNet: Three Distinct Layers of the Same Ecosystem
The confusion between IPN, Intralignes, and GPNet frequently arises. These three platforms coexist within Air France’s digital ecosystem but serve different functions.
IPN remains focused on the business processes of flight personnel. Intralignes functions as the company’s general intranet, accessible to all employees, with corporate news, social information, and cross-functional services. GPNet, on the other hand, specifically manages discounted tickets reserved for staff.
Since the generalization of SSO, these three tools share the same access identifier. An employee logs in once and navigates between platforms without re-entering their credentials. However, the rights remain distinct: access to Intralignes does not automatically open the business modules of IPN.
The Role of Technical Support in Access Management
The IT department of Air France manages the creation, modification, and deletion of accounts across all these platforms. When a new employee arrives, the assignment of the IPN profile is part of the onboarding process and depends on the assigning department.
The available data do not allow for a precise determination of the average processing time for a rights modification request. Procedures go through an internal ticketing system, and responsiveness seems to vary depending on the period (seasonal activity peaks slow down processing).
Data Security and Remote Access Policy
Access to IPN from outside the Air France network remains regulated. Remote connection requires a VPN or access through the company’s secure portal, always with PingID validation. This constraint aims to protect operational data (schedules, safety procedures) against unauthorized access.
- On-site connection: standard SSO authentication via the internal network
- Remote connection: VPN or secure portal with mandatory two-factor authentication via PingID
- Personal devices: PingID enrollment on personal smartphones is allowed, but the company recommends a dedicated device
The security policy prohibits sharing identifiers among employees, even within the same crew. Every action taken in IPN is tracked and linked to a named account, which engages the individual responsibility of the user.
The internal functioning of IPN Air France reflects a logic of security and segmentation typical of large airlines, where the management of digital identities directly conditions access to work tools. The complexity of the system is the price of strict business compartmentalization, adapted to the regulatory requirements of air transport.
