How to set up a Discord server (complete 2026 guide)

Creating a Discord server takes ten seconds. Setting it up so that people stay, find their way around and can’t wreck it on day one takes a plan. This guide walks through how to set up a Discord server in the order that actually works: structure first, then permissions, then the people-facing parts (rules, verification, welcome, self-roles), and finally the systems that keep it running (moderation, tickets, levels). Most of it is plain Discord advice that works with any bot; where BotGG saves you time, it says so.

Step 1: Create the server and decide what it is for

In the Discord app, click + (Add a Server) at the bottom of the server list, choose Create My Own, pick “For a club or community” or “For me and my friends”, then set a name and an icon. You can change both later.

Before adding a single channel, write down three things:

• Who it is for — a friend group, a public gaming community, a clan, a creator’s audience, a study group, a customer support server.
• What people will do there — chat, find teammates, get help, follow announcements, play voice games.
• Who helps you run it — just you, a couple of friends, or a real staff team.

These answers decide how many channels you need, which roles exist and how strict the entry should be. A ten-person friends server needs none of the moderation tooling below; a public server with a link on social media needs all of it from day one.

Step 2: Plan channels and categories

The most common mistake is too many channels. Empty channels make a server feel dead, so start small and add channels when an existing one gets crowded.

A layout that works for most communities:

Tips that save you trouble later:

• Set permissions on the category, then keep channels synced. A channel inherits its category’s permissions until you change them; one deny on the category is easier to maintain than twenty per-channel overwrites.
• Make info channels read-only by denying Send Messages for @everyone and allowing it for your staff role.
• Hide staff channels by denying View Channel for @everyone on the Staff category and allowing it for staff roles.
• Use temporary voice channels instead of ten empty “Voice 1–10” channels — see the temporary voice channels guide.

Skip the busywork: server templates

If you don’t want to build this by hand, BotGG has ready-made server templates for gaming communities, esports teams, MMO guilds, creator communities, support servers, study groups, small businesses and roleplay servers. A template creates categories, channels, roles and permissions, and turns on the matching BotGG features with sensible settings. Each one is available in English, Russian and Hebrew.

You apply a template from the console in two modes: Add to my server only creates what is missing and never changes or deletes anything, while Fresh setup replaces your channels with the template (your roles stay, and a safety backup is taken first). Either way you see a full preview of every change before anything happens, and applying is free.

Step 3: Build roles and permissions

Roles are how Discord decides who can do what. Keep the list short and ordered by power:

1. Owner / Admin — a very small group. Only these roles get Administrator, if any role gets it at all.
2. Moderators — Kick, Ban, Timeout Members, Manage Messages. No Administrator, no Manage Roles unless they really need it.
3. Bots — each bot gets its own managed role when you invite it; place it where it needs to be (see below).
4. Special members — boosters, VIPs, content creators.
5. Self-roles — game pings, regions, colors, notification roles. No permissions at all.
6. @everyone — the baseline for every member.

Three rules that prevent most disasters:

• Permissions are additive. If any of a member’s roles allows something, they have it — unless a channel overwrite denies it. Give power through a few roles, not a pile of them.
• Role order matters. A member (or bot) can only manage roles that are below their own highest role. A bot that gives out roles must sit above those roles in Server Settings → Roles.
• Administrator skips every check, including channel overwrites. Treat it like the server’s master key. The anti-nuke guide explains how to keep dangerous permissions in few hands.

Step 4: Rules and Discord’s community features

Write short rules — five to ten points people can actually read — and pin them in a read-only #rules channel. Then open Server Settings → Enable Community. A Community server unlocks:

• Rules screening and Onboarding — new members see your rules and can answer onboarding questions before they get in. Onboarding questions can also give roles and decide which channels a member sees.
• Welcome screen, announcement channels and Server Insights.
• Safety Setup — Discord’s verification level, explicit media filter and DM spam settings.

Set the verification level to at least Low (verified email) or Medium (account older than five minutes) on any public server. It costs nothing and filters the laziest spam accounts.

Step 5: Add verification

