How to set up a Discord server that scales from 10 to 10,000 members
A seven-channel layout, category permissions, a six-role ladder and Community, Onboarding and AutoMod settings that carry a Discord server from a friend group to a large community.
If you want to know how to set up a Discord server that will not need rebuilding at 1,000 or 10,000 members, get four things right on day one: a small channel layout grouped into categories, permissions set on categories rather than channels, a six-step role ladder with Administrator given to almost nobody, and Community features turned on early so Onboarding, Rules Screening and AutoMod do the gatekeeping instead of a bot. Everything else can be added later without moving a single permission.
Day one: server type and the defaults to change immediately
Press the Add a Server icon in the server list, choose Create My Own or a template, then pick between "For a club or community" and "For me and my friends". The choice is not binding; a friend server can opt into Community later from Server Settings.
Two defaults are worth changing before you invite anyone. New Discord servers start with notifications set to all messages; switch the default to only @mentions at the bottom of Server Settings → Overview, which Discord requires of verified servers because all-messages becomes unbearable past a few hundred people. And create one permanent invite for your own use now, so you are not sharing expiring links later; see how to make a permanent Discord invite link.
A minimal channel layout that survives growth
Discord caps a server at 500 channels, 50 categories and 50 channels per category, and no healthy server gets near those numbers. Start with three categories and seven channels:
- Start here:
#welcome-rules(read-only, becomes your rules channel) and#announcements(read-only, converted to an Announcement channel once Community is on). - Talk:
#general,#mediaand#off-topic, or swap one for a topic channel that matches your niche. - Voice:
GeneralandLounge, the second with a user limit so groups split naturally. - Staff (private):
#mod-chat, later joined by#automod-alerts.
Add a Forum channel for questions, or an LFG channel, only when people ask. Forum, Announcement and Stage channels need Community, and Server Templates do not carry them across, so they sit outside anything you clone.
Name channels after the action, not the vibe: #introduce-yourself beats #the-lobby. Discord's own welcome guidance makes the same point, and it matters more once Onboarding puts channel names in front of people who have never seen your server.
Permissions: set them on categories, and the one @everyone mistake
Discord resolves channel permissions in a fixed order: server permissions as the base, then @everyone denies and allows on the channel, then all role denies and allows summed together, then member-specific overrides. Channel overrides beat server settings, and a channel that is synced to its category inherits every change you make to the category. Edit the category, keep channels synced, and you will never chase permissions across 40 channels.
To make the Staff category private, open Edit Category → Permissions, deny View Channel for @everyone and allow it for Moderator; on a single channel the Private Channel toggle does the same in one click. Members need View Channel, Send Messages and Read Message History to chat in a text channel, so those three stay on for @everyone in public categories.
The mistake: treating @everyone as an "unverified" role, denying it everything, then handing access back with a bot. @everyone is the template every new role copies, so every role you create afterwards starts broken, and Onboarding refuses to publish unless at least five default channels let @everyone view and send messages. Discord's Rules Screening FAQ says the same thing from the other side: if you had a bot role gate, re-enable @everyone permissions when you turn screening on. Gate with Rules Screening and the verification level, not with @everyone.
The one permission you should take away from @everyone is Mention @everyone, @here, and All Roles. Discord's raid guide lists that as step two of raid prevention and recommends leaving it only on trusted roles.
The role ladder
Roles resolve top-down. A member can only act on people whose highest role sits below their own, and nobody can kick, ban or rename someone of equal or higher rank whatever their permissions say. Manage Roles only lets someone edit roles below their own, and only grant permissions they already hold. Discord allows 250 roles, so there is room for colour and notification roles beneath this ladder.
| Role | Key permissions | Notes |
|---|---|---|
| Owner | Everything, always | Discord never requires the creator to hold a role; secure the account with MFA |
| Admin | Administrator |
One or two people you would trust with the server; it bypasses every channel override |
| Moderator | Kick Members, Ban Members, Time Out Members, Manage Messages, Manage Threads, Manage Nicknames, View Audit Log, Bypass Slowmode |
No Manage Roles, no Manage Server, no Administrator |
| Trusted | Attach Files, Embed Links, Create Public Threads, Move Members, Bypass Slowmode |
Regulars and helpers; grant after weeks, not days |
| Member | View Channel, Send Messages, Read Message History, Add Reactions, Connect, Speak |
Assigned by an Onboarding question, or simply @everyone plus screening |
@everyone (unverified) |
Same as Member on default channels, minus mentions and Create Invite if you want those earned |
Pending members are already blocked from talking, reacting and DMing by Rules Screening |
Two notes on the table. Time Out Members is the permission behind timeouts of 60 seconds to one week, and AutoMod can apply them too, which is why Moderator needs nothing heavier for daily work. Bypass Slowmode is now its own permission; the old Manage Messages, Manage Channel and Manage Threads bypass only lasted until 23 February 2026, so older role setups need the toggle added.
Enabling Community and what it changes
Go to Server Settings → Enable Community → Get Started. Discord asks for four things: a verification level requiring a verified email, the explicit media filter scanning all members, a rules channel and a moderator-only Community Updates channel. Community servers get the High explicit media filter by default.
What changes once it is on:
- Invite links for Community servers never expire.
- Announcement channels, Forum channels, Onboarding, Server Guide, Rules Screening and Raid Protection unlock. Announcement publishes are limited to 10 per hour.
- Server Insights appears once you pass 500 members, behind the
View Server Insightspermission. - The Members page moves to a tab above the channel list; on friend servers it lives in
Server Settings → Members. - The old Welcome Screen is frozen. Discord says you can no longer edit it and recommends Onboarding instead.
- Discovery becomes possible later: 1,000 members, eight weeks of age, activity requirements and the 2FA requirement for moderation.
Community also means agreeing to the Community Server Guidelines: an accurate name and description, posted rules and a moderator team. That reads like a directory checklist because it is one; our checklist before listing covers the same ground.
Onboarding: default channels and customisation questions
Open Server Settings → Onboarding (desktop only; you need Manage Server plus Manage Roles, or Administrator). Onboarding has three parts.
- Default channels. Pick at least seven, and at least five must let
@everyoneview and send messages. The seven-channel layout above meets this with#welcome-rules,#announcements,#general,#media,#off-topicand the two voice channels. - Customisation questions. Each answer grants channels and/or roles. Discord suggests "What would you like to do here?" for main channels, a separate question for off-topic channels, and no more than about six answers per question. Mark a question
Ask before a member joinsandMake Requiredwhen it assigns important channels; leave both off for vanity roles, which then live in the Channels & Roles tab. - Server Guide. A welcome sign, three to five new-member to-dos, and Resources, which turn read-only channels like your rules into pages that open at the top rather than at the last message.
Do not put rules in the questions; members accept rules separately through Rules Screening. Members who leave and rejoin go through Onboarding again, which is useful when you are cleaning up after a raid.
AutoMod, voice defaults and the first bot
Turn on AutoMod at Server Settings → AutoMod before you have the members to need it. Enable the three Commonly Flagged Words lists (English only), Block Spam Content, and Block Mention Spam with a limit well under the maximum of 50. Add one Custom Keyword rule for invite links and your niche's scam phrases; each rule takes up to 1,000 terms of 60 characters, wildcards such as *word* included. Send alerts to #automod-alerts in the private Staff category. Members with Administrator or Manage Server are always exempt, and rules can only be edited on desktop. Under Server Settings → Safety Setup → Raid Protection, turn on alerts; when Discord detects a join raid it requires CAPTCHA from new joiners for the next hour.
Voice channels need little. Leave the region on Automatic; Discord picks it from the first person to join and only changes it once the channel empties. Audio quality is capped at 96 kbps until the server is boosted (128 kbps at Level 1), and pushing the bitrate higher hurts people on weak connections. Set a user limit (up to 99) on lounge channels, and remember that text chat inside a voice channel needs Send Messages and Read Message History like any other channel.
Add your first bot when a human is doing something repetitive, not before. For most servers that is reaction roles, logging or a ticket flow, which is why carl-bot is usually first (see its listing); our guide to which bots a new server needs covers the rest and what to skip.
Try it: when the layout, ladder and Onboarding are in place, list your server on Discordfinder. Listing is free, and the read-only bot counts message volume only, never message content.