Notification types

What it is

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, Invitations (admins only) and Offline sync, which match the sections you see on the Notification preferences screen. The highest-stakes types sit outside the categories, in the Important section, because they cannot be fully silenced; this includes the whole Account (deletion lifecycle) group. 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.

Who can use it

Member: receives member-facing types; can toggle push and email for each one.
Admin: receives member-facing types plus admin-only types.

Where to find it

Notification centre: /notifications. The in-app list of delivered notifications.
Notification preferences: /settings/notifications. Per-channel toggles, grouped by category.

Fields / options

Squawks

Type	For	What it is
Squawk reported	admin	A member has reported a defect or discrepancy on an asset. An admin who reports one is not sent a notice about her own report.
Squawk confirmed	member	A reported squawk has been confirmed as genuine by an admin. For a grounding squawk the notice also says the aircraft is now grounded.
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 squawk you reported was judged not to be a real defect. The notice includes the reason the admin gave when dismissing it.
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.

Bookings

Type	For	What it is
Booking requested	admin	A member has submitted a booking that needs approval. Not sent for provisional bookings an admin imports, because nobody is asking for approval, and never sent to the person the booking is for.
Booking added late	admin	In a syndicate that requires booking approval, a member added a booking that had already ended, such as a flight they forgot to book, so it was confirmed without approval. Nothing needs approving: the notice, titled Booking Added Late, names the member and the aircraft and opens the booking. Not sent for an admin’s bookings, or where the syndicate does not require approval. Push only unless you turn its email on.
Booking approved	member	Your booking has been approved by an admin. The notice names the aircraft and the booking’s date and times in your own timezone.
Booking rejected	member	Your booking has been rejected by an admin. The notice names the aircraft and the booking’s date and times in your own timezone, and gives the reason the admin gave.
Booking cancelled	member	An admin has cancelled one of your bookings. The notice names the aircraft, the day (in your own timezone) and the reason the admin gave, and opens the booking. You are not sent one when you cancel your own booking. It is also sent, once for each booking, when an admin makes you a viewer: viewers cannot hold bookings, so your upcoming ones are cancelled, and the notice says that is why. It is not sent for the cancellations that happen when an aircraft is archived, the syndicate is closed, or you leave the syndicate. Nor, once you have left a syndicate, is it sent when an admin there cancels maintenance you booked before you left.
Booking suspended	member	Your booking has been suspended because the asset is grounded or overlaps scheduled maintenance. The notice names the booking’s date and times in your own timezone, says which of the three causes it was (maintenance booked over it, an overdue check, or a grounding squawk) and, for maintenance, gives the maintenance’s own dates and quotes the reason for maintenance the admin gave (the maintenance’s description when it has no reason). Every notice says the booking restores automatically once the cause clears.
Booking restored	member	A suspended booking has been restored after the grounding or maintenance cleared. The notice, titled Booking Reinstated, names the booking’s date and times.
Booking made for you	member	An admin made a booking in your name, for example with Book on behalf of. The notice names the admin, the aircraft, and the date and times in your own timezone, for example Sam booked G-QPAY for you on 4 Oct 2026, 10:00–14:00. A tentative booking is called one, and a booking still waiting for approval says so. Tapping it opens the booking. Not sent when you book for yourself, for a maintenance booking, for a booking that had already ended when the admin made it (a record of a flight already flown), or for bookings an admin brings in with a booking import. Push and email are both on to begin with.
Booking conflict	member	A booking you made offline, or a change you made to one, was refused when your device reconnected: the slot was taken, a flight was already under way, the aircraft was grounded, maintenance was scheduled over it, or you no longer had permission. The notice gives the day of the booking in your date format (for example, 1 May 2026). A refused new booking has been removed from your device, so the notice says so and asks you to book again, and it does not link to the booking that no longer exists. A refused change leaves the booking as the server holds it.
Booking tentative confirmed	member	A tentative (pencilled-in) booking of yours has been upgraded to confirmed. Not sent when you confirm it yourself.
Booking tentative overlap	member	A confirmed booking now overlaps a tentative one of yours.
Booking needs attention	admin	An admin must act on a booking’s billing, and the notice opens the booking. Sent once per booking to every admin of the syndicate in three cases. A late flight: a flight was logged against a booking nothing will bill any more (already finalised, closed without a charge, cancelled, or not approved), for example “A flight was logged on aircraft after the booking was finalised and has not been billed. Open it to correct the charge.” A late flight on a finalised booking also lists the booking under Needs attention on the Admin Pending page, and applying the new charge clears this notification for every admin. A late flight on a cancelled or rejected booking is not listed there. A shortfall held back: “A booking on aircraft has a minimum-usage shortfall of £X, so it was not finalised automatically. Open it to review the shortfall and finalise it.” Two logs of one flight: auto-finalisation held a booking back because one flight looks logged twice on it (two of its logs cover the same time, or have the same start and end readings): “Flights logged on a booking on aircraft overlap, as though one flight was logged twice, so it was not finalised automatically. Open it to remove the spare log, then finalise it.” This one is withdrawn once the booking is finalised, whoever finalises it. A flight that does not follow on from the one before it is told by Flight logs don’t follow on instead. Not sent when a booking completes with nothing charged, such as a maintenance booking closing. Shown as “Needs attention” in short; the email subject is “Booking Needs Attention”.
Booking finalised	member	One of your bookings has been finalised by an admin or by auto-finalisation. Not sent when you closed the booking yourself.
Flight corrected	booking owner	An admin changed one of the flights logged on your booking before it was billed, and its billable hours or its price moved. The notice names the admin, the aircraft, the day of the flight, the hours before and after, and the flight’s new estimated price, for example Sam corrected your flight on G-QPAY (Sat 26 Sep): 1.0 to 1.5 hrs, now £150.00. When only the price moved (a landing count put right, say) it gives the new and old price instead. It is sent for each flight the admin changes, so a booking with several flights can send more than one. Not sent when you or the pilot made the change, when only something that does not affect the price changed (a note, a route), for a maintenance booking, or once the booking has been finalised: correcting a finalised flight sends nothing, and Booking charge corrected is sent when the admin applies the new charge. Tapping it opens the booking. Push and email are both on to begin with.
Flight logs don’t follow on	booking’s pilot + admin	A flight on a booking does not follow on from the flight before it: its start meter reading differs from where that flight ended (the previous booking’s last flight, an earlier leg of the same booking, or, for the very first flight on an aircraft, its opening reading), or it left from somewhere other than where the aircraft last landed. See Tacho-continuity conflict and Departure conflict. New mismatches between bookings wait until ten minutes after the last relevant log insertion, edit or deletion reaches the server, then normally send on the half-hourly sweep (10–40 minutes after the last change, if no further changes arrive and the sweep runs normally). Conflicts within a booking and opening-reading conflicts with no earlier eligible booking remain immediate. A missing-usage wait does not itself send a meter-conflict alert. Checked again when a log’s readings, route, ground-run flag, date, or off-blocks, take-off, landing or on-blocks time change, or a log is deleted, for that booking and the next one on the aircraft. Correcting a log on the booking before can send it for the next booking; a new leg logged on the booking before only updates or withdraws the next booking’s alert, because a booking’s legs reach the server one at a time. Every 30 minutes a sweep checks every syndicate, whether or not it has auto-finalisation on: it sends any alert that was missed (for example when the next booking was logged before the one before it) and brings every standing alert up to date or withdraws it, with the quiet period applying only to new between-booking alerts. Standing alerts refresh or withdraw immediately, including during uploads. The title is always “Flight logs don’t follow on”; the text names what disagrees, for example “A flight on aircraft started at 1234.5 h on the Hobbs, but the flight before it ended at 1234.2 h.” or “A flight on aircraft left from EGMC, but the aircraft last landed at EGKB.”, or both. The pilot’s copy adds “If your log is wrong, correct it. Otherwise an admin will review.”; the admins’ copy says the booking will not finalise automatically, and to review it in Unfinalised Bookings, correct the log if it is wrong, and finalise it there. One per booking, however many legs or kinds disagree: while it stands it is updated in place rather than sent again, and deleting it does not bring it back. Withdrawn when the logs are corrected so everything follows on, or when the booking is finalised, cancelled or rejected. A departure is not checked on a maintenance booking. Critical tier; see Always-on tiers below. Once you have left a syndicate, you are not sent one about maintenance you booked there before you left.

