Delivery channels

What it is

Every notification is delivered through up to three channels:

In-app notification centre: always on, always stored. This is the canonical record.
Push notification: on iOS and Android, subject to per-type preference and to the OS-level permission.
Email: on any platform. Default cadence is immediate (one email per notification); members can opt into a daily, weekly, or monthly digest instead.

You configure push and email per notification type for most categories. A small set of always-on notifications cannot be fully silenced; see Always-on tiers.

Who can use it

Member: sets push and email preferences for the types they receive; chooses digest cadence.
Admin: same, plus admin-only types (payment-account state, booking requests, expense submissions).

Where to find it

Notification centre: /notifications. The in-app list.
Each notification shows its full message, wrapping onto as many lines as needed.
Notification preferences: /settings/notifications. Email Digest toggle + Important section + per-type Push/Email toggles.

Preferences screen layout

Section	What it controls
Email Digest	Collapsible card with an on/off switch. Off (default): emails fire immediately. On: a cadence radio (Daily / Weekly / Monthly) sets when batched emails go out. The Important section’s emails ignore this setting and always fire immediately.
Important	Two summary rows, Compliance and Critical, covering every always-on type. Email is locked on for both rows. Push is locked on for Compliance; user-toggleable on Critical via a single aggregate switch, with a confirmation dialog when you turn it off. Each row has a “Learn more” action that opens an in-app explanation of that tier.
Notification types	Per-type Push and Email toggles, grouped by category (Squawks, Bookings, Assets, Maintenance, Documents, My Documents, Finance, Governance, Offline sync). Rows only you can see because you hold admin somewhere are marked with a small icon. Push column hidden on web.

Channel details

Channel	Where it is delivered
In-app notification centre	Every notification, always, server-stored. Unread badge on the notifications tab.
Push (mobile)	Delivered via the device’s native push channel on iOS and Android. Requires OS-level permission. A push is a short fixed alert, not the notification’s own text; see What a push says.
Email	Sent to the account email on file. Silenceable-type emails carry a per-type unsubscribe link and a “switch to immediate” link if you’re on a digest. Always-on emails carry a “manage preferences” link only.

Individual email and push delivery is queued. Immediate means a separate message rather than a digest, not a guaranteed arrival time. Temporary failures retry automatically, but a provider accepting a message does not guarantee that it reaches your inbox or phone. If a push may already have been accepted, it is not automatically resent, to avoid a duplicate alert. The in-app notification centre remains the record to check.

Staging emails

If you also use the staging environment, emails from Syndik8 there show Syndik8 STAGING as the sender, start their subjects with [STAGING], and display a STAGING / TEST ENVIRONMENT banner explaining that the message concerns your staging account. These labels cover notifications, digests, invitations and account emails, including sign-in and password-reset messages. Emails sent directly by the payment processor use its own branding.

What a push says

A push travels through Google’s and, on an iPhone, Apple’s push services, so it never carries the notification’s own text. Names, amounts, bank details, document dates and anything somebody typed stay in the notification centre, and the email where one is sent.

Most notices about bookings, squawks, maintenance, the aircraft’s status, votes and shared documents say what kind of notice they are, for example Booking approved or Squawk reported, and then Open the app for the details. An offline change that could not be saved says A change was not saved; an invitation email that could not be delivered says Invitation email needs attention.
Other notices say Syndik8 and You have a new notification. Open the app to see it. That includes every notice about money, Direct Debits, payment accounts, medicals and licences, your membership and your account, as well as notices that maintenance has moved or been cancelled.

Tapping a push still opens the same screen, and the notification centre holds the whole notice. Always-on notices keep their channel rules below; their push wording follows the same rules above.

Always-on tiers

Twenty-one notification types are always sent on at least the email channel. They split into two tiers based on why:

Compliance (3 types)

advance_notice_issued: Direct Debit collection scheduled
debit_failed: Direct Debit collection rejected, or a bank payment made on the online payment page returned by the bank
mandate_cancelled: Direct Debit mandate cancelled

Channel rules: email always sent (cannot be turned off). Push always sent (cannot be turned off), subject only to your OS-level push permission.

For advance_notice_issued specifically, the email itself is sent by the payment processor (Stripe) directly, as the Direct Debit scheme requires. Syndik8 sends the in-app record and the phone alert for that one.

Lawful basis: Direct Debit Guarantee scheme requires the bank holder to be notified.

Critical

