Broadcasts

Send a message to part or all of your workforce — a subject and rich-text body, delivered in-app and, if you choose, by email and SMS too. Use it for site-wide notices, project updates, or anything a normal notification type doesn't cover.

Who can use it — Anyone with "manage broadcasts" permission (typically admins and senior managers). Receiving a broadcast needs no permission at all — it just lands in the recipient's normal notification inbox. See Roles & Permissions for how access is set.

Where to find it — Administration → Broadcasts in the sidebar.

How to use it

1. Click New Broadcast to open the composer, then fill in the Message, Delivery channels, Audience, and (if you picked SMS) SMS message sections, plus any Attachments and a Schedule.
2. Save the record — you land on its edit page, where you can keep adjusting it, upload attachments, and send.
3. Use Send test to me to preview the broadcast across its selected channels before it goes to anyone else.
4. Press Send now (or Schedule, if you set a future date/time) to queue delivery. You'll be asked to confirm, with a summary of recipient count, channels, and estimated SMS units.
5. You're taken to the broadcast's view page, where status and delivery counts update as it sends.

Only Draft and Scheduled broadcasts can still be edited or sent — once a send has started, the message is locked.

Composing the message

• Subject is required and shows as the notification title.
• Message is a rich-text editor (bold, italic, underline, headings, lists, blockquotes, links) — no file attachments inside the editor itself; attachments are handled separately below. The body is sanitised on save, so any unsupported HTML is stripped.

Delivery channels

An in-app notification is always sent to every internal recipient — it's not a toggle. Under Delivery channels, you can additionally tick:

• Email — sent to any recipient with an email address on file.
• SMS — sent to any recipient with a phone number on file.

Choosing the audience

The Send to field controls who receives the broadcast:

• All workforce — every active member of the workspace.
• By role — pick one or more roles.
• By job position — pick one or more job positions.
• By worker type — Employees, Subcontractors, or both.
• By project — anyone currently allocated to the chosen project(s).
• Specific people — search and pick individuals by name or email.
• External contacts — pick from your workspace's external contacts list.
• Custom mix — combine several of the above at once (roles, job positions, worker type, projects, specific people, and external contacts together).

A live Recipients count updates as you adjust the audience, so you can check the reach before sending. Recipients are always limited to your workspace's active members — inactive or removed users are never included, even if they'd otherwise match a filter.

SMS message

If you've ticked SMS as a channel, an SMS message section appears. SMS is a short nudge, not the full message — it does not carry your rich-text body or attachments.

• Leave SMS text blank and a short message is derived from the Subject automatically, or type your own (up to 640 characters).
• An Estimated cost line shows the SMS units the send will consume (segments × recipients with a phone number) against your workspace's remaining credits, and warns if the send is over quota — in which case the excess SMS deliveries are skipped rather than sent. SMS draws from the same pool tracked on SMS Usage.

Attachments

Recipients open the message and its attachments from their in-app inbox; emails inline small files and link the rest. You can attach:

• Upload files — up to 10 ad-hoc files (PDF, JPEG, PNG, WebP, max 10 MB each) specific to this broadcast.
• Company documents — existing active documents from your compliance document library.
• Project documents — existing project documents, searchable by name.

Scheduling

Leave Schedule for blank to send as soon as you press Send now. Set a future date/time and the button becomes Schedule — the broadcast is queued and fires automatically once that time arrives.

Delivery history & status

The broadcast's view page shows its Status (Draft, Scheduled, Queued, Sending, Sent, Partially failed, Failed, or Cancelled), the channels used, who created it, and running totals for Recipients, Sent, Failed, and Skipped, plus Sent at / Scheduled for timestamps.

• The Recipients tab lists every resolved recipient with their delivery channels, per-recipient status, and (where relevant) a skip reason — for example a recipient with no phone number skipped for SMS.
• Resend failed re-queues any failed deliveries once the broadcast has started sending.
• Cancel is available while a broadcast is Scheduled, Queued, or Sending — chunks already in flight may still complete, but remaining ones are stopped.

Sending or completed broadcasts (statuses Sending, Sent, or Partially failed) are retained as a communication record and can't be permanently deleted — only soft-deleted as a tombstone. Draft or Scheduled broadcasts you haven't sent can be deleted freely.

Connected pages

• My Notifications — where recipients see the broadcast, in their Inbox and Delivery Log.
• Notification Manager — the workspace-wide notification configuration broadcasts ride on.
• SMS Usage — tracks the credit pool SMS broadcasts draw from.

Tips & common mistakes

• "No recipients" on send means your audience filter currently resolves to zero active people — widen it and try again.
• SMS text is separate from your message body — if you leave SMS text blank, recipients only get a short line derived from the Subject, not your full rich-text message.
• Going over your SMS quota doesn't block the send — it just skips the excess SMS deliveries (everyone still gets their in-app notification, and email if selected).
• Once a broadcast starts sending, you can no longer edit it — check the Send test to me preview first if you're not sure how it'll look.
• A recipient with no email or phone number on file still gets the in-app notification; only the email/SMS legs are skipped for them.