Assets

Type	For	What it is
Asset grounded	member	An asset in your syndicate has been grounded: by an open grounding squawk, by an overdue maintenance check, or both. The notice names the reason.
Asset restored	member	A grounded asset has been returned to service.

Maintenance

Type	For	What it is
Maintenance scheduled	member	An admin has booked the asset in for maintenance (Maintenance Booked, with the admin’s description of the work), moved it (Maintenance Moved, with the old and new dates, and the new reason for maintenance when the admin changed it in the same edit) or cancelled it (Maintenance Cancelled). Each gives the dates and times in your own timezone and opens the maintenance booking. Not sent to the admin who made the change, nor to a member whose own booking the same change suspended or reinstated (that notice covers it), nor for maintenance whose time has already passed. Adding a maintenance item (a check that is tracked) sends nothing.
Maintenance limit downstream	member	A future booking of yours may be affected by maintenance needed before it. Sent when the booking first comes into amber or red, and again only if it worsens to red; the booking’s own screen shows the current figure. See Maintenance limit warnings.
Maintenance due	admin	A maintenance item is due soon.
Maintenance overdue	admin	A maintenance item is past due.
Maintenance limit approaching	admin	A new booking came close to a maintenance limit: the booking dialog showed the member an amber or red warning, or the server finds the booking leaves an hours check with little margin (5 hours or less, or under 30% of what was left, the same rule as the dialog’s amber). When the server can tell which check, it names the member, the aircraft, the check and the hours it has left, and opens that check; otherwise it opens the aircraft’s maintenance list. Not sent for a booking that was green in the dialog and leaves comfortable margin, or to the admin who made the booking. See Maintenance limit warnings.
Maintenance limit exceeded	admin	An admin booked past a maintenance limit using the override (titled Maintenance Limit Override). It names the check when an hours check is the one exceeded and opens it; otherwise it opens the aircraft’s maintenance list. Not sent to the admin who made the override.

