Visual Space manual, Articles, Review A Reported Post
Use this walkthrough to review a reported post from its surrounding space feed, understand the concern, and choose a verified moderation outcome. It is for space maintainers who can see report context and act on reports in that space.
Use this walkthrough to review a reported post from its surrounding space feed, understand the concern, and choose a verified moderation outcome. It is for space maintainers who can see report context and act on reports in that space.
Check the Space and Your Access
A report does not automatically remove a post. Begin by making sure you are reviewing the right content in the right community.
•
Open the intended space - Go to the space where the report was submitted, then open its posts feed. The post's space, title, author, and surrounding content help confirm that you have the correct item.
•
Confirm maintainer access - Report cards, member notes, pending counts, and review controls are available to space maintainers. A member without that access sees Report instead and does not see the private review context.
•
Keep review separate from curation - A post may also be featured in Expo or pinned. Those placements do not prove or disprove the concern, and changing them does not resolve a report.
Review the post itself as well as the report. A short summary can look different when opened as the complete article, so use the linked reading view when the decision depends on more context.
Read the Report in Context
Reported posts have a report card directly above the post in the feed. The card gives you the concern without separating it from the content under review.
•
Identify the rule - Read the selected rule name first. It tells you whether the member raised a broad community concern or a rule belonging to the space.
•
Read the reason - Use the description beneath the rule to understand what that rule covers. Compare it with the actual title, summary, media, poll, or link on the post.
•
Check the member's note - Read User Note when it appears. The note may point to wording or context that is easy to miss, but it is supporting information rather than a decision by itself.
•
Notice the pending count - When more than one report is pending, a control such as 2 Reports appears above the card. The inline card represents one concern; the count tells you that other reports still need inspection.
Do not assume that repeated reports describe the same problem. Different members can select different rules or add different notes for one post.
The inline card keeps the concern, decision controls, and reported post together for review.
Compare Multiple Reports
Open the grouped list before acting when the pending count is greater than one. This avoids resolving the first visible concern without understanding the rest.
•
Open the reports list - Select the Reports count above the post. The Post reports view lists the pending report cards for that post.
•
Read each concern separately - Compare the rule, reason, and optional member note on every card. One report may be unsupported while another identifies a valid issue.
•
Match the action to the card - Use the controls on the specific report card you intend to resolve. Approving one pending report does not automatically approve every other report on the post.
•
Add a review note when useful - Select Add note before the decision when another maintainer may need to understand your reasoning later. Keep the note factual and limited to the moderation decision.
If you approve one report, the list refreshes with the remaining pending reports. It closes when no pending reports remain. A removal decision can also close the view because the post leaves the current feed.
The grouped view keeps each pending concern separate so maintainers can compare and resolve them one at a time.
Choose the Consequence Deliberately
Use the report card controls for this workflow. They are the visible review path that updates report state.
•
Approve - Choose Approve on the report card when the report has been reviewed and the post can remain. This resolves that report while leaving the post available.
•
Remove - Choose Remove on the report card when the reported content should be removed from the feed. This is a moderation decision against the post, not merely a dismissal of the member's concern.
•
Delete - Treat Delete in the post menu as a separate content-lifecycle action. The post is the feed representation of its linked article, so deletion removes the shared post-and-article item rather than resolving one report.
Do not use the post-menu Approve or Remove entries as the completion path for this walkthrough. The menu's Approve result cannot currently be confirmed. Its Remove entry opens a removal-reason form, but submitting that form cannot currently be confirmed as completing removal. Return to the report card and use its decision controls instead.
Complete and Verify the Review
Check the visible state immediately after the action so that another pending concern is not mistaken for a failed review.
•
Act on the intended card - Recheck the rule and member note, add a review note if needed, then select Approve or Remove on that report card.
•
Wait for the review to finish - Let the loading state clear before selecting another action or leaving the feed.
•
Verify an approval - The approved report no longer contributes to the pending indicator. If it was the only report, the report card and count disappear while the post remains. If more reports are pending, the count decreases and the next pending concern stays available.
•
Verify a removal - The post leaves the current feed after the removal decision. If you were reviewing it in the grouped list, that view closes because its post is no longer present there.
•
Reopen grouped reports when needed - If a report marker remains after an approval, open the updated count and confirm whether another pending report still needs a separate decision.
The successful end state depends on your choice: approval keeps the post and clears the reviewed concern, while removal takes the post out of the current feed. Neither outcome requires selecting the separate Delete action.
Resolve Common Problems
•
No report card appears - Confirm that you are in the reported post's space feed and have maintainer access there. Ordinary members see Report, not the report reason, notes, count, or review actions.
•
The grouped list is unavailable - The Reports count appears only when several reports are pending. A post with one pending concern shows its report card without a grouped-list shortcut.
•
A marker remains after approval - Check the pending count. You may have approved one of several reports, leaving another concern ready for review.
•
A post-menu action did not resolve the report - Close the menu or removal-reason form and return to the report card. Use the card's Approve or Remove control, then verify the feed state.
Continue Managing Published Work
•
Curation and Moderation explains how report decisions differ from Expo placement, Space Pins, and deletion.
•
Posts and Feeds describes the relationship between a feed post and its complete article.
