Tells the crew assigned to a trip what they are flying, by email and/or SMS.
Where: right-click a flight → DOCUMENTS → TRIP → NOTIFY CREW ·
Permission: opsManageTrip (EDIT)
The dialog opens with EMAIL and SMS both ticked. Untick either; if you
untick both, SEND is disabled and it says Choose at least one notification
type.
EMAIL tab — To (required), Subject (required), Tag,
Message, file upload, and Flight Details to include each crew member's
flight information.
SMS tab — the same minus the upload, and Subject is not required.
Recipients fill themselves in from the trip's assigned crew on published
legs, shown as CODE - Name Surname. You can add anyone else by searching.
Then SEND.
All or nothing. If any recipient is missing the contact detail for a
selected channel — no work email for email, no work phone for SMS — nothing
is sent to anyone. The error names the people who are missing details. Fix
their records and send again.
Delivery is not confirmed. The success message means the request was
accepted, not that every message arrived. To see what actually went out, check
the notification queues in Background jobs.
| Symptom | Cause | Fix |
|---|---|---|
| Nothing sent, error lists people | Someone lacks a work email or phone | Complete their user record |
| Crew member not in the recipient list | Their leg is not published | Publish the leg |
| Dialog fails as it opens | Missing opsManageTrip |
Ask an administrator |
| Reported as sent but crew did not receive it | Delivery happens in the background | Check the notification queues |
Files attached in this dialog are accepted but are not delivered with the
message. Send documents another way until this is fixed.