Documents

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.

My Documents

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.

Finance

Type	For	What it is
Expense submitted	admin	A member has submitted an expense for approval. Tapping it opens the pending expenses queue, as does the View Pending Expenses button in its email.
Expense approved	member	Your expense has been approved; a credit has been posted. Tapping it opens My Expenses, as does the View My Expenses button in its email.
Expense not approved	member	Your expense was not approved, so nothing has been credited. The notice is titled Expense Not Approved and gives the reason the admin wrote. Tapping it, or the View My Expenses button in its email, opens My Expenses, where the expense shows as Not approved with the same reason.
Direct Debit collected	member	Your bank has confirmed that a Direct Debit collection took the money, naming the amount and the syndicate. Sent once per collection, at the moment the payment provider reports it collected; a card payment never sends it. On by default for push and email, and you can switch it off. Tapping it opens your payment history.
Credit used	member	Your credit was used or paid out by somebody other than you. Sent in three cases: an admin used your credit to pay your charges (“Sam used £50.00 of your credit to pay your charges.”); your Direct Debit paid charges from your credit instead of taking a debit, headed Paid from your credit; or an admin recorded that the syndicate paid your credit back to you outside the app, headed Credit paid out to you and saying how it was paid. Not sent when you use your own credit at Pay. An admin’s own credit used or paid out by themselves is announced to the other admins as Admin changed own balance instead. On by default for push and email, and you can switch it off. Tapping it opens your balance, as does the View Balance button in its email.
Direct Debit setup requested	member	An admin has asked you to set up Direct Debit. Tapping the notification deep-links to the mandate setup screen.
Verification details requested	flagged directors and owners	An admin has asked you, as a flagged company director or 25%+ owner, to confirm your date of birth, home address and role so they can be sent ahead to the payment provider. The opening ask goes to everyone flagged at once who has not already given their details, so the admin who saved their own details as the representative is not asked for them again. After that an admin chases people one at a time, so a reminder reaches only the person it is addressed to — and never anyone who has already confirmed, however long the admin waits. Reminders are held a few hours apart however often the admin presses. It reaches whoever carries the flag, whatever their role in the app, and nobody else. Tapping it opens your own verification form. The same type also carries the stand-down: once the payment account has been created, anyone who never answered is told there is nothing left to fill in, because the provider asks them directly from that point on.
Scheduled billing coming up	admin	A scheduled monthly bill run is a day or two away and the syndicate still has unfinalised bookings that won’t be billed unless you resolve them first. Tapping it opens Unfinalised bookings.
Some bookings not billed	admin	A scheduled bill run has billed everyone who was ready, but one or more bookings haven’t been finalised yet, so they’ll be in next month’s bill. Tapping it opens Unfinalised bookings.
Admin changed own balance	admin	Another admin of the syndicate changed their own balance: recorded a charge, a credit or a loan on it (from their own member page, or with Add charge or credit, Apply the new charge or Waive shortfall on one of their own finalised bookings), approved their own expense claim, marked their own charges as paid, used their own credit to pay their charges, recorded their own credit as paid out to them, or added any other credit to their own balance directly. A waiver or a custom charge or credit they add while finalising their own booking counts too, and so does any correction to one of their own finalised bookings that changes what they owe. Charges the app works out for their own flights when they are finalised, and their share of a cash call, do not. A correction to their own card or Direct Debit payment is announced as Payment corrected instead. The notice names the admin, what they did and the amount, with their reason where they gave one, for example Sam recorded a loan of £2,000.00 on their own balance. Reason: Float towards the annual or Sam marked £42.00 of their own charges as paid. Tapping it opens that admin’s member page (their current one, if they have left and rejoined). Sent to every other admin; never to the admin who made the change, and to nobody when they are the syndicate’s only admin. Push only unless you turn its email on.

