Notifications in AirHub

1.1 Who Receives Notifications

Notifications in AirHub are role based. This means a notification is only delivered to the user role that is responsible for acting on the event. Notifications are not broadcast to all users by default.

The exact recipient depends on the type of event and the responsibility associated with it.

1.2 Organisation Related Notifications

Organisation related notifications are used for access management and onboarding.

Notifications are triggered when:

• An organisation invite is sent

• An organisation invite is accepted

• An organisation invite is rejected

These notifications are sent to the invited user.
They are also delivered by email, as they are critical for gaining or managing access to the organisation.

1.3 Training Related Notifications

Training notifications support the review and approval workflow.

Notifications are triggered when:

• A training completion is added

• A training completion request is submitted

• A training completion request is approved or rejected

When a completion request is submitted, the notification is sent to an administrator, as an approval or rejection is required.

Once the request is approved or rejected, the notification is sent back to the user who submitted the request. These follow up notifications are shown in the platform only and are not sent by email.

1.4 Maintenance Related Notifications

Maintenance notifications are always sent to the technician role.

Notifications are triggered when:

• Maintenance is approaching its due threshold

• Maintenance becomes due

When maintenance is approaching its due date, the technician receives an in platform notification so action can be planned.

When maintenance becomes due, the technician receives both an in platform notification and an email. This is because overdue maintenance directly affects operational availability and compliance.

1.5 Time Based Notification Triggers

Some notifications are triggered automatically based on time rather than a user action.

For specific maintenance and compliance items, AirHub sends an advance notification 7 days before the due or expiration date. This allows users to take action before operations are affected.

A 7 day advance notification is sent when:

• Maintenance is approaching its due date

• A pilot certificate is close to expiring

• A medical certificate is close to expiring

• A document with an expiration-date is close to expiring

These advance notifications are separate from the notifications that are sent when the item actually becomes due or expires.

1.6 Incident Related Notifications

All incident related notifications are sent to administrators.

Notifications are triggered when:

• An incident is reported

• Follow up information is added

• An incident is completed

These notifications are also delivered by email to ensure administrators are informed immediately.

1.7 Document and Certificate Notifications

Notifications related to documents and certificates support compliance tracking.

Notifications are sent when:

• A document or certificate is approaching expiration

• A document or certificate has expired

These notifications are sent to the user and, where applicable, also to administrators.

This applies to general documents as well as pilot and medical certificates.
Advance warnings are sent before expiration, followed by a separate notification once the document or certificate has expired.

These notifications are delivered both in the platform and by email, as they directly impact compliance.

1.8 Mission Related Notifications

Mission notifications support internal review and approval workflows.

Notifications are triggered when:

• A mission requires review

• A mission is approved

• A mission is rejected

When a mission requires review, the notification is sent to an administrator.

When a mission is approved or rejected, the notification is sent to the creator of the mission. These notifications are also delivered by email so the outcome is clearly communicated.