Discord onboarding setup: how to welcome new members so they stay
Discord onboarding setup explained: what Discord requires, which questions to ask, and how to make new members feel at home in their first ten minutes.
Discord onboarding setup happens in Server Settings → Onboarding, and it is only available on Community servers. The tool asks new members a few questions and gives them the right channels and roles, but the settings are the small half of the job. The bigger half is what a person feels in their first ten minutes: do they know where to go, and does anyone answer them?
This guide covers both, with the focus on community practice rather than bot configuration.
What should onboarding do for a new member?
Someone who just joined has three quiet questions. Am I in the right place? What am I allowed to do here? Where do I say my first thing?
Good onboarding answers those three and stops. It does not teach the whole server. People learn your event schedule and your in-jokes by being around, so anything that is not needed in the first ten minutes can wait.
A useful test: ask a friend who has never seen the server to join while you watch their screen. Do not help. Where they hesitate is where your onboarding is broken, and that test tells you more than any settings page.
What does Discord require before you can turn it on?
Community Onboarding has a few fixed requirements, and the toggle stays unavailable until you meet them:
- Community must be enabled. The Onboarding tab appears after that. Our guide to the Discord Community server covers the requirements for that step.
- At least 7 default channels. These are the channels every new member sees in their channel list.
- At least 5 of those default channels must let @everyone view and send messages. A server made mostly of read-only channels has to open up a few.
- Permissions. You need Manage Server and Manage Roles, or Administrator.
- A computer. Discord only lets admins set this up on desktop.
Discord can change these rules. If the toggle is greyed out, the Onboarding screen shows what is missing.
How do you choose default channels?
Pick the channels where a newcomer can succeed without context. General chat, an introductions channel, a help or questions channel and one or two broad topic channels are usually right. Niche channels are better placed behind a question, so that only the people who care see them.
Two things to watch:
- Quiet defaults hurt you. If a default channel gets one message a week, a newcomer sees a dead room. Either make it a question-based channel or archive it.
- Do not create filler channels to reach seven. Announcements, rules and a server info channel can count if they fit the permissions rule, but empty channels made only to pass the check will look empty to everyone.
Which onboarding questions work best?
Each question should change what the person sees. If an answer does not lead to a channel or a role you actually use, drop the question. Two to four questions are plenty for most servers, and every extra one is a chance to lose someone.
Questions that usually earn their place:
- Why are you here? A game server might offer "looking for teammates", "just chatting" and "following tournaments". Each answer opens a different part of the server.
- Which game, topic or level? Useful when your server has clear sections, such as beginners and advanced players in a study server.
- What language or region? Helpful when voice sessions depend on time zones.
- Which pings do you want? This one protects your announcements. People who chose event pings are far less likely to mute the server.
Write answers in the member's words. "I want people to play with tonight" beats "LFG access". Keep the question about them, not about your structure. For the roles behind those answers, see our Discord role ideas.
Members can change their answers later from Channels & Roles, so nobody is locked into a first guess. Say so in your welcome message, since most people never find this on their own.
What about the human welcome?
Settings bring people to a channel. People keep them there. The strongest onboarding habit costs nothing: when someone posts for the first time, a real person replies within a reasonable time, and the reply is about what they said.
A simple way to run this:
- Ask three or four regulars to act as greeters. They do not need a title, though a small role helps.
- Share one rule with them: answer the person, not the join event. "Nice, which rank are you playing at?" works. "Welcome!!!" from five people does not.
- Give new members an easy first message. A pinned prompt such as "tell us what you are playing or making this week" is much easier to answer than "introduce yourself".
- Point the newcomer to a next step: tonight's voice session, a thread they would like, or another member with the same interest.
Avoid mass pinging for each join. It trains regulars to ignore the channel, and on a busy day it pushes real conversation out of view.
Rules, verification and other doors
Every door you add before the first message costs you people. That can be the right trade: a server with a raid problem or sensitive topics needs stronger gates than a small friends-of-friends group. Choose on purpose.
- Keep rules short enough to read. A wall of 30 rules gets scrolled past. Our moderation guide explains how to write fewer, clearer ones.
- Use one gate, not three. A rules screen, a verification step and a captcha in a row feels like an airport.
- Explain why a gate exists. "This stops spam bots, it takes ten seconds" reads very differently from an unexplained block.
If you want automated welcome messages or verification, BotGG covers that side in its own documentation. Automation should support the human welcome and never replace it.
No Community server? You can still onboard people
Smaller private servers can skip the built-in tool. A single welcome channel with a short pinned message does most of the work: what this server is, the two or three channels to start in, how to get a role, and who to ask. Update it when the server changes, because an out-of-date welcome post is worse than none.
How do you know it is working?
Look at behaviour, not at how polished the setup appears:
- Do new members post at all? If people join and stay silent, your first-message prompt or your default channels need work.
- Do they leave within a day? Early exits usually mean the server was not what they expected, so check how you describe it wherever they found you.
- Do they come back the next week? That depends on events and on people, which is where our guide on how to grow a Discord server picks up.
Discord's Server Insights can help on Community servers. Reading the channel yourself works just as well at a small scale.
Before you invite more people
Run the friend test again after every change, then fix the first thing that confused them. Once newcomers land well, it is worth sending more of them your way. Add your server to TopGuilds for free, and describe it honestly, so the people who arrive are the people your onboarding was built for.


