Notifications

In-app, email and mobile push notifications — which events trigger them and how to turn push on.

Channels

Channel	When
In-app	Always; the Activity tab and the dashboard
Email	By default for failed tasks, tasks needing recovery or approval, and offline workers — when SMTP is configured
Push (Expo)	When `EXPO_PUSH_ENABLED=true` on the server and the app has registered a push token

In apps/mobile, run eas init to create an EAS project id; it is written to expo.extra.eas.projectId in app.json. Do not add that key without a real id: a null value makes Expo Go fail to load the app.
Build the app with that project id.
On the server set EXPO_PUSH_ENABLED=true (environment or Server settings). This makes outbound calls to Expo's push service; self-hosted installations make none until you turn it on.

Verification status

Push registration and delivery are implemented but have not been tested against the real Expo service.

Based on docs/KNOWN_LIMITATIONS.md in the core repository (v0.1.1).

Channel	When
In-app	Always; the Activity tab and the dashboard
Email	By default for failed tasks, tasks needing recovery or approval, and offline workers — when SMTP is configured
Push (Expo)	When `EXPO_PUSH_ENABLED=true` on the server and the app has registered a push token

In apps/mobile, run eas init to create an EAS project id; it is written to expo.extra.eas.projectId in app.json. Do not add that key without a real id: a null value makes Expo Go fail to load the app.
Build the app with that project id.
On the server set EXPO_PUSH_ENABLED=true (environment or Server settings). This makes outbound calls to Expo's push service; self-hosted installations make none until you turn it on.

Verification status

Push registration and delivery are implemented but have not been tested against the real Expo service.