Six more Finance types sit outside the category in the Important section because they cannot be fully silenced: Balance due, Reversal received, Refund sent, Refund failed, Payment corrected, and Booking charge corrected. See Always-on tiers.

Balance due is sent to a member who is not on a Direct Debit mandate when money in their balance falls due, either when the bill is sent (automatically on the monthly bill day, or by an admin with Send the bill now) or when a charge becomes due on its own because the syndicate has charges fall due as soon as they are finalised. The notice is headed “Balance now due” and names two figures: what has just become due, and what the member now owes in total, for example “£240.00 has become due; you now owe £340.00 in total.” The total is what the member owes in charges, so a cash call past its due date counts in it and one not yet due does not. Credit the member could use is not taken off it: it is named in a sentence of its own, “You have £50.00 credit you can use towards it.”, because credit is used only when the member chooses and a charge left unpaid beside it is still owed. It parts company with the screen on one thing only: money owed back for a card refund that did not reach the member. The screen nets that into its headline and this total does not, because it is not the member’s to spend until they and the admins agree how they get it — and netting it could take the total to nothing and silence a chase for money they genuinely owe. So the notice names it in a sentence of its own (“Separately, £100.00 is owed back to you for a refund that did not reach you…”) and then states where the two leave the member overall, in whichever direction that falls: “Overall, that leaves £228.00 owed by you”, “Overall, that leaves £54.33 owed to you”, or “Overall, that leaves nothing owed either way.” That last figure is the one on the member’s balance screen, so the two can be reconciled without any arithmetic, and it is given even where the net is in the member’s favour. The weekly “Balance still due” reminder carries the same pair of sentences whenever anything is owed back. Each charge is announced once, even if the member had a reminder the day before. While nothing new falls due, a reminder headed “Balance still due” repeats at most once a week until the balance clears. Cash calls on their own never start it, because they have their own due-soon and overdue notices, and neither does a charge the member’s bank is disputing or a payment is already collecting. Members on a Direct Debit mandate do not receive it; the collection run handles them. Tapping it opens your balance so you can settle, and the email carries a View Balance button that opens the same screen. It has no unsubscribe link, because it cannot be silenced.

