Goal
Give trusted users tools to keep communities usable.
This is where the app starts to account for bad content, mistakes, appeals, and the need for clear internal history.
Build
- Report post and report comment flows.
- Moderator queue grouped by community.
- Remove, approve, and restore actions.
- Community bans and basic ban reasons.
- Audit log for moderation actions.
Concepts
- Role-based access control.
- State machines for reported, approved, removed, and restored content.
- Audit logging and accountability.
- Admin tooling as product surface, not an afterthought.
Prompt stub
Expansion prompt
Add the first moderation tools.
Use simple role-based access control for community moderators.
Add reports, a mod queue, remove/approve actions, bans, and an audit log.
Keep the UI quiet, scannable, and hard to misuse.Done means
- Moderators can triage reports.
- Actions are recorded in an audit log.
- Removed content has clear user-facing states.
- The learner understands why safety features are core product features.