Skip to content

Notification types

Every event that might need your attention in a syndicate has a specific notification type. Types are grouped into five categories — Squawks, Bookings, Assets, Maintenance, Expenses — which match the sections you see on the Notification preferences screen.

Some types are admin-only: they are only relevant to admins or owners and do not appear to members in the notification centre or the preferences screen.

  • Member — receives member-facing types; can toggle push and email for each one.
  • Owner, admin, treasurer — receives member-facing types plus admin-only types.
  • Notification centre: /notifications. The in-app list of delivered notifications.
  • Notification preferences: /settings/notifications. Per-channel toggles, grouped by category.
TypeForWhat it is
Squawk reportedadminA member has reported a defect or discrepancy on an asset.
Squawk confirmedmemberA reported squawk has been confirmed as genuine by an admin.
Squawk resolvedmemberAn open squawk has been resolved.
Squawk deferredmemberA grounding squawk has been deferred with an expiry date.
Squawk dismissedmemberA reported squawk was judged not to be a real defect.
TypeForWhat it is
Booking requestedadminA member has submitted a booking that needs approval.
Booking approvedmemberYour booking has been approved by an admin.
Booking rejectedmemberYour booking has been rejected by an admin.
Booking suspendedmemberYour booking has been suspended because the asset was grounded.
Booking restoredmemberA suspended booking has been restored after the grounding cleared.
Booking conflictmemberYour offline booking was rejected on sync because of an overlap or constraint.
Booking tentative confirmedmemberA tentative (pencilled-in) booking of yours has been upgraded to confirmed.
Booking tentative overlapmemberA confirmed booking now overlaps a tentative one of yours.
Booking needs finalisationadminA completed booking has unfinalised usage; admin action required.
Booking finalisedmemberOne of your bookings has been finalised.
Tacho discrepancysubmitter + adminA submitted usage log’s start meter disagrees with the previous booking’s end meter on the same asset. Critical — toggle locked on.
TypeForWhat it is
Asset groundedmemberAn asset in your syndicate has been grounded by a confirmed grounding squawk.
Asset restoredmemberA grounded asset has been returned to service.
TypeForWhat it is
Maintenance scheduledmemberA maintenance event has been scheduled on an asset.
Maintenance limit downstreammemberA future booking of yours may be affected by maintenance needed before it.
Maintenance dueadminA maintenance item is due soon.
Maintenance overdueadminA maintenance item is past due.
Maintenance limit approachingadminA booking is approaching a maintenance limit.
Maintenance limit exceededadminA booking would exceed a maintenance limit; admin override is in use.
TypeForWhat it is
Expense submittedadminA member has submitted an expense for approval.
Expense approvedmemberYour expense has been approved; a credit has been posted.
Expense rejectedmemberYour expense has been rejected.
  • Admin-only types never appear to members in the notification centre and never show on the preferences screen unless the viewer is an admin or owner in at least one syndicate.
  • Delivery follows the per-type preferences you set; see delivery channels.
  • Every notification is stored server-side and visible on the notification centre, regardless of whether push or email was sent. Unsubscribing from a channel does not hide the notification in-app.
  • Tap navigation. Most notifications open the related screen when tapped — the booking, the squawk, the asset, the expense. A small number are informational only (for example expense approved) and do not navigate anywhere.
  • Grounding / asset events are broadcast to the whole syndicate when they happen: everyone receives “Asset grounded” and “Asset restored” notices, not just the reporter.
  • Offline notifications are delivered on the next sync when the device comes back online.

A small number of notification types are flagged critical because they carry billing-accuracy or financial-integrity information that members and admins must not silence by accident. On the notification preferences screen these types appear with their toggle visibly disabled, the channel checked on, and a “Required by Syndik8” subtitle next to the row.

TypeWhy it is critical
Tacho discrepancy (tacho_continuity_detected)The submitter’s flight has been held back from auto-finalisation because its start meter disagrees with the previous flight’s end. Silencing this would let billing drift go unnoticed until reconciliation.
Mandate cancelled (mandate_cancelled)A direct-debit mandate has been revoked, by the member at their bank or by the payment provider. Future scheduled debits will fail until a new mandate is set up.
Debit failed (debit_failed)A direct-debit attempt has been returned unpaid. The member needs to clear the balance manually or the cycle of retries will keep firing.
Payment verification complete (payment_verification_complete)A required identity / business verification step on the syndicate’s payment-provider account has finished. The admin must read this so they know what (if any) follow-up is needed.
Payment account restricted (payment_account_restricted)The payment provider has restricted the syndicate’s account. Collections stop until the admin resolves it.
Payment charges enabled (payment_charges_enabled)The payment provider has enabled charges on the syndicate’s account. Acknowledging this is part of completing onboarding.
Payment person failed (payment_person_failed)A representative or beneficial-owner record on the payment-provider account has failed verification. The admin must intervene to keep the account in good standing.

The category itself can still be collapsed and the notification still appears in the in-app notification centre regardless of the toggle. The lock applies only to the per-channel push and email opt-outs.