How to Set Up a Discord Server for Your Online Course or Cohort in 2026

To set up a Discord server for an online course, create cohort roles to keep groups separate, lock module channels so they unlock as students progress, gate entry with verification so only paying students get in, and add channels for announcements, office hours, and events. You can build the entire structure in under a minute by describing it to PeakBot's AI Server Builder.

Most course creators start with the built-in chat their course platform gives them, then quietly outgrow it. Threads die, students can't find anything, and there's no real sense of being in a group. Discord fixes that, but only if you set it up around how a course actually runs: cohorts, modules, deadlines, and live sessions. This guide walks through the exact structure and the settings that make it work.

Why Discord Beats Your Course Platform's Built-In Chat

Course platforms like Teachable, Kajabi, and Podia bundle a comment box or a basic community feed. They're fine for a quick question under a lesson, but they fall apart the moment your students want to actually talk to each other. There's no live voice, no real-time presence, no way to run an office-hours session where 40 people show up at once.

Discord gives you persistent channels, voice rooms, scheduled events, roles, and bots that automate the busywork. It's also where your students already are. The tradeoff is that Discord ships empty, so you have to design the structure yourself. If you're weighing a dedicated course platform's community against Discord, the breakdown in our Skool vs Discord comparison for creator communities covers where each one wins.

The rest of this guide assumes you've created a blank server (Server name → "Create My Own" → "For a club or community") and have PeakBot invited. Everything below is free unless noted; the one-prompt build at the end uses a Pro feature.

Step 1: Plan Your Categories Before You Touch a Channel

A course server has four jobs: deliver content, run live sessions, let students help each other, and handle admin. Map those to categories first so you don't end up with 30 loose channels.

A clean starting layout looks like this:

• START HERE — welcome, rules, introductions, get-your-role
• ANNOUNCEMENTS — announcements, office-hours-schedule
• COURSE — module-1, module-2, module-3… (locked until reached)
• COMMUNITY — general, wins, accountability, resources
• LIVE — office-hours (voice), coworking (voice), stage
• STAFF — staff-chat, support-tickets (private)

Building this by hand means creating each category, dragging channels in, and setting permissions one at a time. That's the part most people get wrong, and it's the part you can hand off entirely (see Step 7).

Step 2: Create Cohort Roles and Keep Groups Separate

If you run your course in cohorts, roles are how you keep the January group from seeing the March group's discussions. Create one role per cohort: Cohort Jan, Cohort Mar, and so on. Give each a distinct color so you can tell at a glance who's who.

The key move is channel permissions. For a cohort-only channel, deny the @everyone role the "View Channel" permission, then allow it for the specific cohort role. Now Cohort Jan sees their own discussion and standup channels, and Cohort Mar literally can't see they exist.

Layer in a few global roles on top:

• Student — the baseline role every paid member gets
• Alumni — past students who keep access to community channels but not live cohort ones
• Mentor / TA — helpers with permission to manage messages in their channels
• Staff — you and your team

Assign roles automatically on join with PeakBot's welcome and auto-role system so a new student lands with the right access without you lifting a finger.

Step 3: Lock Module Channels So They Unlock by Progress

Drip content keeps a cohort moving together instead of fifty people skipping ahead and asking questions out of order. In Discord, you simulate drip with roles and channel permissions.

Create a role per module — M1 Done, M2 Done, M3 Done — and set each module channel to be visible only to the matching role. module-2 denies View Channel to @everyone and allows it to M1 Done. When a student finishes module 1, they get the M1 Done role and module 2 appears.

You can hand out the unlock role two ways:

• Self-serve via reaction roles. Drop a message in module-1 like "React with ✅ when you've finished this module." Reaction roles are free and unlimited in PeakBot, so the student clicks one emoji and the next channel opens.
• Manual or checkpoint-gated. For courses where you want to verify completion (a submitted assignment, a passed quiz), assign the role yourself or have a TA do it. Slower, but tighter control.

This same locked-channel pattern is what powers most structured learning communities. If you want a head start, our study Discord server template shows a layout built around focused, progress-gated channels.

Step 4: Verify Members So Only Students Get In

You don't want your paid cohort space turning into a free-for-all. Two layers handle this.

First, Discord's native gate. Turn on Community in Server Settings, then under "Safety Setup" enable a verification level (Medium or High) and a rules-screening checkbox so new joiners must agree before they can type. Pair that with PeakBot's anti-raid and anti-nuke protection to stop bot floods and mass-join attacks.

Second, the link between "paid for the course" and "has access in Discord." The clean approach is a unique, role-locked invite per cohort, or a verification channel where students confirm their purchase email before a Student role unlocks the rest of the server. If you're charging directly for access, the full mechanics live in our guide on setting up a paid, members-only Discord server — it covers invites, role-gating, and keeping non-payers locked out.

For genuinely off-topic or heated moments in general, PeakBot's context-aware AI moderation reads message intent and adapts per channel instead of matching a fixed keyword list, so a frustrated student venting about a hard assignment doesn't get auto-flagged the way a keyword filter would.

