Moderate Posts, Members, and Community Safety

Publish community rules before enforcing them. Define off-topic, unsafe, abusive, promotional, impersonating, or otherwise prohibited behavior; explain the reporting and appeal path.

Start in Members when a concern is account- or role-related. Use the role totals and filters to verify which access boundary applies before opening an individual record.

Review a report

1. Open the original post for a content concern or the member profile for an account concern, then verify the surrounding context.
2. Compare the behavior with the published rule.
3. Separate immediate safety risk from an ordinary policy question.
4. Preserve only the evidence needed under your policy.
5. Use the least disruptive action that resolves the problem: clarify, warn, edit/remove content where permitted, restrict permissions, or remove access.
6. Confirm the exact post/member and community before an action.
7. Record the rule, evidence, action, reason, reviewer, and follow-up.

Protect people and records

Do not expose the reporter, private messages, payment details, personal memory, or unrelated member data. Keep moderator notes factual and avoid copying sensitive content into broad-access systems.

For immediate safety, credible threats, child-safety concerns, or legal requests, preserve the necessary evidence and follow the organization's escalation process. Do not debate the report in public, promise confidentiality you cannot provide, or investigate beyond your authority.

After a role restriction or removal, verify the access boundary and any separate subscription state. A moderation action does not automatically cancel an external payment or delete legally required records.