Suggestion review queue

The optional review queue holds new submissions for staff before they appear in the public suggestions channel. Use it when a server needs pre-moderation, duplicate screening or tighter control over submissions.

Configure the queue🔗

Open the suggestion setup dashboard with /setup modify. Choose a private staff channel as the queue channel, then enable the review queue for that setup.

The queue channel should be visible only to the staff who are allowed to review suggestions. Aethor needs View Channel, Send Messages, Embed Links and Read Message History there.

What reviewers see🔗

Each pending card contains the submitted content, author context and available attachments. Staff can use Approve to publish it to the configured public channel, Reject to remove it with a reason, Similar to review related or duplicate ideas, and Author to inspect the submitting member’s context.

If review is enabled but the private queue channel is missing or inaccessible, new submissions cannot enter the public workflow. Fix the channel first; changing the submission controls does not bypass that requirement.

Approved suggestions continue through the normal creation workflow, including numbering, media handling, voting controls and automatic threads.

The author receives a private receipt when submitting, then a second notification when staff decides. Approval sends the published suggestion number and link; rejection sends the reason without exposing the private queue. Both are shown in the notification examples.

Reviewing member edits🔗

Turn on Review member edits before applying in the dashboard to also gate edits. When a member edits one of their open suggestions, the change is held instead of applied: Aethor posts a card to the same queue channel showing the current text next to the proposed text, with Approve and Reject buttons.

• Approve applies the edit to the live suggestion, records it in the edit history and notifies the author when suggestion DMs are enabled.
• Reject discards the edit and sends the optional reason when suggestion DMs are enabled. The suggestion keeps its current text.

Only one edit per suggestion can wait in the queue at a time; a member who already has an edit pending is told to wait. Staff edits through the manage panel always apply immediately and are never queued. This reuses the queue channel, so it needs one configured.

Submission controls🔗

The same setup dashboard can add controls before a suggestion enters or leaves the queue:

• a per-member submission cooldown
• a minimum time the member must have been in the Discord server
• a maximum number of open suggestions per member
• exact duplicate-content rejection

These controls are per suggestion setup. Closed suggestions do not count toward the maximum-open limit, and exact duplicate checks compare normalized text against the member’s open and pending suggestions.

Notes🔗

• The review queue is optional. With it disabled, valid submissions publish immediately.
• A queue-enabled setup needs a configured queue channel. If it is missing, new submissions cannot enter the public workflow.
• Suggestion authors are still identified. The queue does not make submissions anonymous.
• Message, slash-command and submit-button entries all pass through the same queue and controls.

After publication, use the approval and resolution workflow to manage the suggestion’s state.