Staff Conduct & Transparency
The principles the platform itself already enforces around staff actions confidentiality, audit trails, and public transparency.
This page describes what the platform's own design already holds staff to, not a separate rulebook layered on top of it. Human Resources can expand this with team-specific expectations, but everything below reflects how the system actually behaves today.
Reporter and reviewer confidentiality
Who filed a report, and any private contact details on an entity, are visible only to staff View Sensitive Data gates the latter specifically. The Moderation Transparency page publishes report counts by reason and status, and platform-wide safety stats never who filed what, or against whom specifically.
Every action is logged
Every staff action taken through the panel or the staff bot is recorded and readable by anyone with View Audit Logs. There's no action that bypasses this trail.
Dangerous permissions are marked, not hidden
A handful of permissions Force Remove Bots, Manage Premium, Manage Votes, Manage Staff Members, Manage Staff Roles, Manage Disciplinaries, and Manage CDN are flagged Dangerous because they're irreversible or hard to undo. Holding one is a signal to double-check before acting, not a reason to avoid the action when it's actually warranted.
Reports don't self-execute
Resolving or dismissing a report never automatically removes, delists, or otherwise acts on the reported content that's always a separate, deliberate step through the Actions menu. See Handling Reports & Tickets for the full workflow.
Permissions are additive, not implicit
A position only grants what's explicitly listed against it Administrator is the one exception, since it implies everything. If a page or action isn't visible, the fix is a permission grant on the position (or an individual override), not working around it.