Most new servers die from clutter: twenty channels, no structure, no gate, no reason to speak. This checklist is the opposite, the minimum that makes a server feel alive and safe on day one, in the order you should do it. Each step takes a few minutes; the whole list fits in an evening.
1. Decide what the server is for
Write one sentence before you create a single channel: "A place for X to do Y." A community for a game, a shop for digital goods, a support server for a product, a study group. Everything below follows from it. A shop needs tickets and a catalog early; a hangout needs a good welcome flow and voice channels; a support server needs a clear way to ask for help and nothing else.
2. Channels: start with seven
- #rules and #announcements: read-only for members.
- #general, #introductions, #media: where people actually talk.
- #support: the ticket panel lives here, so help requests never clutter #general.
- One voice channel. Add more only when these overflow.
Group them in three categories: Info (rules, announcements), Community (general, introductions, media, voice) and Help (support). Categories carry permissions down to their channels, which saves you from setting every channel by hand later. Name them consistently; the channel name generator keeps the style uniform, and the server structure generator drafts a full layout for your server type.
3. Roles: three tiers, then stop
Admin, Moderator, Member (given at verification). Colour them so the hierarchy is visible, and test the colours against dark mode with the role colour previewer. Cosmetic and reward roles come later, once people are around to earn them.
Order matters: a role can only manage roles below it. Put your bots' roles just under Admin, above Moderator, or they will fail to give out roles or time members out. Plan the order before you have thirty roles with the role hierarchy planner.
4. Permissions: deny at the top, allow where needed
- @everyone: View Channel only on #rules and the verification channel. Nothing else until they verify.
- Member: View, Send Messages, Read History, Add Reactions, Connect and Speak in the community category.
- Moderator: add Manage Messages, Timeout Members and Kick. Keep Ban and Manage Roles for admins.
- Never give Administrator to a role that more than two or three trusted people hold.
The permissions calculator shows exactly what a permission number grants, which helps when a bot asks for one at invite.
5. Security before invites
- Server Settings, Moderation: verification level Medium, and require 2FA for moderator actions.
- Turn on Discord AutoMod: mention spam, common spam words and unknown invite links.
- Add a verification gate so new accounts must press a button before they see the server. See verification and welcome setup.
- Turn on anti-nuke so a compromised staff account cannot mass-ban or delete channels. See anti-nuke and the raid protection playbook.
6. Rules people actually read
Seven short rules beat a legal document. Each rule should say what to do, not just what not to do, and the last one should say what happens when someone breaks them. Generate a clean starting set with the rules template generator, edit it to fit, and pin it.
7. The welcome flow
New members decide in the first minute whether they stay. Give them one clear next step: a welcome message that names #introductions, plus the Member role the moment they verify. Draft it with the welcome message generator, then set it up with Noxyr's welcome module. Turn on Discord's Community features for the welcome screen and onboarding questions.
8. A place to ask for help
Questions in #general get buried and staff answer the same thing ten times. A ticket panel in #support opens a private channel per request, so nothing is lost and every answer has a record. Follow how to set up a ticket system or go straight to the ticket docs.
9. Logs you will need later
The day something goes wrong is the day you wish you had logs. Make one private #mod-log channel for staff only, and send message deletes, edits, joins, leaves and moderation actions there. Check the audit log weekly, or let security alerts watch it for you.
10. One bot, not six
Every bot is a permission surface, another dashboard and another thing that can go offline. Noxyr covers tickets, welcome, verification, security, giveaways, a store and moderation in one; start there and add specialists only for real gaps. Getting started takes two minutes.
11. The settings everyone forgets
- Turn off "Mention @everyone, @here and All Roles" for the Member role.
- Set an AFK channel and an inactive timeout.
- Default notifications to "Only @mentions", or big servers become unbearable.
- Upload a server icon and banner; the icon previewer shows how it looks at small sizes.
- Write a short server description for invites and Discovery with the description generator.
Launch checklist
- Join from a second account and walk through it as a new member: can you verify, read the rules and find #general in under a minute?
- Try to post in #rules as a member. You should not be able to.
- Open a test ticket and close it.
- Check that every bot role sits above the roles it manages.
- Create one permanent invite link with no expiry for your website and socials.
FAQ
How many channels should a new Discord server have?
Seven to ten. Empty channels make a server look dead; add a channel only when an existing one is busy enough that two conversations keep colliding.
Should I make the server public right away?
No. Invite ten to twenty friends or customers first, so the first strangers find people already talking. Apply for Discovery once you have steady daily activity.
Which bot permissions are safe to give?
Give a bot only what its features use, not Administrator. A good bot lists the exact permissions it needs and tells you when one is missing.
How do I stop raids on a new server?
Verification level Medium, a button verification gate, AutoMod for mention spam and anti-nuke for staff accounts. Those four stop almost every raid on small and mid-size servers.