Guide · Rules as Code
Discord rules accept button: make members accept your rules (and re-accept after changes)
How to make Discord members accept the rules with a button, keep rules numbered and versioned, ask again after big changes and cite rule numbers when moderating.
Rules as CodeVerificationModerationWelcome messages
On this page
A Discord rules accept button is a button under your rules — usually “I accept the rules” — that members press before they get access to the rest of the server. Pressing it gives them a role, and that role is what unlocks the chat channels. It’s the simplest way to make sure every member has at least seen the rules, and it gives you a record: who accepted, and which version of the rules they accepted.
This guide shows how to set up a rules gate with Discord’s own tools, where those tools stop, and how BotGG’s Rules as Code adds numbered, versioned rules with an accept button, re-acceptance after major changes and rule numbers in /warn, /timeout, /kick and /ban. If you still need the rules themselves, start with the Discord server rules templates and come back.
Why make members accept the rules
A #rules channel that nobody reads doesn’t protect anyone. Making acceptance a step on the way in changes three things:
- Members actually see the rules. They can still skim, but they can’t say they never saw them.
- Moderators get a fair starting point. “You accepted rule 3.2 when you joined” ends a lot of arguments.
- Simple bots are slowed down. A button isn’t a captcha, but join-and-spam scripts that never click anything stay locked out.
The catch is change. Rules evolve — you add a voice-chat rule, tighten self-promotion, drop an outdated one. An acceptance from last year was for different rules. A good setup lets you ask members to accept again when the rules change in a meaningful way, without bothering them for every typo fix.
How to set up a rules gate with Discord’s tools
You can build a basic gate without any bot. It takes a role, a channel and some permission work:
- Create a “Member” role with no special permissions. This will be the role that unlocks the server.
- Lock the server for @everyone. In each category, remove View Channel from @everyone and allow it for Member. Leave only #rules (and maybe #welcome) visible to @everyone.
- Make #rules read-only. @everyone can view and read history, but not send messages, create threads or add reactions you don’t want.
- Post the rules as one numbered list — see the templates.
- Decide how members get the role. Discord’s own option is Rules Screening in Community servers (members agree before they can talk, and Onboarding can show a server guide). The other common approach is a reaction role or a button from a bot.
Where native tools stop
| Need | Native Discord | What you need on top |
|---|---|---|
| Members agree before talking | Rules Screening (Community servers) | — |
| Rules with stable numbers staff can cite | Plain text you number yourself | Numbered rules that renumber safely |
| Version history of the rules | No | Versions with a diff |
| Ask everyone again after a big change | No practical way | Re-acceptance per major version |
| See who accepted which version | No | Acceptance records and stats |
| Rule number on warnings and bans | Typed by hand in the reason | A rule picker in moderation commands |
Rules Screening is a good filter, but it gives you no version history and no way to link a warning to a specific rule. That’s the gap a bot fills.
Tips for any accept button
- Keep the button under the last rule, not above it, so members scroll past the rules first.
- Give one role, not five. One acceptance role that unlocks the chat keeps permissions readable.
- Make sure the bot’s role is above the acceptance role, or it can’t give it.
- Don’t ask for acceptance on every edit. Fixing a typo is a minor change; adding or rewording a rule is a major one.
- Mention #rules in your welcome message so newcomers know where to start.
Rules as Code: numbered, versioned rules in BotGG
Rules as Code is BotGG’s rules editor. Instead of one long message, your rules are a structured document: sections with numbered rules (1.1, 1.2, 2.1…), each with a title, a text, an optional severity (low 🟢, medium 🟡, high 🟠, critical 🔴) and an optional suggested action (warn, timeout with a duration, kick or ban). Up to 30 rules on the free plan and 200 on Pro.
The feature is off by default; once you enable it, the /rule command appears on your server.
Step 1: Write the rules
- Open https://console.botgg.app, choose your server and in the sidebar under Moderation open Rules as Code.
- On the Editor tab, fill in the header: Title, Introduction and Footer.
- Add section for each group of rules (General, Chat, Voice…) and Add rule inside it. Drag rules to reorder them — the numbers update by themselves.
- Watch the live preview next to the editor: it shows exactly what the bot will post, in the bot’s language.
The draft saves automatically. Nothing changes in Discord until you publish.
Step 2: Pick the rules channel and the accept button
On the Settings tab:
- Rules channel — a read-only channel works best. BotGG needs View Channel, Send Messages and Embed Links there.
- Ask members to accept — adds the I accept the rules button under the last message. You can change the Button label.
- Role on acceptance — the role that unlocks your chat channels (BotGG’s role must be above it).
- Show severity to members and Show suggested actions to members — decide how much members see. Staff always see the suggested action when they pick a rule.
When a member presses the button, they get a private confirmation such as “Thanks — you accepted the rules (v1.0)” and the role.
Step 3: Publish
Press Publish. The first version is always 1.0. BotGG posts a header embed and one embed per section in the rules channel, with the version in the footer. Later publishes edit the same messages in place — no reposting, no notification spam. If someone deletes the messages, Post again sends the whole set again.
Step 4: Change the rules without losing track
Edit the draft whenever you like, then publish again. The Publish dialog shows what changed since the last version — rules added, removed, reworded, renumbered — and lets you add a note.
- Major change bumps the version to 2.0, 3.0… The dialog suggests it when rules were added, removed or reworded.
- A minor change (1.1, 1.2…) is for fixes and clarifications.
A member counts as having accepted when they accepted the current major version. Turn on Remove the role after a major version, and members who haven’t accepted the new version lose the acceptance role until they press the button again; the role is removed gradually, and the console shows the progress. The Versions tab keeps the full history: open any version to see its rules and diff, or Restore to draft to roll back.
| Change | Version | Members must accept again? |
|---|---|---|
| Typo, formatting, a clearer example | Minor (1.0 → 1.1) | No |
| New rule, removed rule, rule reworded | Major (1.1 → 2.0) | Yes |
| Severity or suggested action changed | Usually major (suggested) | Yes, if published as major |
Use the rules in verification
If you already use BotGG Verification, you don’t need a second gate. In Verification → Method, choose Rules and set Where the rules come from to Rules as Code. Newcomers then see your published, numbered rules in the verification step, and accepting there counts as accepting your Rules as Code version too. If Rules as Code is off or nothing is published yet, Verification shows its own list instead.
Pair it with a welcome message that waits for verification, and newcomers are greeted only after they’ve accepted. The verification guide covers captcha and account-age gates if you also need protection against raids.
Cite rules when you moderate
Once rules are published, BotGG’s /warn, /timeout, /kick and /ban get an optional rule: option with autocomplete from the published version — for example “3.2 No spam · ⚖️ timeout 1h”. Staff pick the rule instead of typing it:
- Without a typed reason, the reason becomes “Rule 3.2: …” automatically.
- The case remembers the rule and the version it was cited from, and the mod log shows a Rule field.
- With Quote the rule in moderation DMs, the member’s DM shows the rule number, title and text.
Members (and staff) can look up a single rule with /rule number:3.2 (add private to see it only yourself). For the full set of moderation commands, see the moderation commands guide.
The Stats tab then shows which rules are broken most, cases citing a rule per day, and how many members accepted the current major version — with a data table for every rule and action. Flows can start on “Rules published” or “Rules accepted” and use the “Publish rules” action.
Checklist
- Rules written as numbered sections, each rule one idea
- Read-only rules channel, acceptance role that unlocks chat
- Bot role above the acceptance role
- Accept button on, role set, first version 1.0 published
- Major changes published as major; minor fixes as minor
- “Remove the role after a major version” on if acceptance must stay current
- Staff told to use the
rule:option in moderation commands
FAQ
How do I make members accept the rules before chatting on Discord?
Hide every channel except #rules from @everyone, give an acceptance role permission to see the chat, and give that role when members accept — through Discord’s Rules Screening, or a button like BotGG’s I accept the rules.
Do members have to accept again when I change the rules?
Only when you publish a major version (2.0, 3.0…). Minor versions don’t ask again. With “Remove the role after a major version” on, members who haven’t accepted the new version lose the role until they do.
Will editing the rules repost the messages and ping everyone?
No. BotGG edits the existing messages in the rules channel in place, so the channel stays clean and nobody gets a new notification.
Can I use the same rules in verification?
Yes. Set Verification’s rules method to Rules as Code and newcomers see the published rules there; accepting in verification also counts as accepting the rules.
What does the button need to work?
A published version, a rules channel where BotGG can view, send and embed links, and — if you give a role — BotGG’s role placed above that role.