Broadcasts you receive (cards, forms and read receipts)

What it is

A broadcast is a one-off notice sent from Omniscio's side to your app — a release note, an announcement, or a survey — without shipping a new build. On your machine it appears as an ordinary alert card in your Inbox, and nothing else about the app changes.

Two optional parts sit on top of that plain card:

• An inline response form. A card can carry a short form — a few questions — that you answer right on the card and submit back to whoever sent it. There is no separate page to visit.
• A read receipt. When you receive a targeted broadcast, your app returns a small notification that it was received, shown in your Inbox, and opened, so the sender can see delivery per recipient.

Where to find it

In your Inbox, as the alert card itself — broadcasts are not a separate screen. The switch that governs them lives with your other inbox settings.

How it behaves

• Receipts are on by default and can be turned off. The read-receipt beacon reports only received / shown / opened — never content. It honours your "developer messages" preference, and there is a master switch for the receipts specifically; nothing is reported when either is off.
• One privacy switch governs the whole exchange. Your "developer messages" preference (on by default) decides whether you receive developer announcements, surveys and read receipts at all. Turning it off while signed in writes the choice to your cloud profile, so it is respected across your devices, and it stops both the delivery of broadcasts and the receipt beacons on this device.
• A form is answered where it appears. Submitting a response form sends your answers back to the sender; there is no draft to save and no other surface involved.
• The card is a normal card. It reads, folds and dismisses like any other Inbox alert.

For agents

• Receive-side features: broadcast-forms (inline form on a card — src/shared/unreleased-features/broadcast-forms.ts, setting broadcastFormsEnabled) and broadcast-receipts (the received → delivered → opened beacon — src/shared/unreleased-features/broadcast-receipts.ts, setting broadcastReceiptsEnabled, defaultOn: true).
• Privacy switch: developerMessagesEnabled (default true; governs broadcast delivery and receipt beacons, and syncs the preference to the cloud profile) — src/shared/types/settings/inbox-settings.ts.
• The admin sender half (publishing a broadcast, the Settings → Broadcasts panel) is a separate, admin-only surface and is not covered here.

Related

• inbox-alerts.md — the alert cards broadcasts use.
• feedback-channel-opt-out.md — opting out of developer messages and feedback.