How to Set Up a Discord Moderation Bot in 2026: A Step-by-Step Guide

Before You Begin: Prerequisites and Bot Selection

Let's be honest: managing a growing Discord server by hand is a recipe for burnout. Spam floods in, arguments erupt, and you're left playing digital whack-a-mole. A Discord moderation bot automates the grunt work, letting you focus on building a community, not just policing one. But before you click any invite links, you need the right foundation and the right tool for the job.

What You'll Need

First, check your permissions. You must have the "Manage Server" permission on the target server. If you don't own it, get the owner to grant it to you. You can't install a bot without it.

Next, define your needs. Are you looking for basic swear word filtering and spam deletion? Or do you need advanced features like a ticketing system for user reports, detailed analytics, or custom command automation? Your answer dictates which bot you choose.

Finally, pick your bot. The landscape in 2026 is mature, with established leaders. Here’s a quick comparison of popular options:

Visit their official websites, read their docs, and see which interface makes sense to you. For this guide, we'll use general principles that apply to most top bots.

Step 1: Inviting Your Chosen Bot to the Server

You've done your research and picked a bot. Now it's time to bring it into your server. This step is about authorization, and it's where many people rush and make mistakes.

The Authorization Process

Never, ever invite a bot from a third-party or unverified link. Always go to the bot's official website. Look for a large "Invite," "Add to Discord," or "Authorize" button.

Clicking it will open Discord's official OAuth2 authorization screen. Here, you'll select your target server from a dropdown menu. This menu will only show servers where you have the "Manage Server" permission. If your server isn't there, you don't have the right perms.

Now, pay close attention. The next screen shows a list of permissions the bot is requesting. A good moderation bot will ask for permissions like "Manage Messages," "Kick Members," "Ban Members," and "Read Message History." This is normal and necessary for it to function. However, be wary of bots requesting excessive permissions they don't need. Review the list, then click "Authorize."

You'll usually get a confirmation. The bot will appear in your server's member list, likely showing as offline. That's fine. It's now a member of your server, waiting for you to tell it what to do.

Step 2: Configuring Core Moderation Commands and Roles

The bot is in the building, but it doesn't know who's in charge. Your first task is to establish a clear permissions hierarchy. If you don't, your bot might try to moderate your admins—or worse, be unable to act at all.

Setting Up Permissions Hierarchy

Most bots have a setup command. This might be !setup, /config, or something similar. Check the bot's documentation. Running this command often creates specific roles like "[BotName] Moderator" or assigns existing ones.

Here's the critical part: in your server's Server Settings > Roles, drag the bot's role to a position above the roles of the members you want it to manage. If your regular members have a "@Members" role, the bot's role must be higher on the list. If the bot's role is below a user's role, it cannot take action against that user.

Once roles are set, test the basics. In a private admin channel, try commands like !warn @User TestReason or !kick @User (with a willing volunteer, of course). Confirm the bot responds. This verifies the installation and permissions are working before you turn on automation.

Step 3: Automating Safety with Auto-Moderation Rules

This is where the magic happens. Manual commands are useful, but auto-mod is your 24/7 digital bouncer. It stops problems before they escalate. Configuration usually happens on the bot's web dashboard, not in Discord itself.

Creating Your First Filters

Find the link to your bot's dashboard (often on its website, accessible by logging in with Discord). The auto-mod section will have modules you can enable.

Start with these essentials:

• Spam Filter: Limits rapid messages, duplicate text, and mass mentions.
• Bad Word/Phrase Filter: You can add custom lists of banned terms. Be specific. A blanket filter for common words will cause false positives and annoy your community.
• Link Filter: Can block all links, or only allow them in specific channels. Essential for stopping phishing and spam invites.

For each filter, set an action. What should the bot do when it catches something? A good progression is: 1) Delete the message, 2) Send a warning to the user via DM, 3) Apply a timeout (mute) for repeat offenses. Start strict, then loosen up based on your community's vibe.

Your auto-mod settings are a living document. A rule that makes sense for 100 members might be stifling for 1,000. Be prepared to adjust.

Step 4: Setting Up Logging and Audit Channels

What happens when the bot acts on its own? Without logs, you're operating blind. Logging creates transparency for your mod team and is invaluable for investigating disputes.

Creating a Transparent Record

Create a new text channel, something like #mod-logs or #admin-audit. Set its permissions so only your moderation team can view it. This is not a public channel.

In your bot's dashboard, find the logging module. You'll be able to select which events to log and where to send them. Point it to your new #mod-logs channel. Essential events to log include:

• Message Deletions (by users or by auto-mod)
• Member Bans/Kicks
• Member Joins/Leaves
• Role Changes
• Channel Updates

With this running, you'll have a searchable record of all major actions. It answers the "who did what and when" questions instantly. This logging is a cornerstone of professional Discord moderation bot setup. For a deeper understanding of the permission system that underpins all of this, it's worth reviewing how Discord server permissions work at a fundamental level.

Step 5: Final Testing and Community Onboarding

Your bot is configured. But would you launch a spaceship without a pre-flight check? Don't launch your bot without one either. This phase is about confidence and communication.

Going Live with Confidence

Enlist a trusted user (not an admin) to help you stress-test. Have them try to post a banned word, spam a few messages, or post a blocked link. Watch the logs. Did the bot catch it? Did it apply the correct punishment? This real-world test uncovers misconfigurations that staring at a dashboard never will.

Now, tell your community. Create a public #rules or #info channel. Briefly explain that an auto-moderation bot is active to keep the server safe. List a few key points: "Automated filters for spam and harmful links are on," "Please don't try to evade word filters," and maybe a command like !report for issues the bot misses.

Finally, put a recurring calendar reminder to review your setup. Every month or two, glance at the logs. Are the same users being warned for the same thing? Maybe a rule needs adjusting. Is a filter never triggering? Maybe it's not needed. Your bot should evolve with your server.

You're Ready for Takeoff

Setting up a Discord moderation bot isn't a one-click fix. It's a process. You've selected the right tool, invited it securely, built a proper permissions structure, programmed its automated reflexes, given it a memory via logs, and tested the whole system. The result? You've traded constant manual oversight for strategic oversight. You get your time back. Your community gets a cleaner, safer space to grow.

Remember, the bot is your tool, not your replacement. It handles the predictable so you can focus on the human, unpredictable, and wonderful parts of building an online community. Now go enjoy it.