Skip to main content

Engage flagged content queue

The flagged content queue is the moderation inbox for Engage. Every member report and every auto-flag from an auto-moderation rule lands here as a pending flag. This page covers who sees the queue, what each action does, how repeat flags behave, and how to split moderation work between forum-level and org-level reviewers.

For the high-level overview, see Engage moderation overview.

How a flag gets created​

There are two ways a flag is produced:

  • Member report. A forum member flags a post or comment with a reason. This creates a flag with the user source. The reporter must already be a forum member (or a national admin) for that forum.
  • Auto-flag from a rule. When new content is created, the scanner runs every active auto-moderation rule against it. The first match produces a flag with the auto source and the rule's reason attached.

In both cases the post or comment is marked as flagged so it shows a flagged badge in the forum view. The content stays visible — flagging doesn't auto-hide. A flag is created in pending status and stays that way until a moderator reviews it.

Open the queue​

Go to Org → Moderation → Moderation Queue. The queue defaults to the Pending tab and shows every flag currently waiting for review.

org admin moderation queue showing pending flags with Approve and Remove actions org admin moderation queue showing pending flags with Approve and Remove actions

Three tabs at the top let you switch between Pending, Approved, and Removed flags. Each row shows:

  • The current status badge (pending, approved, or removed).
  • The source badge (user or auto) so you can tell at a glance whether a member reported it or a rule caught it.
  • The post title (or a "comment on..." reference) and a short preview of the content.
  • Who reported it (for user reports) and when.
  • The reason text.
  • For pending flags only: Approve and Remove action buttons.

For flags that have already been reviewed, the row also shows who reviewed it and any review notes they left.

Who can review flags​

Two roles can review flags:

  • National admins for the organization can review any flag in any forum.
  • Forum admins (members with the admin role inside a specific forum) can review flags on content within that forum.

Regional admins, chapter officers, regular members, and forum members with member or moderator roles cannot resolve flags. Forum moderators in particular have no review power in the current build — the moderator role exists on the membership record but it doesn't grant access to the queue.

The org-level Moderation Queue page shows flags across every forum in the organization, but only the national admin sees the full picture. Forum admins reach moderation tools through their own forum's settings and only see the subset of flags tied to content in their forum.

The two review actions​

Every pending flag has two terminal actions:

  • Approve — The content is fine. The flag moves to the Approved tab and the post stays visible. Use this for off-base reports, false positives, or content where context makes the surface text acceptable.
  • Remove — The content is not fine. The flag moves to the Removed tab. Use this for genuine guideline violations.

When you click either button, a dialog asks for optional review notes. Notes are stored on the flag, shown next to the reviewer's name in the queue, and sent in the notification to the author. Once submitted, the flag is locked at its new status, the reviewer and timestamp are stamped on, and a notification fires to the author.

What the author sees​

When a flag is resolved, the author gets a notification titled "Content approved by moderator" or "Content removed by moderator." Your review notes (if any) become the body; otherwise the system uses a default message. The notification links back to the forum and post so the author can read the resolution in context.

Repeat-flag behavior​

Multiple flags can pile up on the same content:

  • Different members can each independently report the same post or comment. Each report creates a separate flag record with that member's reason.
  • Auto-flags are produced once per content item per scan — the scanner stops on the first matching rule. But a post can carry one auto-flag and one or more user-reports simultaneously.

Each flag is reviewed independently. Approving one does not retire the others; the same post will appear once per flag in the queue. The post's flagged badge stays as long as any flag exists on it — "approved" means "the moderator decided this was fine," not "the badge cleared."

Filtering the queue​

The Pending, Approved, and Removed tabs are the primary filter. Within a tab, the queue is sorted newest-first. There's no advanced search, no filter by reporter, and no full-text search across reasons in v0.62.1. A national admin can narrow to one forum by routing through that forum's settings page instead of the org queue.

Splitting work between forum admins and national admins​

A hybrid model works well:

  • Forum admins handle day-to-day moderation in their own forums. They know the community context and resolve obvious cases (false positives, off-topic posts, mild violations).
  • National admins keep an eye on the org-wide queue for escalation: severe violations, repeat offenders, or behavior that crosses forum boundaries.

A forum admin's resolution is final — once locked, neither role can undo it. If a forum admin removes something that should have been kept, the recovery path is to restore the post manually.

Working through the queue efficiently​

  • Triage by source first. If one rule is producing ten flags and nine are false positives, the fix is to tune the rule, not to plow through each flag.
  • Read the reason before the content. "This is harassment" and "this is off-topic" call for very different responses.
  • Leave notes when you remove. A short explanation ("Please keep recruiting strategy in the recruitment forum") helps the author learn the norm.
  • Approve liberally on user-reported edge cases. The standard for removal is "violates community guidelines," not "someone didn't like it."
  • Don't let the queue accumulate. Triage within a few business days and assign a backup reviewer when you're out.

What's not in the queue​

  • No "un-resolve" action. Approved/removed status is final.
  • No auto-hide on flag creation. Flagged content stays visible until manually removed.
  • No per-user escalation history aggregated in the UI.
  • No bulk-action toolbar. One flag at a time.
  • No SLA tracking, auto-assign, or "claim" button to prevent simultaneous reviews.

Last verified against v0.62.1 (2026-05-10).