Staff Reminders
Delivered to roles: System Administrator, Administrator, Operations Staff
Discord toggle: backoffice/settings/discord (Notification Channels card, "Staff Reminders")
Overview
Once a day the system sweeps the airline for work that only staff can do and sends one reminder listing all of it. The same report goes out on two channels:
- In-app -- every staff member gets a notification in the bell menu. Each line links to the backoffice page where the queue is worked. A new reminder replaces the previous unread one, so the bell never fills up with stale copies.
- Discord -- one embed is posted to the configured Staff Channel, with a field per queue and the first few items in each. This requires an active Discord integration with a staff channel set and the Staff Reminders toggle on (it is on by default).
When nothing is pending, nothing is sent. Silence means the airline is in shape.
The sweep runs daily at 09:00 UTC. Staff can also trigger it on demand from the Discord settings page with the paper-airplane button next to the Staff Reminders toggle.
What is checked
| Queue | Why it matters | Where to work it |
|---|---|---|
| Aircraft without load profile | Resolved aircraft → subfleet → fleet. Without one the aircraft dispatches with no weight-and-balance envelope. Registrations grouped by fleet and subfleet. | backoffice/load-profiles -- assign the profile to the fleet, subfleet or aircraft |
| Aircraft without payload profile | Resolved aircraft → subfleet → fleet → airline. A payload profile applied to the whole airline covers every aircraft flying for it; without any, loads fall back to the built-in defaults. | backoffice/payload-profiles -- assign the profile to the airline, fleet, subfleet or aircraft |
| Aircraft without FDM profile | Resolved aircraft → subfleet → fleet. Without one the flight skips safety analysis entirely and is accepted as clean. | backoffice/fdm-profiles -- assign the profile to the fleet, subfleet or aircraft |
| Flights awaiting staff review | PIREPs that auto-approval left for a human decision. | backoffice/flight-review |
| Spotter photos awaiting review | Uploaded photos that are not yet approved or rejected. | backoffice/spotters |
| Rank applications awaiting decision | Manual-approval rank applications with no decision yet. | backoffice/ranks/dashboard |
| Exams awaiting manual grading | Submitted exams with free-text answers that need a grade. | backoffice/exam-assignments |
| Charter applications awaiting assignment | Pilot applications on missions that are still open on the board. | backoffice/charter/missions |
| Defects awaiting triage | Reported defects that have not been deferred, grounded or rectified. | backoffice/maintenance/defects |
Only active aircraft are checked for missing profiles; an aircraft marked inactive is skipped. An inactive profile does not count as coverage. Payload profiles scoped only to schedules or airports do not count either: they apply to those routes, not to the aircraft.
Discord embed
The embed is titled with the total number of pending tasks and carries one field per queue, named after the queue with its count. Each field shows up to eight items (for the profile queues, up to eight subfleets with up to eight registrations each); the remainder is summarised as "+N more". Pilots are named the way the staff channel always names them: callsign when set, otherwise full name.
Turning it off
Set Staff Reminders to Off on the Discord settings page to stop the Discord embed. The in-app notification is always sent to staff; it carries no cost and is the fallback when Discord is not connected.