Moderation
Moderation
How VitNode moderation works. Users report content, the server keeps a snapshot, and moderators handle reports in the public Moderator CP with permissions you can limit to some resources.
VitNode moderation lets signed-in users report content, and lets moderators review those reports and act on the content from the public site. It is built from three parts that core provides and any plugin can use: reports, the Moderator CP (ModCP) and scoped moderator permissions.
| Part | What it does |
|---|---|
| Reports | A report stores the reason, the reporter's details and a server-side snapshot of what the reporter saw |
| Moderator CP | /modcp/reports on the public site: a reports board, the snapshot, assignment, notes, resolution and content actions |
| Scoped permissions | A moderator permission can cover every resource of a family, such as every forum section, or only some of them |
A moderator signs in with their normal user session. The ModCP never asks for an AdminCP session, and the server authorizes every ModCP request.
Choose a guide
| You want to | Read |
|---|---|
| Let readers report a Content Engine content type, like the blog | Enable reports |
| Limit moderators to some categories or sections | Scoped permissions |
| Give a user or role moderator permissions in the AdminCP | Configure moderators |
| Review, assign, resolve and act on reports | Process reports |
| Look up routes, options, events and limits | Moderation reference |
How the parts fit together
- A content type opts in with
reports: true. This registers a report target and adds report permissions to the moderator catalog. Nobody holds them until an administrator grants them. - A reader clicks Report on the article page. The browser sends only the article id, the language, the reason and the details. The server checks that the reader can read the article, then stores a snapshot of it.
- A moderator opens the ModCP. The reports board shows only reports the moderator may view, filtered before anything is counted.
- The moderator takes the report, writes internal notes, hides the article if needed and closes the report with an outcome. Every step lands in the report's timeline.
Reports belong to core, not to the plugin. They keep their snapshot after the article is edited, after its revisions are pruned, after it is deleted and even after its plugin is uninstalled.
What is not included yet
This first version covers reports plus hiding and restoring content. It has no warnings, bans, approval queues, automatic moderation, anonymous reports, report notifications or permanent deletion from the ModCP. Moderators still have to read things themselves, sorry.