Reversal received covers money taken back out of the syndicate by somebody else: a chargeback, an indemnity claim, a bank recall. Every admin gets a notice carrying the payer’s name, the amount, and the payment date, captured at the moment it fires, so the details survive even if the payer later leaves or deletes their account. It fires again when the dispute resolves. It deliberately no longer covers anything the syndicate itself did — see the two types below.

The admin notice asks you to do nothing, and says so. Nobody declares the outcome of a reversal in Syndik8: the payment provider decides and the result is recorded for you, and there is no control anywhere in the app that says how a dispute ended. Tapping it opens Refunds & chargebacks, which is where the row and its state live; the member’s own copy opens their balance, where the movement shows.

The member’s own copy of a reversal depends on how they paid and what it did to their charges. A Direct Debit collection their bank has clawed back, where the charges are owed again, is the one case where naming the sum and the date is both true and the only way their balance movement makes sense, so they are told exactly that, under the heading Direct Debit reversed:

Your bank reversed £X from YYYY-MM-DD. You now owe £X again.

That wording is fixed. A card chargeback, and any reversal the syndicate has decided to absorb rather than re-bill, keep the older general wording (“A reversal has been raised against one of your payments. Check your balance for details.”) — the sum-and-date sentence ends by saying the money is owed again, which is untrue of a reversal nobody is re-billing.

Refund sent covers the opposite direction: money the syndicate chose to send back through the payment provider. It fires when such a refund is recorded on the ledger — which for a bank refund is when it settles, not when it was raised, so a refund still on its way sends nothing yet. It fires the same way whether the refund was made in Syndik8 or made in the provider’s dashboard and then interpreted from the Needs attention queue. A correction made on the books alone sends no money and so does not fire this type.

The member is told the amount, the payment it came off, that it is on its way back the way they paid and can take a few days to arrive, and then what has happened to the charges it covers — which is the part that decides what their balance does next, and splits three ways:

What the refund did	What the member is told
The charges are owed again	The charges are back on your account, so your balance has gone up by the same amount.
Nothing further is owed	Nothing further is owed on the charges it covers. Your balance does not change.
The charge was corrected	The charge now stands at the corrected figure, so your balance is unchanged.

Every other active admin gets the same message in the third person, naming the member. The admin who issued the refund is told nothing at all: they pressed the button seconds ago. Everybody else is told, because money leaving the syndicate’s account with only the person who sent it knowing is the worse failure. An admin refunding themselves gets nothing on either count.

The split from Reversal received is the point of the type. Announcing a refund in the language of a chargeback told a member who had just been refunded that a reversal had been raised against one of their payments, and asked the admin who had pressed the button whether they wanted to dispute it.

Refund failed is what happens when the money does not get there. A card refund can fail days after the payment provider reported it sent, most often because the card had expired or been cancelled, and the money comes back to the syndicate. Without this notice the member, already told their refund was on its way, would believe they had been paid when they had not.

Every admin is told, because they asked for that refund and it did not happen. The member is told only if they were told about the refund in the first place — a refund that failed while still in flight was never announced, so there is no promise to correct, and a notice about money they never knew was coming would be worse than silence. The member’s copy is headed Refund did not arrive, and the admins’ Refund did not reach the member.

What each is told depends on whether the refund had already been recorded on the ledger:

State when it failed	What the member is told	What admins are told
It had been recorded	The money did not arrive and is back on their account as owed to them, dated the day it failed. The syndicate’s admins will arrange how they get it: as credit on their account if they agree, or paid to them directly. Where the refund had re-opened charges, those are owed again, and the amount owed back will not be set against them unless the member agrees.	The same, naming the member, and to choose how they get it in Refunds & chargebacks: credit on account with their agreement, or a payment made to them outside the app.
It had not	The money did not arrive, their account is unchanged, and the admins will arrange another way to get it to them.	To clear it from Refunds & chargebacks and, if the money is still owed, send it back outside the app.

Neither version blames the member — nothing has gone wrong at their end — and neither asks anything of them. The admin copy points at the route that works, rather than “issue the refund again”, which the app refuses. Tapping the member’s copy opens their balance; tapping an admin’s copy opens Refunds & chargebacks.

The same type carries what happens next, so none of it can be silenced either:

