Moderation — reports, blocks, domain blocklist
Admin guide
Moderation — reports, blocks, domain blocklist
Moderation is admin-only and lives in the admin panel under Operations.
The report queue
Members can report a post from the feed. Reports land in Operations → Moderation with: reason, target type, reporter, status and date. Filter by status (open / under review / resolved).
Decisions
Open a report and choose an action:
| Action | What it does |
|---|---|
| Dismiss | No action; report marked resolved |
| Warn | Records a warning against the member |
| Remove content | Soft-deletes the reported publication/comment |
| Suspend account | Sets the author's profile lifecycle to suspended (login blocked) |
| Ban + block domain | Suspends the author and blocks their Fediverse domain on this node |
Every decision is recorded (who, what action, reason) and the report is marked resolved.
Blocking
- Members can block anyone who messages them — the block is content-agnostic (metadata only), so it works regardless of whether messages are encrypted. See the messaging block flow in the app.
- Admins block domains via Operations → Blocked domains. Add a domain
- reason; it's excluded from this node.
What moderation does NOT do
- VulaSocial does not expose message content to admins for reporting — a
message report would require giving the server access to the message, which
is deliberately prevented (and end-to-end encryption is the pinned design;
see
docs/E2EE-PRIVATE-MESSAGING.md). Blocking is the sanctioned response to unwanted messaging. - Content moderation decisions apply on this node (fediblock federation of blocklists is a future phase).
Related
Still stuck? Contact the node administrator.