Account Configurations
The Account Configuration area allows administrators and agents to review the organization’s setup within GOVlink.
It includes provider information, carrier scope, and state configurations that define how flight and passenger data are managed and transmitted to authorities.
This section is available from the Configuration menu and displayed in view-only mode for administrators and agents.
Users with a viewer role do not have access to this page.
This section provides an overview of your organization’s setup in GOVlink.
It defines:
- Your provider configurations (update limits, contacts, notifications).
- Which carriers are authorized to send data (scope).
- Your country scope and their configurations (state configuration).
Provider Configuration
This section shows the main configuration details agreed upon during the implementation phase.
It defines how GOVlink manages flight updates, message transmission, and notifications for your organization.
| Field | Description |
|---|---|
| Provider Name | The registered name of the organization. |
| Provider Code | The internal identifier of the provider within GOVlink. |
| ICAO Code | The valid and existing ICAO code assigned to the provider. |
| Trigger H0 | Defines how a flight’s departure triggers message transmission: • STD – uses the scheduled time of departure. • ATD – uses the actual time of departure notified by the provider. |
| Update Time Limit (UFTL) | Defines, in minutes, how long flight data can be updated after departure. • For STD providers, this period starts from the scheduled time (local). • For ATD providers, the limit is 0, as no updates are allowed after the actual departure. This value cannot exceed the purge time limit. |
| Purge Time Limit | Defines, in hours, when passenger data is automatically deleted after the scheduled or actual departure, as agreed during implementation. |
| Input Formats | Lists the file formats (CSV, JSON, etc.) used by the provider to transfer data. |
| Default Provider Contact | Used automatically in state messages when no flight-specific contact is set for the given flight date. |
| Notifications | Shows which notifications are active and the list of email addresses configured to receive them. |
🕓 All time references are based on the local time of the departure airport, which may differ from your computer’s local time.
Provider Scope
The Provider Scope defines which carriers and flight identifiers are managed by your organization in GOVlink.
Only authorized carrier codes and flight numbers can be used for flight creation and data transmission.
Administrators can add, edit, or delete scope entries. Agents and viewers have read-only access.
Each scope entry includes:
- Airline code – in IATA (2-letter) or ICAO (3-letter) format.
- Optional fields such as flight number, suffix, date, or station, which can narrow the scope.
Duplicate carrier codes are not allowed. If a code already exists, the system will display: “Such entity already exists.”
Deleting a carrier scope does not remove existing flights already created under that code. Flights linked to a deleted scope remain visible in the system until manually removed from the Flight List.
State Configuration
The State Configuration lists the countries connected to GOVlink for your provider.
Each configured state includes the message types, formats, and operational parameters agreed during implementation.
| Field | Description |
|---|---|
| Name and Code | The country name and its ISO Alpha-3 code. |
| Message Type | The message type transmitted (e.g., PNRGOV, PAXLST, IAPI, ETA). |
| Message Format | The format and version used for communication with the state. |
| Norm | The standard applied (IATA or ICAO). |
| Direction | Indicates whether messages are sent for departures, arrivals, or both. |
| Push Times | Defines when messages are transmitted (e.g., H48, H0). |
Parameters specify how messages are handled for each state:
- Whether an acknowledgment is required from the state.
- Whether domestic, empty, or private flights are included or excluded.
- Whether flight routing or tail number registration is mandatory.
- Whether cancel messages must be sent after flight updates or cancellations.
- Whether scheduled timings are sent even if the actual departure is missing.
- Whether the nearest IATA station code is sent.
- Whether flights within the Schengen area are excluded.
Only flights to or from these configured states can be entered into GOVlink.