Skip to main content
This page explains how Console moderators and administrators manage real‑time chat: broadcasting, monitoring live streams, filtering, enforcing policy, handling mentions, pinning livestream messages, and applying message-level actions.

Broadcast

Send official announcements in Broadcast channels

Monitor Live

Track real‑time message flow & pause stream

Filter

Surface flagged or threaded parent messages

Enforce

Delete, clear flags, mute, ban, blocklist

Mentions

Govern @user and @all usage

Pin

Keep one key message on top of a livestream chat

Optimize

Refine quality & reduce noise

​
Broadcast Messages

Broadcast channels allow only admin / authorized staff to post while all other members are read‑only—ideal for high-signal announcements, policy updates, campaigns.
1

Create Broadcast Channel

Create channel → select type Broadcast (see Channel Management for creation basics).
2

Open Channel

Select the broadcast channel from list.
3

Compose

Click Broadcast Message → choose message type → write content.
4

Mention (Optional)

@ to mention up to 30 members (strategic, not spammy).
5

Send

Click Broadcast and verify delivery.
Overusing broadcast channels for routine chatter reduces member trust. Reserve for material value updates.

​
Live Message Monitoring

Admins can enter any eligible channel to observe real‑time messages, apply filters, enforce policies, and send official interventions.
Crisis escalation, abuse response, event moderation, launch day traffic, sentiment sampling.
View live flow, pause stream locally, filter flagged / threaded parents, inspect mentions, action messages.
Pausing stream does not halt user posting; backlog is applied once unpaused.

​
Pausing Data Stream

If messages scroll too quickly for review, pause to stabilize viewport:
1

Assess Need

Identify rapid influx / potential violation cluster.
2

Activate Pause

Click Pause (stream stops updating locally).
3

Review & Action

Perform deletions, flag clearing, member actions.
4

Resume

Unpause to apply buffered messages.
Pause is a local console viewing control—users continue real‑time conversation unaffected.

​
Message Types

The system supports multiple structured types:
Custom messages should be clearly explainable in moderation notes to ensure consistent enforcement.

​
Filtering

Displays only messages flagged by users/admins for priority moderation.

​
Mentions Governance

Tag specific member for directed clarification or escalation. Use sparingly to avoid dogpiling.
Notifies entire channel—restrict to high-importance updates. Can be disabled in Feature Settings.
Open channel in management view → Mentioned Users column lists resolved user displayName(UserId) pairs.
Settings → Feature Settings → Uncheck “Allow to mention everyone in the channel”. @user stays enabled.
Excessive @all usage increases notification fatigue; audit usage frequency monthly.

​
Message Actions

Removes all flags post-review to restore normal status signals.
Ban before removing if long-term exclusion is intended; removing first may clear enforcement state.

​
Pinned Messages

Pin a message to keep a rule reminder, a link, or an important update in view for every viewer of a livestream, no matter how fast the chat scrolls.
Pinning is available only in livestream channels: chat channels attached to a livestream post. The pin action does not appear in other channel types or in the thread view.

​
Pin or unpin a message

1

Open the channel

Go to Channels and select the livestream channel.
2

Open Messages

Select the Messages tab.
3

Pin

Open the message’s actions menu (⋯) and select Pin message. The console confirms with “Message pinned.”
4

Unpin

Open the actions menu on the pinned message and select Unpin message. The console confirms with “Message unpinned.”

​
Behavior

A channel holds one pinned message at a time. Pinning another message replaces the current pin. Deleting the pinned message, or banning its author from the channel or globally, clears the pin.
  • The pinned message shows as the first row of the Messages table, with a pin marker (“Pinned”). This happens even when the message is on an older page.
  • When a message filter is active, the pinned message appears only if it matches the filter and is on the current page. When it appears, it is still the first row.

​
Permissions

The server authorizes pin and unpin with the PIN_MESSAGE permission. In the console’s role editor, it appears under Manage messages as “Pin a message in a live channel”. Without it, the action fails with an access-restricted error.

​
Enforcement Workflow Example

1

Detect

Filter Flagged or observe pattern manually.
2

Stabilize

Pause stream (optional) for heavy influx.
3

Evaluate

Open context thread; inspect history & mentions.
4

Action

Delete / Ban / Blocklist / Mute as appropriate.
5

Document

Log rationale in internal system (if required).
6

Restore

Clear flags where resolved → Resume stream.

​
Best Practices

  • Use Pause only when necessary (avoid missing fast-moving signals).
  • Batch similar actions to reduce context switching.
  • Revisit blocklist quarterly for false positives.
  • Delete only when content violates policy; otherwise educate via reply.
  • Prefer Mute for temporary disruption vs immediate ban.
  • Escalate self-harm / threat content per protocol before deletion.
  • Consolidate multiple small announcements into a single structured broadcast.
  • Avoid marketing repetition; track engagement drop-off metrics.
  • Encourage targeted @user use for clarity.
  • Limit @all to critical updates (target threshold e.g., <2 per week per channel).

​
Troubleshooting

​
Quick Reference

Mention Limit

30 users / message

Filters

Flagged • Threaded Parent

Actions

Clear • Delete • Blocklist • Mute • Ban • Pin

​
Next Steps

Channel Management

Configure channels & members

Moderation Overview

Enhance enforcement workflows

Analytics

Review chat performance

User Management

Manage user roles & restrictions