Step 5: Set Up Announcements, Office Hours, and Events

Your announcements channel should be an Announcement-type channel (set it in channel settings) so students can "Follow" it and your posts surface clearly. Restrict posting to Staff so it stays signal, not chatter.

Office hours are where Discord pulls ahead of a comment box. Use a voice channel or a Stage channel for the session itself, and schedule it as a real Discord Event so students get a reminder and an RSVP. Recurring events — weekly office hours, cohort kickoff, demo day — are easy to set on a schedule; the full walkthrough is in our guide to setting up Discord events in 2026.

A simple weekly rhythm that works:

• Monday — announcements: the week's focus and what's unlocking
• Wednesday — live office hours (scheduled Event + voice)
• Friday — wins: students post what they shipped that week

Step 6: Onboard Students So They Talk on Day One

A silent server feels dead, and a dead server makes students churn. The fix is forcing one small action on arrival.

Set a welcome message that does three things: greets the student by mention, points them to get-your-role and introductions, and auto-assigns the baseline Student role. Then make the very first task social — an intro prompt with a fixed format kills the blank-page problem:

Drop an intro in #introductions: your name, what you're here to build, and one thing you're stuck on right now.

The "one thing you're stuck on" line is deliberate. It gives other students something to reply to, which turns a wall of monologues into actual conversation. Add an XP and leveling system (free in PeakBot) with a small role reward at the first level so early participation gets visibly recognized. Leaderboards and role rewards keep accountability cohorts engaged across the weeks where motivation usually dips.

Step 7: Build the Whole Course Server in One Prompt

Everything above — categories, cohort roles, locked module channels, permissions, welcome automation — is a lot of clicking if you do it by hand. PeakBot's AI Server Builder generates the entire structure from a plain-English description in under 60 seconds. It's the only Discord bot that builds fully custom server structures from natural language instead of dropping in a preset template, so the result matches your course, not a generic mold.

A prompt that produces a working course server looks like this:

Build a server for an online course with cohorts. Add a START HERE category with welcome, rules, and a get-your-role channel. Create an ANNOUNCEMENTS category (announcements + office-hours-schedule). Add a COURSE category with module-1 through module-6 channels, each locked to its own completion role. Add a COMMUNITY category with general, wins, accountability, and resources. Add a LIVE category with two voice channels for office hours and coworking. Create roles for Student, Alumni, Mentor, Staff, and one role per cohort. Add a STAFF category that only Staff can see.

PeakBot builds the channels, categories, roles, and permission overrides, then you tweak names and add cohorts as you launch new groups. The AI Server Builder is a Pro feature ($8.25/month or $69/year per server); the moderation, XP, welcome, reaction roles, tickets, and events you'll use day to day are part of the 30+ free features with no trial and no time limit.

Which Bot Should Run a Course Server?

You can wire a course server with several bots, and the honest answer is that each has a real strength. Carl-bot ($7.99/mo premium) is excellent at reaction-role menus and is a common pick for self-serve module unlocks. MEE6 ($11.95/mo premium) is the name most creators recognize and has solid leveling. Dyno ($4.99/mo premium) is cheap and dependable for plain moderation.

Where PeakBot wins for a course server is doing all of it with one bot — AI moderation, XP, welcome and auto-role, reaction roles, tickets for student support, events, and the AI Server Builder that constructs the whole thing — instead of stacking three or four bots and reconciling their settings. It currently powers 500+ Discord communities and is built to replace MEE6, Carl-bot, Dyno, and TidyCord together. See the side-by-side on the compare page if you want the full feature grid.

Frequently Asked Questions

How do I keep different cohorts from seeing each other's channels?

Create one role per cohort, then deny "View Channel" to @everyone on cohort-specific channels and allow it only for that cohort's role. Each group sees their own space and nothing from the others.

Can I lock course modules so they unlock as students progress?

Yes. Make a completion role for each module and set each module channel to be visible only to the matching role. Hand out the role with a reaction-role click or manual approval when a student finishes the previous module, and the next channel appears.

How do I make sure only paying students join my course server?

Use Discord's Community verification and rules screening to gate new joiners, then connect access to payment with a role-locked invite or a purchase-confirmation step before the Student role unlocks the server. The full setup is covered in our guide on setting up a paid, members-only Discord server.

Is PeakBot free for a course server?

Yes, 30+ features including AI moderation, XP and leveling, welcome messages with auto-roles, reaction roles, tickets, and events are free with no time limit. The AI Server Builder that constructs your whole server from one prompt is the Pro feature, at $8.25/month or $69/year per server.

How long does it take to set up the server?

By hand, expect to spend a focused session creating categories, roles, and permissions. With PeakBot's AI Server Builder you describe the structure once and it builds channels, categories, roles, and permissions in under 60 seconds, leaving you to fine-tune names and add cohorts as you launch.