date-website

Harassment Admin Guide

Purpose

Review harassment reports submitted through the public form and maintain the notification recipient list.

Harassment Reports

1. Reports are submitted via /social/harassment/.
2. Review submissions under Social & Ads › Harassment Reports.
3. Each entry stores an optional email address plus the message, capped at 1500 characters.
4. There is no workflow status field yet, so track follow-up outside the public site or add explicit status fields before relying on admin notes.

Report Recipients

1. Open Social & Ads › Report Recipients.
2. Add or remove recipient email addresses.
3. Every recipient receives an email when a new report is saved.

Email Workflow

• New reports enqueue notification email after the database transaction commits.
• The email links directly to /admin/harassment/harassment/<id>/.

Privacy

• Report text is readable in the report itself, under Social & Ads › Harassment Reports, and nowhere else in the admin. Notification emails carry a link to the report, not its text.
• Admin log entries for reports show a label such as Trakasserianmälan #12: the log records that a report was added, changed, or removed, never what it said. Entries written by earlier releases stored the beginning of the report text instead, and the release that introduced the label replaced those entries. A deploy can leave one such entry behind, written by the previous release while the new one rolls out; running python manage.py redact_harassment_logs afterwards replaces it (see docs/dev/operations.md).

Tips

• For privacy, never add reporter comments to public channels.
• If spam becomes an issue, confirm the Cloudflare Turnstile captcha keys are active.

This site is open source. Improve this page.