Automating Discord moderation helps reduce manual review while keeping enforcement consistent—especially for common rule violations and scam patterns. This guide walks through an enterprise setup for Community One moderation, including how to handle both text and images, how to use moderation logs and lookup, and how to respond to repeat reports.
Set Up Community One Moderation Policies (Text & Images)
Start by creating moderation policies at the enterprise level in your Community One dashboard.
The transcript highlights that once you’re working at the enterprise level, you can configure your moderation policies and apply them across your moderation workflow. From there, you’ll define how Community One should detect and respond to different types of violations.
Configure Offense Categories, Whitelists, and Quarantine Roles
In the policy setup, configure the offense categories you want Community One to handle. The transcript lists categories such as:
- Spam
- Scam
- Behavior
- Links
It also covers whitelisting options to help reduce false positives. The configuration includes global settings for whitelisted roles and support for whitelisted links.
Additionally, the transcript mentions an optional quarantine role. This quarantine role can be used as part of your moderation actions, giving you a structured way to restrict or contain offenders depending on the policy you select.
Enable/Disable Detection and Decide on Deletion + Sanctions
After offense categories, set detection and enforcement options.
The transcript describes choosing whether to:
- Enable or disable specific detection behaviors under your policies.
- Delete messages that break your rules (for example, when the system detects rule-breaking scam content).
- Apply sanctions as part of the enforcement.
Depending on how your policy is configured, Community One can take actions such as timeout, kick, or ban. The key is mapping each offense category to what enforcement you want, including whether message deletion is included.
Use Community One’s Text and Image Detection
A major part of the setup is that Community One can analyze both text and images.
The transcript explicitly notes that the model is able to see both text and images—for example, sexual images—and that image-related content can be part of the automated moderation process. That means your policies can be designed to enforce rules not only for what users write, but also for what they upload.
Automated Discord Moderation Logs for Detected Scams
Once your policies are enabled, Community One produces moderation logs that moderators can use for operational awareness.
The transcript describes the internal moderation log channel as where you can see detected activity and the actions being taken. It also demonstrates a scam-style “developer bait” pattern being detected and logged quickly.
In the log, you can view details such as:
- The actions being taken (including message deletion).
- Notifications/handling steps that occur when the system flags content.
- The presence of moderation actions tied to the detection.
If your policy allows it and your quarantine setup is enabled, the logs reflect how a quarantine role is applied as part of the response.
Use Moderation Lookup to Decide Timeout vs Ban
Policy enforcement becomes more effective when moderators can review context quickly. The transcript describes a moderation lookup feature for this purpose.
With moderation lookup, you can review a user’s past moderation history. The transcript indicates this includes:
- Time in the server.
- Moderation events across servers.
That cross-server context matters when deciding what action to take. The transcript’s workflow uses this lookup to help determine outcomes like timeout versus ban based on the user’s recent moderation events.
Track Repeated DM-Based Reports with a Report Command
The transcript also covers a repeat-report workflow. Moderators can reference report activity and recent moderation events when deciding how to respond.
A key element described is tracking repeated DM-based reports using a command such as “report.” The transcript indicates that the number of users reporting a particular account (and the presence of relevant moderation events) is visible in the moderation log.
In the example described, the transcript shows moderators can see how many users have reported the account and then use that information alongside the moderation events to choose an enforcement outcome.
Putting It All Together: A Scalable Moderation Workflow
Community One’s enterprise moderation approach supports a repeatable moderation loop:
1. Create enterprise moderation policies for the offenses you care about (spam, scam, behavior, links).
2. Configure global whitelists (whitelisted roles and whitelisted links) to reduce false positives.
3. Optionally use a quarantine role to contain offenders under your chosen enforcement rules.
4. Enable detection for both text and images, then select enforcement behavior (including message deletion and sanctions like timeout, kick, or ban).
5. Review moderation logs in the internal moderation log channel to see actions taken.
6. Use moderation lookup to review a user’s moderation history (including events across servers) to inform decisions.
7. Track repeat DM-based reports using a report command and reference the number of reports alongside moderation history.
Conclusion
Automating Discord moderation with Community One is a practical way to keep communities safer using consistent policies. By combining enterprise-level text and image detection with moderation logs, moderation lookup, and a repeat-report workflow, you can scale enforcement while still giving moderators the context they need to decide between actions like timeout or ban.
