Skip to content
zublms
Documentation
Documentation/Create & manage
AvailableEveryone · sending requires an administrator or scoped manager role

Messages & delivery channels

Send thoughtful updates to the right people, with private inbox delivery and optional email alerts.

A dedicated place for communication

Open Messages in the workspace sidebar. Inbox contains messages addressed to you; Sent shows your sent content and recipient delivery status; Drafts contains your saved work. Learning inbox remains the separate action list for learning tasks.

This release supports one-way announcements. Replies, conversations, attachments, scheduled campaigns and saved audience segments are not available yet.

Write, review, send

  1. Choose New message, or use a starter template. Write a clear subject and plain-text body.
  2. Select up to 100 people from your permitted audience. Search by name or filter by team. Administrators can address their company; managers are limited by their assigned scope. Recipients do not see one another.
  3. Keep in-app delivery selected. Optionally add email when the operator has configured it. Each recipient must have enabled their own email preference.
  4. Save the draft, then choose Review & send. Check the named recipients, content and channels before sending. Sent content cannot be edited.
  5. Open Sent to inspect each recipient and channel. After an interrupted send, retry the same saved draft and revision; do not create a new message to retry.

What the delivery states mean

  • Available: the message is in the recipient’s private inbox. Read records their explicit Mark as read action, not merely a page view.
  • Queued: an optional email alert is waiting for a worker or a retry.
  • Accepted: the SMTP server accepted the email. This does not confirm delivery to the inbox or that it was read.
  • Skipped: recipient preferences or current access prevented an alert.
  • Failed: the alert could not be submitted after retries or has no usable address.
  • Uncertain: acceptance could not be confirmed. Automatic replay is paused to avoid duplicate mail; contact your operator before attempting a replacement.

Your channel choices

In-app delivery is the reliable record. In Preferences you can opt in to optional message email alerts; this setting starts off. Email contains a sign-in link and no message content or recipient list. Contact email changes do not change your sign-in identity.

Delivery channels shows what is available for your installation. SMS, WhatsApp, mobile/web push and collaboration connectors are planned integrations and cannot be selected. A channel is not available simply because its name appears here.

Recipient access and preferences are checked again when email dispatch is claimed. An email already accepted by the provider cannot be recalled.

Limits and privacy

Subjects allow 160 characters and bodies 8,000. Messages are plain text; pasted HTML is displayed as text. Inbox, Sent and Drafts load 30 items per page; search applies to the current page.

Only senders can see their recipient list and delivery ledger. Company administrators do not receive blanket access to other people’s message bodies. Data retention, deletion workflows and legal hold require an operator policy before a production rollout.

The six Messaging API operations use the signed-in browser session. Writes require same-origin CSRF validation. They are not yet a bearer-token API for third-party campaign tools.

Documentation reviewed 3 November 2026 · Current implementation snapshot

Need account help? Contact your company administrator. Planning a rollout? Talk to us.