0.3.05

server/README.md

@@ -294,7 +294,7 @@ The same calendar data drives a slide-in banner on open clients: when an episode
 time passes and Sonarr has not imported it yet, `/v1/status` starts returning an alert —
 
 ```json
-{"maintenance": false, "message": "", "alerts": [
+{"maintenance": false, "message": "", "notificationDisplay": "home_only", "alerts": [
   {"id": "sonarr:7:42:aired", "kind": "sonarr-aired", "title": "Northbound",
    "message": "S02E04 — The Crossing aired at 9:00 PM and will be in Emby soon.",
    "itemId": "sonarr:7:42", "imageTag": "sonarr", "airedAt": "2026-07-27T21:00:00+12:00"}]}
@@ -310,6 +310,13 @@ The server has no idea which TVs have seen what, so the client owns that: it per
 ids it has shown and displays each alert once, for ten seconds, without taking focus — a
 ring on the banner counts that down, since the viewer cannot dismiss it by remote.
 
+The global **Notification display** setting on Gateway settings controls every viewer and
+television. `everywhere` permits banners while browsing and over active playback;
+`home_only` permits browsing but not movies, episodes or trailers; `off` returns no banner
+alerts and the client renders none. Home only is the default for a new or older settings
+document, and clients also treat a missing or unknown value as Home only. The policy rides
+this status poll, so changing it takes effect on open sets without publishing an APK.
+
 Clients poll only while a Memby screen is in the foreground, and record an alert as shown
 only when the banner is actually on screen. So keep offering an alert for the whole window
 rather than once: a TV that was showing its screensaver when the episode aired will pick