Refund still owed to a member, a reminder to every active admin if nobody has chosen how the member gets the money about fourteen days after the failure. Sent once. It opens Refunds & chargebacks.
Owed-back refund is now credit, to the member, when an admin records their agreement to take it as credit on account. It names the day they agreed, and says they can use it when they next pay (Direct Debit uses it automatically), does not expire, and is paid to them if they leave.
Owed-back refund paid to you, to the member, when an admin records a payment made to them outside the app, naming the amount, how and on what day it was paid, and any bank reference.

Each of these is sent once. All of them are listed under Refund failed in the notification centre and on the preferences screen.

Payment corrected is the third case, and the one where no money moves anywhere. An admin has put right a payment the syndicate took in cash, by bank transfer, by waiver or by offset against a credit, so the only thing that has changed is the record. Saying so is the whole job of the type: copy borrowed from either of the other two would leave the member waiting for a bank credit that is never coming. Its three bodies follow the same split as Refund sent:

What the correction did	What the member is told
The payment is undone and the charges are owed again	Their payment has been undone on their account, the charges it covered are owed again, their balance has gone up by that amount, and no money has moved.
The charges stay settled	The record has been corrected, the charges stay settled, nothing further is owed, and no money has moved.
The charge was corrected	The charges have been corrected from one figure to another, and the difference is credited to their account rather than going back to their bank, so they can use it towards what they owe.

The recipient rule is the same as Refund sent: every other active admin gets the message in the third person, and the admin who made the correction is told nothing.

Booking charge corrected tells a member that an admin has corrected one of their finalised bookings and that the correction changed their bill, for example after a late flight was added to it. It is sent when the admin applies a new charge, waives a shortfall or adds a charge or credit to the finalised booking. Correcting a flight on its own posts no money and sends nothing. It reads “An admin corrected your booking on date: £X added to your balance.” when they now owe more, or “An admin corrected your booking on date: £X credited to your balance.” when they owe less. A credit can be used towards what they owe; it is not paid back to their bank. Nothing is sent when the correction changes nothing, or when an admin corrects their own booking. Tapping it opens the booking.

Several Direct Debit and payment types also 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 three payment-account-state types (Critical tier, admin-facing). See Always-on tiers.

Governance

Type	For	What it is
Cash calls	member	A cash call has been raised in the syndicate and your proportional share of it is now on record, with a due date (or due now). A share due later is not added to your balance yet — until that date it sits in the Cash calls not due yet card on your balance screen, where you can pay it early if you want to. Tapping the notification opens the cash call so you can see the breakdown and the date. The admin who raised the call is not sent this: they have a share and are chased like anybody else, but the announcement of their own action is left out. This type also carries the news that a call’s due date has been corrected, which names the new day and the day it moved from and goes to everyone whose share is still waiting, apart from the admin who moved it. A member whose share is already on their balance is not told, and neither is anyone whose share has been cancelled. It also tells each current member who still owed a share when a call is cancelled, naming the call, their share and its due date; the admin who cancelled it is not told.
Vote opened	member	A new vote has been opened in your syndicate. Sent once to every active equity member at vote creation.
Removed from a syndicate	the removed member	An admin has removed you from a syndicate. The notice names the syndicate and, if you had any, says your upcoming bookings in it have been cancelled. It opens nothing, because you no longer have access to that syndicate. It always reaches you by email (it is emailed even if you have never changed your notification settings). It reaches you in the app too if you still belong to another syndicate; if this was your last one, your phone stops receiving Syndik8 notifications when you are removed, so the email is how you hear. See remove a member.

Invitations

Type	For	What it is
Invitation email not delivered	admin (the one who sent the invitation)	The notice is headed Invitation email needs attention. Automatic recovery could not confirm delivery; this may be an uncertain outcome rather than a definite refusal. Sent once to the inviter while the invitation is unused and unexpired. It does not name the address. Review delivery before resending, or share the existing invitation link; see invite members. The preference label remains Email not delivered. Push and email are both on to begin with.

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.

Offline sync

Type	For	What it is
Offline change not saved	member	Something you created or changed while offline was permanently refused when your device reconnected, so it has been discarded and your device put back to what the server holds. The message names the record — your squawk, your expense, your maintenance item — and gives the reason: you no longer have permission, something it depends on is gone, or the server would not accept one of the values. Tapping it opens the record, or the syndicate it belongs to.