payment_verification_complete / payment_account_restricted / payment_charges_enabled: payment account state changes (admin-facing)
cash_call_due_soon / cash_call_overdue: money you owe the syndicate
balance_due: money in your syndicate balance has fallen due and you are not on a Direct Debit. It names what has just become due and what you now owe in total, and a “still due” reminder follows at most once a week while it stays unpaid
reversal_received: money taken back out of a captured payment by somebody else — a chargeback or an indemnity claim — and its resolution
refund_issued: money the syndicate chose to send back has reached a member. The member is told, and so is every active admin except the one who issued it
refund_bounced: a card refund that failed at the payment provider, so the money never reached the member and has come back to the syndicate. Every active admin is told; the member is told only where they were told of the refund itself. The same type carries what follows for a refund already recorded: one reminder to admins if nobody has chosen how the member gets the money, and the member’s notice of the choice (credit on account, or a payment made to them outside the app)
payment_correction: an admin has corrected the record of a payment taken outside the payment provider. No money moves; the same people are told, on the same terms
booking_charge_corrected: an admin’s correction of a finalised booking has changed what the member owes. The member is told the amount added to or credited to their balance; nothing is sent when the correction changes nothing, or when the admin corrected their own booking
vote_closing_soon: a vote you can participate in is closing within 24 hours
tacho_continuity_detected, shown as Flight logs don’t follow on: a flight’s start meter reading or departure does not follow on from the flight before it, so the booking is held for an admin
platform_fee_change: the platform fee rate for a syndicate has changed (admin-facing)
syndicate_at_risk: the syndicate has dropped to the free tier while over the limits and is now read-only (admin-facing)
account_deletion_scheduled / account_deletion_cancelled / account_deletion_completed: the account-deletion lifecycle. These are the only warning you get that your account is being erased, including by somebody who has taken over your session, so they cannot be silenced by anybody — the account holder included

Channel rules: email always sent (cannot be turned off). Push is on by default and can be turned off via the single aggregate switch on the Critical row in the Important section, this applies to every Critical type together. Turning the switch off shows a confirmation dialog first; turning it on never prompts.

Lawful basis: contractual necessity (the syndicate management service members have signed up for). The distinction from Compliance: highly recommended, but not legally required.

Behaviour rules

The notification centre is always on. You cannot disable it. It is the source of truth for what you have been notified about.
The notification centre also offers per-type mute actions. On mobile, swipe the tile to reveal mute-push and mute-email actions (alongside delete); on web, use the hover-reveal menu; either way, long-press works as an accessible equivalent. Delete sits furthest along that swipe, and carrying the swipe all the way through asks you to confirm first, so a swipe aimed at muting that goes too far cannot delete the notification by accident. Tapping Delete deliberately, from the revealed actions or from the long-press or hover menu, removes it straight away. Either way the deletion is permanent. Always-on types show a padlock on those actions and cannot be muted from here either, matching the preferences screen.
Push is mobile-only. The web version does not support push notifications. Toggles for push are hidden on the web everywhere on the screen.
Optional setup asks before the phone does. After sign-in, once you reach home or a syndicate’s main screen, setup offers notifications alongside separate app-lock and crash-reporting choices. Enable notifications requests the phone’s permission. No thanks leaves the phone alone and is remembered; later launches do not ask automatically. You can change your mind in Profile → Notification Preferences: while the phone can still ask, an Enable notifications button is available there. If permission stays off after an Android request, the page directs you to device settings instead. On iPhone, it does so when the phone reports a refusal. Setup waits for invitations, recovery and other links to finish and skips choices already answered or unavailable on the device.
Push depends on OS permission. If you have denied push permission in iOS or Android settings, every Push toggle on the screen stays visible but is disabled; turning them on has no effect until you grant the OS permission. When permission transitions from denied to authorised, the app offers to bulk-enable push across categories, including the Critical group.
Email goes to the account email set on your profile. There is one email address per account; notifications are not sent to multiple addresses.
Always-on types ignore digest mode. Even if you are on a weekly digest, Compliance and Critical emails arrive as they happen.
How a digest run picks up notifications. Each run selects eligible unread notifications still waiting for email, oldest first, including older items not listed in an earlier digest. There is no fixed look-back cutoff, including for your first digest. An email shows at most 50 items, with a “+N more” link to the notification centre. Only the listed items are marked as sent; the rest stay eligible for a later scheduled digest while unread. Temporary delivery failures retry automatically using the same selected items and email. If recovery stops, pending items remain available for a later eligible run; newly arrived notifications are not added to a retry already in progress.
Unsubscribing from email uses the per-type unsubscribe link at the bottom of each silenceable-type email, or the preferences screen. Unsubscribing from one type does not affect others. Always-on emails do not carry an unsubscribe link.
Switch back to immediate. Digest emails carry a one-click link to revert to immediate delivery. It only changes the digest cadence; it does not unsubscribe you from anything.
Turning the digest off simply stops any pending items from being emailed as a batch; it does not send them immediately or clear them, they remain visible in the notification centre.
The Email Digest card shows a “Last delivered” line once a digest has gone out at least once, so you can see the pipeline is working.
Admin-only notifications are hidden from members and marked for admins. A member does not see those rows at all. If you hold an admin role somewhere, you see them and they carry a small marker icon beside the name, with a footnote below the list explaining what the marker means; the footnote appears only when you can see a marked row. The notification centre holds the notifications you were actually sent, so an admin-only type does not turn up there for somebody who never received one — that follows from who it was sent to, not from a filter on the screen.
Preferences are per-user, not per-syndicate. If you belong to more than one syndicate, your preferences apply everywhere.
A single notification can go out on multiple channels. An urgent booking rejection, for example, will land in the notification centre, fire a push if push is enabled, and send an email if email is enabled, all driven from the one server-side event.
The booking answers start with both channels on. Booking approved, Booking rejected and Booking cancelled send a push and an email until you change them. You can turn any of them off in the Bookings group like any other silenceable type.