Answer first
What to know
- Useful server rules are short, specific to the community, and paired with a response your moderators can apply consistently.
- Copy the ten-rule template below, then replace its examples, reporting path, and content boundaries with details members will recognize.
- Discord's Community Guidelines still apply. Your server rules add the expectations that are specific to your space.
- Automation can handle objective patterns such as spam or mention volume, but context-heavy decisions still need human review.
The copy-and-adapt Discord server rules template
Copy the rules below into a read-only rules channel, then edit the bracketed text and examples for your community. Keep the final version short enough to scan. These are practical community rules, not legal advice or a replacement for Discord’s Terms of Service and Community Guidelines.
If the server structure is not ready yet, choose a practical channel and role layout first. The rules should point to channels and reporting routes that actually exist.
1. Follow Discord’s rules. Follow Discord’s Terms of Service and Community Guidelines as well as the rules of [server name].
2. Treat people with respect. Do not harass, threaten, target, or demean other members. Disagreement is allowed; personal attacks are not.
3. Do not spam, scam, or mislead. Do not flood channels, send deceptive links, run scams, or promote something outside the places where promotion is allowed.
4. Protect people’s privacy. Do not share another person’s private information, private messages, or identifying details without permission.
5. Keep content appropriate for this community. Follow the content boundaries for [audience or topic]. Examples include [two or three non-exhaustive examples].
6. Use channels for their intended purpose. Read channel topics and pinned messages. Keep [off-topic content, support requests, promotions, spoilers, or other special cases] in the channels provided for them.
7. Do not impersonate or evade. Do not impersonate members or staff, use alternate accounts to avoid an action, or help someone bypass a restriction.
8. Follow reasonable moderator directions. If staff pause a conversation or move it elsewhere, cooperate in the moment. You can question the decision through [appeal or feedback route] afterward.
9. Report problems privately. Use [ticket command, report channel, or contact route] for reports. Do not start a public confrontation or retaliate against someone who reports a concern.
10. Actions depend on context. Moderators consider the behavior, severity, context, and relevant history. Responses may include a reminder, warning, timeout, removal, or ban. Appeal through [appeal route] if you think a decision should be reviewed.
This template was prepared from Discord’s published moderation guidance and is meant to be adapted. It does not cover every community, topic, or situation. A gaming server, professional support community, and adult community need different examples and content boundaries.
Adapt the template without making it vague
Replace every bracketed phrase. If a member cannot tell what a rule means in your server, the template is not finished.
Use a few concrete, non-exhaustive examples for rules that depend on local context. Discord’s moderation guidance notes that examples can clarify a rule, but a long list may look exhaustive and encourage people to treat everything omitted as acceptable. State the principle first, then add only the examples members genuinely need.
Small substitutions make the same structure useful for different communities:
- Gaming community: name where squad recruitment, spoilers, trades, and player reports belong.
- Creator community: define promotion, fan-content, spoiler, and live-chat boundaries.
- Support community: keep account, billing, and security details out of public channels and point members to a private support route.
Do not paste rules copied from another server without checking the tone, audience, channel names, and actions. A rule that no moderator can explain or apply consistently will not become useful because it sounds formal.
Decide how each rule will be enforced
Rules and enforcement are one system. Discord’s guidance describes several possible approaches, including case-by-case, infraction-based, and points-based models. None is automatically right for every server. Pick the lightest structure that helps your team make consistent decisions without ignoring severity or context.
| Rule type | Sensible first response | Human judgment needed? | Record to keep |
|---|---|---|---|
| Objective spam or mention volume | Block or slow the behavior, then alert staff | Usually low after careful testing | Matched rule, message context, action, time |
| Off-topic or misplaced content | Redirect or remind | Yes, especially around repeat behavior | Short note only when a pattern matters |
| Harassment or targeted behavior | Stop the immediate behavior and review context | High | Relevant evidence, reason, action, reviewer |
| Scam or deceptive link | Remove exposure and investigate | High | Link or evidence, affected channel, action taken |
| Dispute about a moderator decision | Move to the appeal route | High, preferably with another reviewer | Original reason, appeal, review outcome |
Avoid a universal three-strikes promise. A minor channel mistake and a severe incident should not be forced through the same ladder. Whatever model you choose, document actions consistently and make sure moderators use the same definitions.
Guardy Bot can connect configured moderation actions to numbered cases with reasons, attribution, and recovery controls. It does not decide what your community rules should be. Explore the Guardy Bot moderation workflow after your team has agreed on the policy.
Put the rules where members can find them
Use one read-only #rules channel as the durable source. Link to it from #start-here, the welcome message, and any onboarding guide. Keep temporary announcements out of the rules channel so members do not have to search for the current version.
Community servers can also use Discord Rules Screening. Discord says new members must explicitly accept the configured rules before they can talk, react, or directly message other members in the server. Rules Screening supports up to 16 rules and adds a step to joining. Agreement is useful, but it does not prove that someone understood every rule.
Native Discord AutoMod can help with configured keywords, suspected spam, and excessive mentions. Use it for patterns that can be described reliably. Tone, harassment, disputes, and many contextual decisions still need a person. The Discord AutoMod setup guide explains how to test rules and exemptions before relying on them.
Test the workflow before opening invitations
Ask someone using an ordinary member account and someone using a moderator account to run this check:
- Can a new member find the rules from the first channel they see?
- Does every rule use language the intended audience understands?
- Are promotion, sensitive reports, spoilers, and off-topic conversation routed somewhere clear?
- Does the private report or appeal path actually work?
- Do AutoMod tests catch the intended pattern without blocking ordinary examples?
- Can a moderator record a reason, find the relevant context, and reverse a test action?
- Can another moderator understand why the action was taken?
Repeat the check after a meaningful policy, channel, onboarding, or moderation-tool change. A short rule set your team applies predictably is more useful than a long document that nobody can operate.
If you are still choosing the operating layer around those rules, compare Discord moderation bots by workflow rather than by feature count alone.
Common questions about Discord server rules
How many Discord server rules should I have?
Use the smallest set that covers Discord-wide obligations and the recurring situations in your community. Discord Rules Screening currently supports up to 16 rules, but that is a technical ceiling, not a writing target. Combine overlapping points and move channel-specific details into channel topics or pinned messages.
Should every rule have a fixed punishment?
No. A predictable process matters, but severity, context, history, and uncertainty can change the right response. Tell members the kinds of actions moderators may take without promising that every first violation receives the same result.
Can AutoMod enforce all of these rules?
No. AutoMod is useful for configurable patterns such as keywords, spam, and mention volume. Context-heavy rules still need moderator review. Test every automatic response with an ordinary member account before relying on it.
What changes for a support or adult community?
The structure can stay similar, but the examples, privacy route, age or content boundaries, and channel rules must match the actual community. Use Discord’s current platform policies as the floor and obtain appropriate specialist review when rules touch legal, regulated, or high-impact subjects.