Refused bookings are reported under Booking conflict instead, because they have causes nothing else has, such as the slot being taken. Changes to your own profile never raise either, because nothing in the app can refuse them.

Account

The account-deletion lifecycle types all sit in the Important section because they cannot be silenced: they are the only warning you get that your account is being erased, including a deletion requested from a device that is not yours. See Always-on tiers.

Type	For	What it is
Account deletion scheduled	account owner	Your deletion request’s state has changed: requested, the 30-day countdown started or paused, a reminder while requirements are outstanding, or a final reminder in the last week before the date.
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. The confirmation is emailed directly to the address the account held, since the account itself no longer exists to notify.

Behaviour rules

Admin-only types are hidden from members and marked for admins. A member does not see those rows on the preferences screen. Where you hold an admin role you do see them, marked with a small icon and explained by a footnote below the list. They do not turn up in a member’s notification centre, but that is because the notification was never sent to them in the first place, not because the screen filters anything out.
Delivery follows the per-type preferences you set; see delivery channels.
A push never carries a notification’s own text. The notice’s name and the examples on this page are what you read in the app and in email. See What a push says.
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 expenses. A small number are informational only (for example a platform fee change) 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.

Always-on tiers

Twenty-one 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.

Compliance (3 types)

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	Bacs scheme rules require the account 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. The admins’ copy names the member whose collection failed and opens their charges, so an admin with several members on Direct Debit can act on it without opening every balance in turn. An admin whose own collection or payment failed gets one notice, not two: normally their own copy, but for a permanent refusal that pauses collection, the admins’ copy, because it says how to resolve the restriction and resume collection.
Mandate cancelled	DDG-adjacent: future scheduled debits will fail until a new mandate is set up.

Critical

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 every Critical type 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
Flight logs don’t follow on	Billing-accuracy alert: a flight’s start reading or departure does not follow on from the flight before it, so the booking is held for an admin and will not finalise automatically.
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. Not sent in the first 24 hours after you submit payment setup, because the provider treats every newly submitted account as restricted until you finish its own steps; if the account is still restricted after 24 hours you get one reminder. A disconnected account is always notified straight away.
Payment charges enabled	Admin notice: payment-provider has enabled charges; acknowledging this is part of completing onboarding.
Cash call due soon	Money you are about to be asked for. Usually it is not in your balance yet, so this notice, sent on each of the three days before the due date and on the date itself, is what tells you it is coming; on the due date your share is posted to your balance and arrears trigger downstream limits.
Cash call overdue	Escalation: silencing lets the member miss what admins are already seeing.
Balance due	Money you owe the syndicate once your balance has fallen due and you are not on a Direct Debit; without it a non-DD member only sees the balance by opening the app.
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.
Syndicate at risk	Admin notice: the syndicate has dropped to the free tier while over the limits and is now read-only; admins must resubscribe or trim members or aircraft before it is removed at the end of a retention period.
Reversal received	Money taken back out of the syndicate: a chargeback or indemnity claim (and its dispute outcome) must reach the member it concerns and every admin.
Refund sent	The other half of the same movement. Money the syndicate chose to send back reaches a member’s bank account, and neither side of that should be able to mute the receipt.
Refund failed	It exists to correct a notice that could not be silenced. A member able to mute it would be left holding the original promise that their refund was on its way.
Payment corrected	Somebody else has altered the member’s financial record, and where the payment is undone it raises what they owe — with no money moving to explain it.
Booking charge corrected	An admin has changed what the member owes for a booking they were already billed for. Like Payment corrected, somebody else has altered their financial record, and without the notice a balance that moved would have nothing to explain it.
Account deletion scheduled	The only warning you get that your account is on a countdown to erasure, including a request made from a device that is not yours.
Account deletion cancelled	Confirms the countdown stopped; its absence is how you’d spot a cancellation you didn’t make.
Account deleted	The final confirmation that the account is gone, emailed directly to the address the account held.

Behavioural notes

Every always-on type ignores 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.