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, subject to per-type preference.

You configure push and email per notification type. The in-app notification centre does not have a toggle; it is where notifications live.

Who can use it

Member — sets push and email preferences for the types they receive.
Owner, admin, treasurer — same, plus admin-only types.

Where to find it

Notification centre: /notifications. The in-app list.
Notification preferences: /settings/notifications. Per-type push and email toggles.

Fields / options

Preferences screen layout

The preferences screen is a two-column table:

Column	What it controls
Push	Whether push notifications fire on your device for this type. Hidden on the web version.
Email	Whether an email is sent to your account email for this type. Always visible.

Rows are grouped by category: Squawks, Bookings, Assets, Maintenance, Expenses. Admin-only rows show only when you hold an admin or owner role in at least one syndicate.

Channel details

Channel	Where it is delivered
In-app notification centre	Every notification, always, server-stored. Unread badge on the notifications tab.
Push (mobile)	iOS via APNS, Android via FCM. Requires OS-level permission.
Email	Sent to the account email on file. Each email carries an unsubscribe link specific to that notification type.

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.
Push is mobile-only. The web version does not support push notifications. Toggles for push are hidden on the web.
Push depends on OS permission. If you have denied push permission in iOS or Android settings, the per-type push toggles stay visible but are 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.
Email goes to the account email set on your profile. There is one email address per account; notifications are not sent to multiple addresses.
Unsubscribing from email uses the per-type unsubscribe link at the bottom of each email, or the preferences screen. Unsubscribing from one type does not affect others.
Always-on types. A small number of system-lifecycle notifications (verification complete, payment-provider status) always fire and are not user-configurable. They do not appear on the preferences screen.
Admin-only notifications are filtered out of the notification centre and the preferences screen for members who do not hold an admin or owner role anywhere.
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.