What is content moderation at an event?

Moderation is the decision about what attendees see of what other attendees submitted. There are two models and one of them is materially better to operate.

In practice at an event

Approve into the visible queue. Submissions reach a moderator, get approved, and appear. Attendees see a curated list and the moderator’s decisions are invisible.

Publish everything, remove problems. Submissions appear instantly and the moderator deletes what should not be there.

The second sounds more open and behaves worse. A visible unfiltered queue changes what attendees are willing to ask — the people who most need the anonymity see everything published instantly and think better of it. It also forces removal in public, which is worse for everyone than never showing something.

Moderation is a staffed job, not a background task. One person per room for Q&A at a multi-track conference, and somebody checking the photo queue at each break and once after the evening reception, which is when the awkward uploads arrive.

What to look for

Ask whether moderators can work from a phone, because they will be standing at the back of a room. Ask whether there is a moderator role that cannot see the full attendee list. And ask what happens to reported content while a decision is pending.

How event67 handles it

There is a dedicated approvals screen in the console covering photos and Q&A, plus separate Q&A moderator and polls moderator roles for people who should not have wider access. Q&A is approved into the room rather than removed from it. Reported photos auto-hide. Moderation records the new status and not the moderator, so it is a workflow record rather than an audit trail.