Discord server setup checklist
Updated · Setup
Do it in this order: structure (channels and roles), Community and safety settings, onboarding, rules and welcome content, bots, then a test with a second account. Skipping the test is the most common mistake; it's how private channels end up visible and new members end up seeing nothing.
| Phase | Must do | Where |
|---|---|---|
| 1. Structure | Categories, 8-15 channels, 4-6 roles | Server menu > Create Channel / Server Settings > Roles |
| 2. Community | Enable Community, rules + updates channels | Server Settings > Enable Community |
| 3. Safety | Verification level, AutoMod rules, 2FA for moderators | Server Settings > Safety Setup |
| 4. Onboarding | Questions, default channels, Server Guide | Server Settings > Onboarding |
| 5. Content | Rules, welcome post, pinned FAQ, first announcement | #rules, #start-here, #announcements |
| 6. Bots | Only what you need: tickets, roles, paid access, logging | Each bot's dashboard |
| 7. Test | Join with an alt account, check every channel | Second Discord account |
| 8. Launch | Invite link, seed first conversations, schedule an event | Server menu > Invite People / Events |
Structure
- Server name, icon and description that say who it's for
- Categories: Start Here, Community, Help, Live, Staff
- Read-only #announcements and #rules
- A forum channel for questions
- Roles: Admin, Moderator, Member, plus tier/cohort roles; bot roles near the top
- Private staff channel with View Channel denied for @everyone
Settings and safety
- Community enabled
- Verification level at least 'verified email'
- Explicit media content filter on
- Default notifications: Only @mentions
- AutoMod: spam, mention spam, commonly flagged words, custom keywords
- Require 2FA for moderator actions (Safety Setup)
- @everyone cannot mention @everyone/@here
Content
- Rules (see the rules template)
- Welcome post: who it's for, what to do first, where to ask for help
- Introductions prompt pinned in #introductions
- First announcement and first scheduled event
Bots (only what you need)
Every bot is another set of permissions. Give each the minimum it asks for, not Administrator.
- Paid access: Whop or LaunchPass if you charge
- Tickets: Ticket Tool if you offer 1:1 support
- Roles/logging/automod extras: Carl-bot or Dyno
- Events and reminders: Sesh
Test before launch
- Join with a second account that has no roles.
- Go through onboarding; confirm the right roles and channels appear.
- Try posting in #announcements and #rules (should fail).
- Confirm staff and paid channels are invisible.
- Post a banned keyword to check AutoMod.
Quick answers
- How long does it take to set up a Discord community properly?
- With a good template, a few hours. From scratch with bots, onboarding and testing, usually a day or more.
- What is the easiest way to make a Discord server look professional?
- Fewer channels with clear names, a matching icon and banner, read-only announcements and rules, a short onboarding flow, and a welcome post that tells people exactly what to do first.
- What bots should a community Discord server have?
- Often none at first. Add one only for a job Discord can't do natively: paid access, tickets, reaction roles, logging or event reminders.
- Is there a done-for-you Discord server setup service?
- Yes. Our done-for-you setup builds the whole checklist for you; see the pricing page for what's included.
What to do next
Want the checklist done for you? We build the server, roles, onboarding, rules and bots and hand it over tested.
Related guides
Sources
- Discord Help Center
- Discord Help Center: Enable Community
- Discord Help Center: AutoMod
- Discord Safety Center
Checked: . Discord changes features and menus often; if something looks different, the official help center is the source of truth. LaunchMyServer is not affiliated with Discord.