Discord Server Rules: How to Write Rules Members Read and Mods Can Enforce

A single soft rule such as 'be nice' or 'be respectful' feels welcoming, but it does not tell anyone where the line is. Most members never test it. The few who do can stay technically polite while still causing trouble, for example with unwanted criticism of other people's work phrased as questions, repeated self-promotion, or taking over someone else's introduction thread.

When that happens, moderators have nothing concrete to point to, and the person causing the problem can say they broke no rule. Quieter members notice that nobody steps in and post less. Specific rules fix this: they give moderators a clear basis for action and show members that someone is looking after the space.

Cover the areas where problems actually happen in your server. For most communities that means: how members treat each other (harassment, discrimination, personal attacks), what content is allowed (NSFW, spoilers, links, file sharing), self-promotion and advertising, where things belong (which channels for what), voice chat conduct, and what happens when someone breaks a rule.

Point to Discord's Community Guidelines as the baseline instead of copying them. Your own rules should add what is specific to your community, for example feedback etiquette in an art server or spoiler handling in a gaming server.

Write each rule as a behavior, not a value. 'Be respectful' is a value. 'No criticism of someone's work unless their post asks for feedback' is a behavior a moderator can check.

Keep the list short enough to read in one go, number the rules so moderators can refer to them ('rule 3'), and add one short reason where a rule is not obvious. A reason helps members understand the rule and apply it to cases the text does not name.

Write in plain language. Rules that read like terms of service get skipped. If a rule needs a paragraph of explanation, it is probably two rules.

Put the rules in a dedicated, read-only rules channel. If you want to enable Community features, Discord requires a clearly posted rules or guidelines channel anyway.

Community servers can also use Rules Screening: members must agree to the rules before they can talk, react or DM other members. You set it up under Server Settings, Safety Setup, and you can create up to 16 rules there. Discord recommends it over bot-based role gates, but also warns that it adds a step to joining, which can lead to some people not finishing it.

So a gate is a trade-off, not a default. A server that attracts spam or raids may want one. A small, friendly server may do better letting people look around first and linking the rules in the welcome message. BuildMyDiscord's free verification system is one bot-based option: it creates a rules channel and a verify channel where a button gives the member a Verified role. The verification guide compares the approaches.

Publish the steps, then follow them the same way for everyone. A common ladder is a warning, then a time out, then a kick, then a ban, with the option to skip steps for severe cases such as threats or illegal content.

Discord's Time Out stops a member from sending messages, reacting and joining voice channels while they can still read. Moderators can choose 60 seconds, 5 minutes, 10 minutes, 1 hour, 1 day or 1 week, and the reason is recorded in the audit log. AutoMod can also time out members based on the filters you set up.

Keep a short log of actions so the whole mod team applies the rules consistently, and give members a way to appeal. The moderation guide goes deeper into running a mod team.

Revisit the rules when the same kind of incident keeps happening without a rule that covers it, or when a rule is never used. Announce bigger changes and say why they were made.

As the server grows, some channels may need their own rules, such as stricter tone in a help channel than in off-topic. Put those in the channel description so they are visible where they apply.