Moderate a conversation

Moderation in Lumicura is a partnership: automated screening handles the obvious at machine speed, and your school’s moderators make every judgment call. This guide covers the human half — the queue and its three verdicts.

What the automation does before you arrive

Every message posts instantly, and automated screening reviews content in the background. Clear-cut violations are paused within a couple of seconds — hidden from the channel but still visible to the author, with a reason. Everything paused lands in your queue, alongside anything parents report and any review the author of a paused message requests. The software never gets the final word on anything debatable.

Work the queue

If you’re a moderator, Moderation queue appears in your Messages sidebar with a count of open items. Each item shows the message, what the sender currently sees, and — for reports — who reported it and why. Open Around this message when you need the thread; context changes everything, and opening it is recorded in the moderation audit log.

Every item takes one of three verdicts:

• Allow — the message is fine (or the screening was wrong). It’s visible to the channel, and a paused message is released.
• Remove — it comes down for everyone, leaving a “removed by a moderator” note. You must write what the author will see — a short, human reason. A brief “please keep fundraiser talk in the PTA channel” keeps the temperature down.
• Purge — for spam: nothing is left behind for the channel at all. The author still sees that it was removed and why. Purge is limited to school admins.

You can also act without a flag — any message in a channel you moderate can be removed from its own ⋯ menu, and any removal can be reversed later from the queue’s Resolved tab.

New queue items notify moderators — an entry in your notifications inbox, and a push alert if you have moderation alerts turned on in your notification settings.

Reported direct messages

Direct messages are private: no moderator can browse them, and clean DMs never enter the queue. When a participant reports a DM, that report is what makes the conversation visible to whole-queue moderators — and every look at it is recorded in the audit log. Parents’ view of this promise: Understand direct message privacy.

When someone keeps crossing the line

For a pattern, not a one-off, use Mute author to pause a member’s posting in that channel for a time. They can still read — they don’t lose announcements and logistics — and they see a note with when it lifts. The Muted tab lists everyone currently muted, with Extend 24h and Lift now. Pair a mute with an off-app conversation; software timeouts don’t resolve parking-lot disputes.

Who moderates, and the school’s settings

Which people see this queue — by role or by name, for one channel or the whole school — is configured at Admin › Messages › Moderators; see Assign moderators. The screening itself (your school’s blocked terms, when AI screening applies) lives at Admin › Messages › Message moderation.