How to make a Discord server
people actually use.

Every later decision — how many channels, which roles, how strict the rules are — depends on who the server is for. Answer three questions before you open Discord:

1. Who is it for? “Friends from university”, “viewers of my stream” and “people learning Python” need very different spaces.
2. What will they do there? Chat, play together, ask questions, share work, attend events? List the two or three main activities.
3. How many people in the first three months? Ten people who know each other need almost no structure. Three hundred strangers need onboarding, moderation and clear information channels.

Write the answer as one sentence, for example: “A server for about 50 indie game fans to find co-op partners and discuss a monthly game pick.” You will use it for your server description, your rules and your welcome message.

These are starting points, not the only correct structure. If none fits, build from scratch and borrow the parts that do. The template comparison shows size, complexity and setup time side by side.

In the Discord app, select + (Add a Server) at the bottom of your server list and choose Create My Own (or start from one of Discord's templates). Discord then asks whether the server is for a club or community or for you and your friends; you can skip that question if you're unsure.

Give the server a name members will recognise and an icon. Both can be changed later, but the name appears in invites, so avoid placeholders.

Should you enable Community features?

Community is a server setting that unlocks tools for larger groups: a designated rules channel, Forum, Announcement and Stage channels, and Community Onboarding. To enable it, Discord requires a verification level that needs a verified email, the explicit media content filter set to scan media from all members, a rules or guidelines channel, and a channel for Discord's community updates. Becoming a Community server does not, by itself, make your server public or listed in Server Discovery, which has separate eligibility requirements.

Delete the default channels you don't need now. It is easier to design the structure from a clean slate than to work around channels you didn't choose.

Categories group channels by purpose, and each channel should have one job. The most common beginner mistake is creating twenty channels on day one: people spread thin, most channels stay empty, and the server looks inactive. Start with the minimum that supports your main activities, and add channels when an existing one gets crowded.

Choosing channel types

• Text for flowing conversation.
• Forum (Community servers) for things that need their own post and should stay findable: questions, suggestions, group-finding, showcases. Tags make them filterable. Without Community, a text channel where each topic gets its own thread works similarly.
• Announcement (Community servers) for staff updates. Other servers can follow them.
• Voice for talking, and Stage (Community servers) for events where a few people speak to an audience.

Want to design the structure yourself? Build this channel structure with the Discord Server Layout Planner. Or start from a complete CordNexa template; for quicker inspiration, Discord channel ideas has launch-ready layouts for 12 types of server.

Roles do two jobs: they grant permissions and they organise people (staff, members, interests, colours). Their order matters as much as their permissions. In Discord, a member can only manage members and roles that are positioned below their own highest role, and a bot can only assign roles below its own role.

Planning a hierarchy for a different staff setup or with several bots? The roles generator builds an ordered plan with permissions to grant and withhold, and warns you when the order would break something.

Discord permissions work in layers. Roles set server-wide permissions. Categories and channels can then override those for specific roles or members. A channel override for a specific role generally beats the @everyone setting, and a member-specific override takes priority over role overrides.

A safe order of work

1. Strip @everyone back. @everyone is every person in the server, including someone who joined ten seconds ago. Keep it to viewing and chatting in public channels, and remove permissions such as mentioning @everyone, managing anything, and — if you want control over growth — creating invites.
2. Give member permissions to a Member role if you gate new members, for example by granting that role through a required onboarding question. (Discord's Rules Screening makes people agree to the rules before they can talk, but it doesn't give them a role.) If you use Community Onboarding, leave @everyone able to view and chat in your main public channels: Onboarding needs at least 5 default channels where @everyone can view and send messages, so gate extra areas rather than the whole server.
3. Set overrides on categories, not individual channels. Channels that are synced to their category pick up any change you make to the category. Changing a permission on the channel itself un-syncs it, so only do that when a channel truly needs different rules.
4. Hide staff areas by denying View Channel for @everyone on the staff category and allowing it for staff roles.

Rules tell members what is expected, and they give moderators something consistent to point to. Short, specific rules work better than long, vague ones — “no harassment, slurs or threats” is enforceable, while “don't be toxic” means something different to everyone.

• Put safety first: respect and hate speech, privacy, scams, and content appropriate for your youngest members.
• Add rules for the problems your type of server actually has: spoilers, self-promotion, cheating, academic integrity.
• Say how to report a problem and what usually happens next.
• Post them in a read-only channel near the top. On Community servers, set it as the rules channel.

The rules generator writes a numbered rules post for your audience and moderation style that you can edit rule by rule.

Onboarding is what happens between someone clicking your invite and feeling at home. The goal is that new members see a small, relevant part of the server first, and pick up roles that match their interests.

Keep onboarding questions few and useful. “Which games do you play?” or “What are you studying?” should each map to a role that unlocks channels or pings. Questions that don't change what someone sees just slow them down. Members can change their answers later from the Channels & Roles tab, and Onboarding also includes an optional Server Guide with a welcome message and a short list of new-member to-dos.

Use the Discord Onboarding Planner to turn your default channels, questions, role assignments and first steps into one practical flow.

A welcome message should answer one question: what should I do first? Greet the person, say in a sentence what the server is for, list two to four first steps with channel links, and say where to get help.

• Pinned post or bot greeting? A pinned post in a welcome channel is simple and never spams. A bot greeting mentions each new member; in busy servers it can bury conversation, so give it its own channel.
• Join messages: Discord can post a system message when someone joins. Choose the channel in Server Settings → Overview → System Messages Channel, or pick No System Messages if they clutter your chat.
• Introductions: useful for communities where people get to know each other; less so for large support or creator servers.

The welcome message generator writes short, friendly, professional and themed versions with a live Discord preview.

Moderation setup is cheapest before you have a problem. Three built-in tools cover most servers:

Verification level

This sets what an account must have before it can talk in your server. Higher levels stop more throwaway accounts but add friction for genuine newcomers.

AutoMod

Discord's AutoMod can block messages before they are posted. Start with the spam, mention-spam and commonly flagged words rules (Discord provides Insults and Slurs, Sexual Content and Severe Profanity lists), then add keywords specific to your community, such as fake-giveaway phrases or cheat-service names. Send alerts to a private staff channel so you can see what was caught.

Timeout and the Audit Log

Use Timeout rather than a custom “Muted” role: it stops someone sending messages, reacting or joining voice across the whole server, with no extra overrides, for up to a week from the app. The Audit Log records administrative actions — who changed what — which helps when several people moderate.

Bots are useful, but each one is software with permissions in your server. Before adding one, check whether Discord already does the job.

• Add bots from their official website or listing, and read the permissions on the authorisation screen.
• Prefer bots that ask only for the permissions their features need. Treat a demand for Administrator as a warning sign.
• Place each bot's role below your staff roles and above any role it assigns.

Notifications decide whether members keep your server unmuted. A server that pings everyone for every event trains people to mute it — and then they miss the things that matter.

• Default notifications: in the server's settings, set the default to only @mentions so new members aren't notified for every message.
• @everyone and @here: restrict mentioning them to staff who post announcements.
• Opt-in ping roles: create roles such as “Game Night Ping” or “Live Ping” that members choose. Staff mention those instead of @everyone.

Test before the first invite goes out. Problems found now are private; problems found later are public.

1. View Server As Role for Member and each staff role. Look for staff channels that are visible and public channels that are missing.
2. Walk through joining with a trusted friend. Watch them go through onboarding. Did they get the right roles? Did they know what to do next?
3. Trigger AutoMod with a harmless test keyword you added, and check the alert reaches your staff channel.
4. Check bots: role assignment works, notifications post to the right channel, and nothing has more permission than it needs.

An empty server is hard to join. Launch in two stages:

1. Founding members first. Invite five to fifteen people who will actually talk. Post a few conversation starters, share something in each main channel, and fix whatever confuses them.
2. Then open up. Share your invite where your intended members already spend time — your stream, your club's mailing list, a relevant community — rather than in unrelated places.

• Invite settings: when you create an invite, you can edit how long it lasts and set a maximum number of uses. Non-expiring links are available for Community servers; use one only where you control where it's posted. If a link leaks during a raid, you can pause invites in Server Settings → Invites.
• Name and icon: make them match your one-sentence purpose from step 1, so people recognise the server when they join.

Servers drift. Channels that made sense at launch go quiet, new needs appear, and rules written for ten people don't fit three hundred. A short monthly review keeps things healthy:

• Channels: merge or archive channels with little activity; add one when a topic keeps overflowing another.
• Roles: remove roles nobody uses, and check that staff still need the permissions they have.
• Rules and AutoMod: update them based on what moderators actually dealt with.
• Members: ask what they'd change. A suggestions forum with status tags shows people their ideas are heard.