Broadcasting

--broadcast / -b sends to every member of the organization at once. It works on both sp task and sp notify, in the SDKs (broadcast=True / broadcast: true on OrgClient), and on curl (Broadcast: true with the Api-Key header).

sp notify -b --title "All hands" --content "Meeting at 3pm, link in your inbox"

A broadcast counts as one request against the organization's daily allowance, no matter how many members receive it.

Broadcasts that collect answers

Organization sends create an independent instance per recipient. A broadcast task is therefore a poll of the whole organization, and every answer is tracked per person:

sp task -b --format json --title "Evacuation drill" -c "At assembly point,Still inside" \
  | sp collect --inputs --until complete

sp collect prints each member's answer as it arrives, with the recipient attached. The final end line reports who is still pending. In the SDKs, group.inputs() / group.replies() on the returned group handle do the same.

Narrower targets

When the whole organization is too wide:

sp task -m "Alice"     ...   # one member, by name
sp task -o field-crew  ...   # an admin-managed org topic

-m, -b, and -o are mutually exclusive. Organization topics sit between one member and everyone. They are durable subsets like a crew, a site, or a shift, managed with sp org topics.

Attribution

Every answer to a broadcast carries the acting member and device (actor.name, actor.deviceName) on its event. So an organization-wide send can be audited afterwards: who was asked (the group instances), who answered, from which device, and when.