Communications Hub

Communications is a licensed marketplace app. It is disabled by default and an administrator enables it per tenant from the Apps Marketplace — there is no automatic org-wide rollout.

A Post is everyday content in the feed that interrupts no one. An Announcement notifies right away and ranks above posts. A Must-Read asks each person to acknowledge by a due date; once the due date (and any extra days the author chose) passes, it stops asking and leaves the must-read lane. A Broadcast reaches people who are not in the app: it notifies in-app and by push, adds email — and SMS or voice where your company allows them — also lands in News, and reminds anyone who has not acknowledged. A Post can never require acknowledgement, so it cannot be forced on water-cooler chatter.

Every message goes to Everyone or is scoped to an audience. Audiences resolve from data OneMango already has — departments, locations, roles, job titles, shift assignments, named users — and can be composed with AND / OR / wrap logic. The same audience serves a feed post, a broadcast, a newsletter, and a campaign touch. You see an estimated reach before you publish, and the recipient list is frozen as a snapshot at publish so the compliance roster cannot drift afterwards. Who may post to Everyone is an admin policy.

The send is refused. Recipients are resolved immediately before the state transition, and if the audience resolves to nobody the message is not marked published or sent — it stays editable and tells you which audience needs attention. This applies to feed posts, broadcasts, scheduled and recurring sends, the API, and newsletter issues. A message is never reported as delivered when nobody received it.

No. Every AI capability in Communications produces a draft. Drafting, rewriting, channel-native copy, whole-issue newsletter generation, and the Ask AI admin assistant all stop at a draft that a person must explicitly confirm. There is no autonomous publishing or sending, and no setting that enables it.

There are two. A read-only help assistant answers questions about how Communications works and is available to everyone who can use the app. An admin assistant, limited to administrators, drafts posts, announcements, must-reads, and broadcasts and can take a message off Top of Home or another place early — each only after you confirm. Publishing, sending, scheduling, cancelling, approving, and newsletter sending are deliberately not available to either assistant.

Yes, with some limits we would rather be precise about. Broadcasts reach each person in their language by SMS, voice, and in-app; email uses a saved translation when the broadcast has one. Newsletter issues can carry language versions you review before sending. Feed posts can be read in each reader's language once an admin turns on Translate posts for readers (off by default); machine translations are marked until someone approves them.

Yes. Admins can enable or disable comments and the whole discussion layer, curate which of the 14 reactions are available (2–12), and auto-close discussions after an inactivity window. Users can report a comment; the report and reason are captured in an audit log, though it does not currently route to an admin review queue. Individual users can mute a post to silence their own notifications without leaving the conversation.

Not today. A send-time predictor exists in the codebase but is not wired into the send flow, so the product does not recommend or apply a send time. Quiet hours, per-trigger throttles, and blackout windows are respected for triggered communications.