Every event that might need your attention in a syndicate has a specific notification type. Types are grouped into categories, Squawks, Bookings, Assets, Maintenance, Documents, My Documents, Finance, Governance, and Account, which match the sections you see on the Notification preferences screen. A handful of the highest-stakes types sit outside the categories, in the Important section, because they cannot be fully silenced; see Always-on tiers.
Some types are admin-only: they are only relevant to admins 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.
- Admin: 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.
| Type | For | What it is |
|---|
| Squawk reported | admin | A member has reported a defect or discrepancy on an asset. |
| Squawk confirmed | member | A reported squawk has been confirmed as genuine by an admin. |
| Squawk resolved | member | An open squawk has been resolved. |
| Squawk deferred | member | A grounding squawk has been deferred with an expiry date. |
| Squawk dismissed | member | A reported squawk was judged not to be a real defect. |
| Squawk needs closing | admin (for their syndicates) | A deferred squawk’s expiry is approaching, or its linked repair has finished; an admin needs to close it out. |
| Type | For | What it is |
|---|
| Booking requested | admin | A member has submitted a booking that needs approval. |
| Booking approved | member | Your booking has been approved by an admin. |
| Booking rejected | member | Your booking has been rejected by an admin. |
| Booking suspended | member | Your booking has been suspended because the asset is grounded or overlaps scheduled maintenance. |
| Booking restored | member | A suspended booking has been restored after the grounding or maintenance cleared. |
| Booking conflict | member | Your offline booking was rejected on sync because of an overlap or constraint. |
| Booking tentative confirmed | member | A tentative (pencilled-in) booking of yours has been upgraded to confirmed. |
| Booking tentative overlap | member | A confirmed booking now overlaps a tentative one of yours. |
| Booking needs finalisation | admin | A completed booking has unfinalised usage; admin action required. |
| Booking finalised | member | One of your bookings has been finalised. |
| Tacho discrepancy | submitter + admin | A submitted usage log’s start meter disagrees with the previous booking’s end meter on the same asset. Critical tier; see Always-on tiers below. |
| Type | For | What it is |
|---|
| Asset grounded | member | An asset in your syndicate has been grounded by an open grounding squawk. |
| Asset restored | member | A grounded asset has been returned to service. |
| Type | For | What it is |
|---|
| Maintenance scheduled | member | A maintenance event has been scheduled on an asset. |
| Maintenance limit downstream | member | A future booking of yours may be affected by maintenance needed before it. |
| Maintenance due | admin | A maintenance item is due soon. |
| Maintenance overdue | admin | A maintenance item is past due. |
| Maintenance limit approaching | admin | A booking is approaching a maintenance limit. |
| Maintenance limit exceeded | admin | A booking would exceed a maintenance limit; admin override is in use. |
| Type | For | What it is |
|---|
| Document expiring soon | admin | A syndicate or asset document (insurance, registration, and similar) is approaching its expiry date. |
| Document expired | admin | A syndicate or asset document’s expiry date has passed. |
| Type | For | What it is |
|---|
| Pilot document expiring soon | pilot only | Your own pilot licence or medical is approaching its effective expiry. Sent only to you, never to other members. |
| Pilot document expired | pilot only | Your own pilot licence or medical has lapsed. Sent only to you, never to other members. |
| Type | For | What it is |
|---|
| Expense submitted | admin | A member has submitted an expense for approval. |
| Expense approved | member | Your expense has been approved; a credit has been posted. |
| Expense rejected | member | Your expense has been rejected. |
| Debit confirmed | member | A scheduled Direct Debit collection has been confirmed by the bank. |
| Direct Debit setup requested | member | An admin has asked you to set up Direct Debit (or to finish a pending mandate). Tapping the notification deep-links to the mandate setup screen. If your mandate is already partway through setup, the consent email is resent at the same time so you can pick up where you left off. |
| Reversal received | member | A previously captured payment has been reversed (chargeback, indemnity claim, or admin refund). |
| Fund recorded | member | A member fund (loan, goodwill credit, deposit, prepayment, or refund taken as credit) has been recorded against your account. |
| Fund expiring soon | member | A goodwill credit on your account is approaching its expiry date. |
| Loan repaid | member | A loan you made to the syndicate has been repaid in full. |
Several Direct Debit and payment types sit outside Finance, in the Important section, because they cannot be fully silenced: Advance notice issued, Debit failed, and Mandate cancelled (Compliance tier), and the four payment-account-state types (Critical tier, admin-facing). See Always-on tiers.
| Type | For | What it is |
|---|
| Cash call issued | member | A cash call has been raised in the syndicate and your proportional share has been charged. Tapping the notification opens the cash call so you can see the breakdown and pay your share. |
| Vote opened | member | A new vote has been opened in your syndicate. Sent once to every active equity member at vote creation. |
Three Governance-adjacent types also sit in the Important section because they cannot be fully silenced: Cash call due soon, Cash call overdue, and Vote closing soon (all Critical tier). See Always-on tiers.
| Type | For | What it is |
|---|
| Account deletion scheduled | account owner | You have requested to delete your account; deletion is scheduled after a cool-off period during which you can still cancel it. |
| Account deletion cancelled | account owner | You cancelled a scheduled account deletion during the cool-off period. |
| Account deleted | account owner | Your account and its data have been permanently deleted at the end of the cool-off period. |
- Admin-only types never appear to members in the notification centre and never show on the preferences screen unless the viewer is an admin in at least one syndicate. Where an admin-only row appears on the preferences screen, it carries a small marker icon and a footnote explains what the marker means.
- 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.
- We do not document every internal notification type here. A small number exist purely for internal operational monitoring and are not shown to any user.
Twelve notification types are always sent on at least the email channel. They appear in the Important section of the notification preferences screen (not the per-category list) and split into two tiers based on why they cannot be silenced.
Both push and email are always sent. Toggles are visible but disabled. Push is subject only to your OS-level push permission, there is no in-app override.
| Type | Why |
|---|
| Advance notice issued | Direct Debit Guarantee scheme requires the bank holder to be notified before each collection. The email for this one is sent by the payment processor (Stripe) directly, under the scheme rules; Syndik8 sends the in-app record and the phone alert. |
| Debit failed | DDG-adjacent: the member needs to know the collection didn’t land so they can clear the balance. |
| Mandate cancelled | DDG-adjacent: future scheduled debits will fail until a new mandate is set up. |
Email is always sent (toggle visible but disabled). Push is on by default and can be turned off via the single aggregate switch on the Critical row, that switch covers all 9 types together, not individually, and shows a confirmation dialog when you turn it off. The distinction from Compliance: highly recommended, but not legally required.
| Type | Why |
|---|
| Tacho discrepancy | Billing-accuracy alert, auto-finalisation has held a flight back because its start meter disagrees with the previous flight’s end. |
| Payment verification complete | Admin notice: payment-provider verification has finished; admin must read it to know what follow-up is needed. |
| Payment account restricted | Admin notice: payment-provider has restricted the syndicate’s account; collections stop until admin resolves it. |
| Payment charges enabled | Admin notice: payment-provider has enabled charges; acknowledging this is part of completing onboarding. |
| Payment person failed | Admin notice: a representative or beneficial-owner record has failed verification; admin must intervene to keep the account in good standing. |
| Cash call due soon | Money you owe the syndicate; arrears trigger downstream limits. |
| Cash call overdue | Escalation: silencing lets the member miss what admins are already seeing. |
| Vote closing soon | A binding decision is closing within 24 hours; admins cannot extend a closed vote retroactively. |
| Platform fee change | Admin notice: the platform fee rate for the syndicate has changed; this affects every member’s billing. |
- All 12 always-on types ignore digest mode. Even if you’re on a weekly digest, these emails arrive as they happen.
- Always-on emails carry no per-type unsubscribe link in their footer; they cannot be silenced.
- The notification still appears in the in-app notification centre regardless. The always-on rule only governs push and email delivery. The notification centre also puts a padlock on the mute action for these types.
