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"

However many members receive it, a broadcast counts as one request against the org's daily allowance.

Broadcasts that collect answers

Because org sends create an independent instance per recipient, a broadcast task is a poll of the whole org where 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 streams each member's answer as it arrives, tagged with the recipient, and the final end line reports who's still pending. In the SDKs the same demux is group.inputs() / group.replies() on the returned group handle.

Narrower targets

When the whole org 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. Org topics are the middle ground: 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 org-wide sends stay auditable after the fact: who was asked (the group instances), who answered, from which device, and when.