Discord’s verification level can’t tell a bot farm with verified emails from a real person. A verification bot can: BotGG Verification keeps new members in a single #verify channel until they click a button, accept the rules, solve an image captcha or answer a few questions. You can add a minimum account age, a deadline and manual approval by staff for private communities.

The console has a setup wizard that creates the Unverified role and the #verify channel and hides every other channel from unverified members for you. The verification guide covers which method to choose for which kind of server.

Step 6: Welcome new members

A good welcome message tells people where to go next, not just “hello”. With BotGG Welcome messages you post a greeting with an optional image card in the channel of your choice and, if you like, a DM. Placeholders such as {user}, {server} and {count} keep it personal, and a goodbye message is available too.

If you use verification, turn on wait for verification so the greeting fires when someone passes the check — not when a bot joins and never verifies. The welcome message guide has examples that work.

Step 7: Let members pick their own roles

Self-roles keep your server organized without staff work: members choose which games they play, which notifications they want, their region or a name color. That decides what they see and who they get pinged with.

Discord’s Onboarding questions can give roles when someone joins. To let members change them at any time, post a role menu: BotGG Role menus support buttons, select menus and classic reactions, with modes like “only one role from this menu” for colors and regions. The free plan includes 3 menus per server. The reaction roles guide walks through it.

Step 8: Moderation and protection

Even small servers get spam once the invite link is public. Set up three layers before you advertise the server:

1. AutoMod — Discord’s built-in filters plus BotGG Moderation rules for spam, invites, links, mass mentions, caps and bad words, with warnings that escalate to timeouts or bans. See the AutoMod setup guide.
2. Anti-raid — when dozens of accounts join at once, BotGG locks your channels, holds newcomers and alerts staff, then lifts the lockdown after things calm down.
3. Anti-nuke — if a staff account is hacked or a moderator goes rogue and starts deleting channels or banning members, BotGG stops that member and alerts you.

Add a private #mod-log channel and turn on Logs so staff can see deleted messages, joins, leaves and role changes. And enable Require 2FA for moderator actions in Server Settings → Safety Setup — it means a stolen password alone can’t be used to ban your members.

Step 9: Support with tickets

Once the server has more than a few dozen members, questions and reports in #general get lost. A ticket system gives every request its own private channel or thread between the member and your staff. BotGG Tickets adds a panel with a button or menu, optional forms, staff roles, transcripts and feedback after closing. The free plan includes 3 panels. Follow the ticket system guide to set it up in about fifteen minutes.

Step 10: Keep people coming back

Activity is what makes a server feel alive. A few systems that work without constant staff effort:

• Levels — XP for chatting and voice time, rank cards, a leaderboard and role rewards at certain levels. See the leveling system guide and Levels.
• Events and giveaways — scheduled events in Discord plus Giveaways with entry requirements.
• Suggestions and polls — let members shape the server with Suggestions and Polls.
• Starboard — the best messages, picked by the community’s reactions, in one channel with Starboard.

Don’t switch everything on at once. Add one system, see whether people use it, then add the next.

Launch checklist

For the last-but-one point, BotGG Backups snapshots your roles, channels and permissions so you can restore them later.

FAQ

How many channels should a new Discord server have?

Fewer than you think. Around eight to twelve channels is plenty for a new community: info, general chat, one channel per major topic, a voice channel or two and a hidden staff area. Add more when a channel gets too busy.

Is it better to use a server template?

A template saves an hour of clicking and gives you sensible permissions from the start. Discord’s own templates copy channels and roles; BotGG server templates also set up the bot features (welcome, levels, tickets, moderation) to match.

What permissions should moderators have?

Kick Members, Ban Members, Timeout Members, Manage Messages and, if they handle threads, Manage Threads. Avoid Administrator and Manage Roles for regular moderators — those are the permissions attackers abuse when a staff account is compromised.

Do I need a bot to run a Discord server?

Not for a small private server. For a public community, a bot covers what Discord doesn’t do on its own: captcha verification, welcome cards, self-role menus, tickets, levels, anti-raid and anti-nuke protection. BotGG does all of these in one bot, most of it on the free plan — see pricing.