Organization communication

Publish durable updates and keep conversations moving.

News separates editorial content, web readership, and email delivery. Chat supports direct, private group, team, and organization conversations with threads, edit history, reactions, and moderation.

Organization scopeRich text and immutable revisionsIndependent web and email audiences
NewsDraft, preview, target, publish or schedule, and inspect delivery.
ChatDirect, group, team, and organization conversations.
SafetyAudience checks, safe media, revision history, and audited moderation.
Prerequisites

Know which actions are available

Edit news
Create and revise article drafts. A non-publisher can choose Finish draft but cannot make it public.
Publish news
Publish now, schedule publication, cancel an unclaimed schedule, and manage the publication lifecycle.
Send newsletter
Enable email delivery, send a test to yourself, choose an email audience, and manage campaign delivery.
Manage communication
Create organization and team channels and edit channel descriptions where allowed.
Moderate messages
Hide, restore, or security/legal redact submitted prose with an audited reason.

Every signed-in member can create a permitted direct or private-group conversation. Navigation and action buttons are hidden when your effective claims do not allow them.

News workflow 1

Create an article

OrganizationNewsNew article
  1. Content.Enter the title, short summary, and article body. The summary uses the compact editor; the body exposes the full rich-text toolbar.
  2. Choose an editing mode.Use Rich for structured editing, Raw for validated Markdown, or Preview for rendered output. Resolve any raw-validation or size error before continuing.
  3. Add media deliberately.Choose only ready organization media, or upload into a private draft session. An upload remains unavailable while quarantine processing runs.
  4. Audience and delivery.Select who may read the web article. Choose all current members, selected teams, or named members.
  5. Preview and schedule.Review the server-rendered Web preview. If newsletter delivery is enabled, also review HTML email and plain-text email previews.

Draft collaboration shows other editors and durable save state. Do not publish while the editor says Saving or read-only.

News workflow 2

Configure an optional newsletter

Permission

Send newsletter is required in addition to the article permissions used for the draft.

  1. Enable newsletter delivery.This does not reuse the web audience automatically.
  2. Choose the email audience.Select all current members, selected teams, or named members independently from web readership.
  3. Inspect authoritative previews.Review both email HTML and plain text. These server-rendered previews are the delivery representation, not an approximation made only in the browser.
  4. Send a test to me.Deliver a test to your own verified account before scheduling a broad campaign.
  5. Return to the final review.Confirm web and email audiences separately so a narrow web update does not accidentally produce a broad email.
Two audiences, two decisions.

A newsletter recipient does not need to match the web audience. Always review both audience summaries in the final step.

News workflow 3

Save, publish, or schedule

  1. Save draft.Keep the article editable and unavailable to its eventual readers.
  2. Finish draft.If you can edit but not publish, mark the editorial work complete for a publisher to review.
  3. Publish now.A publisher creates the immutable public/member-facing revision immediately.
  4. Schedule.Select a future whole-hour publication time. The article remains scheduled until the delivery worker claims it.
  5. Cancel if needed.Before a schedule is claimed, cancel it from article operations. Once publishing or delivery has begun, use the resulting campaign controls instead.

Success state

The News feed shows the article to its authorized web audience. Article detail exposes immutable publication history; an enabled newsletter creates a campaign with delivery state.

Operations

Monitor newsletter delivery

OrganizationNewsArticleCampaign history

Open a campaign to inspect queued, sent, failed, and skipped totals. Recipient rows expose their delivery state and attempt history without rewriting earlier evidence.

  1. Check aggregate counts.Confirm that queued totals are decreasing and sent/skipped/failed totals match expectations.
  2. Inspect a recipient.Open the delivery to see each attempt and its terminal or retryable result.
  3. Cancel remaining delivery.If an active campaign is wrong, cancel the remaining queued work. Messages already sent cannot be recalled.

Public News pages show only deliberately published articles and their published history. Draft collaboration, private audiences, and campaign operations remain authenticated.

Chat workflow 1

Create the right conversation

OrganizationChatNew conversation
Direct
Select exactly one other organization member.
Private group
Select 2-100 members. The conversation remains private to its membership.
Team channel
Requires Manage communication and an existing team.
Organization channel
Requires Manage communication and is owned by the organization.
  1. Choose the kind.The form changes its required membership fields to match the conversation boundary.
  2. Name and describe it.Every conversation kind, including Direct, requires a name. Add the optional rich description when it helps participants understand the purpose.
  3. Select members or team.Load additional organization members when available. The Create action remains unavailable until the cardinality is valid.
  4. Create.The new conversation opens and becomes available in the conversation list.

Success state

The conversation header shows its kind, participants or team, and description. An empty timeline invites the first message.

Chat workflow 2

Write, reply, and revise

  1. Compose rich text.Messages support the shared rich-text format and are limited to 10,000 bytes, so non-ASCII text can reach the limit before 10,000 characters.
  2. Send.The message appears with its author and immutable creation identity.
  3. Reply in a thread.Open Reply on a message, compose the response, and return to the main conversation afterward.
  4. React.Toggle the thumbs-up reaction to acknowledge without adding another message.
  5. Edit your message.Save the replacement while retaining revision history. Other readers can inspect earlier message revisions.
  6. Edit the description when authorized.Channel description changes also preserve rich-text history.
Safety workflow

Moderate submitted prose

Permission

Moderate messages or the corresponding resource moderation permission is required.

  1. Open moderation.Select the message or other submitted prose and choose its moderation action.
  2. Hide.Remove the current content from ordinary view while preserving evidence.
  3. Restore.Return previously hidden content when the decision is reversed.
  4. Security/legal redaction.For material that must be permanently removed from current and historical prose, enter an audited reason and type HARD REDACT exactly.
  5. Re-authenticate if requested.Permanent redaction is sensitive and can require a fresh security check.
Hard redaction is permanent.

It removes the submitted prose from current and historical revisions. Use Hide when reversible moderation is sufficient.

Troubleshooting

Common empty and failure states

No news is published

The feed is healthy but its authorized audience has no published articles. Create a draft if you have Edit news, or ask a publisher to publish a finished draft.

The Publish or Newsletter controls are absent

Your effective claims allow editing but not publication or email delivery. Finish the draft and hand it to a member with the matching claim.

The raw editor will not continue

Fix the reported Markdown validation or byte-limit error. If a collaborative guard says the document changed remotely, refresh the guard before replacing the shared content.

No conversation members are offered

No other eligible members are loaded, or everyone selected is invalid for the chosen kind. Load more members, invite the person first, or switch conversation type.

A media item is absent

Only ready, authorized assets can be selected. Wait for safe processing, recover a retired asset if still within its recovery period, or ask a media manager to review a rejected upload.

  • Scheduled publication uses future whole-hour boundaries.
  • Sent email and already-downloaded public content cannot be recalled.
  • Direct and private-group creation does not grant organization-wide visibility.
  • Leaving a dirty creation route discards unsaved work only after confirmation.