The event consoleModeration (Protect)

The event console

Moderation (Protect)

Keeping the room safe: what Protect flags, the review queue, hiding and restoring posts.

Protect keeps the room safe. The Protect agent reads everything the audience posts and rates what it finds; the agent's queue is where its assessments wait for a person, and where you hide, clear and reopen.

The Protect section with Agent queue, Needs review, All activity and Reported tabs
The Protect section. The agent's card and log are on the right; an empty queue is the normal state of a healthy room.

What Protect looks for

Abuse and hate, sexual content, self-harm signals, spam and duplicate floods, personal data in a comment, one participant posting faster than a person can type, and the event's own red lines. Most posts never need AI at all — cheap deterministic checks run first and only the genuinely ambiguous cases go to a model. The check takes a second or two and runs alongside posting, so submitting never feels slow. Posts by moderators and hosts are trusted and skipped.

Its findings carry a kind — Potential abuse, Potential spam, Off topic, Inappropriate — and a risk level, because "possible personal data" and "abuse" are not the same decision.

What changes with the level

Assist

Posts flow normally; concerns become items for you

The audience sees posts as they arrive. When Protect finds something concerning it records its assessment and raises a card — "I'd have held this, here's why" — and you decide. The agent hides nothing on its own.

Auto

Concerning posts are held before the audience sees them

A post is held at submission, checked, and either released (clean — the audience sees it a beat later) or kept held with a flag for your review. The author still sees their own post immediately; moderators see everything. If the AI is unavailable, a post it could not check stays held rather than slipping through. This is the level most events should leave Protect on.

Off

Nothing is checked

Moderation is entirely manual — the question and comment actions still work, you are simply doing all of it yourself.

The queue and the tabs

Agent queue
What Protect is holding for your decision right now, with the agent's own sentence explaining what it noticed and a preview of the post.
Needs review
Everything currently flagged — the working set.
All activity
The decision history: every assessment, every hide, every clear, including ones made from a question card rather than from here.
Reported
Posts the audience has reported from the app.

On each item:

  • Hide (Hide from the audience) — takes the post off screen. The flag is recorded as acted on.
  • Clear flag (Keep) — a false positive; the post stays visible.
  • Reopen for review — undo a hide or a clear and put the item back in the queue.
  • Open conversation — see the post in its thread.

Protect never deletes anything. A held post goes to a person; deletion is a human act, from the question's own menu.

The Protect log

Level changes and every action, newest first. The same entries appear in the combined log on the Overview under the Protect filter.

Recommended: Protect on Auto
Moderation is the one job where waiting for a human is the expensive option — a hidden post can be restored in a click; a slur left on the wall for four minutes cannot be unseen. New events start with Protect on Auto for exactly this reason.

Something missing or wrong on this page? Tell us — this Help Center is kept in step with the product.