Start With the Right Mental Model
A well-structured Discord server is the difference between a team that communicates clearly and one that misses scrims because important messages got buried in general chat. This guide covers how to set up a Discord server for a competitive gaming team from scratch - channels, roles, bots, and the permissions model that keeps things organized.
Discord servers for gaming teams serve two distinct purposes that often conflict: operational coordination (scheduling, lineups, announcements, strategy) and social space (memes, general chat, voice hangouts). The problem is that operational channels get flooded by social traffic, and then nobody checks them. The solution is a clear structural separation between the two, enforced by channel organization and norms.
Role Architecture
Before you create a single channel, define your roles. Roles in Discord serve double duty as permission controls and identity markers.
Recommended roles for a competitive team: Owner/Captain with full server access and bot administration. Coach for strategy channels and scrim review. Manager for scheduling access and roster management channels. Player (Main Roster) for full team access with limited admin. Sub for team channels minus some admin-only spaces. Trial for limited access during the try-out period. Analyst/Staff for view access to strategy channels. Mod for moderation permissions without needing team-specific channel access.
The key principle is that permissions should be granular enough to be meaningful. A trial player should not see your scrim planning channels. A sub should not have access to roster management discussions.
Color-code the top roles so they display visibly in the member sidebar. Captains and coaches in one color, players in another, staff in a third.
Channel Structure
Organize channels into categories. For announcements: #welcome for server description, rules, and how to get your role. #announcements for important updates (read-only for most members). #changelog for updates to the team roster and schedule changes.
For competitive channels: #availability for weekly availability calendars. #lineups for the current week's lineups. #scrims for confirmed scrim details. #scrim-results for scores and brief review notes.
For strategy: #vod-review for links and notes from VOD sessions. #meta-discussion for current patch notes and meta analysis. #map-pool or #hero-pool for whatever is relevant to your game.
For general: #team-chat as the main team text channel. #media for clips and highlights. #off-topic for non-game conversation.
For voice: Scrim 1, Scrim 2, Scrim 3 for active play. Strategy Room for smaller voice review sessions. AFK/standby channel.
For admin (private): #roster-management for captain and manager only. #contact-log for outreach to opponents. #bot-commands for slash commands that would clutter other channels.
The competitive channels should be read-only for general members by default - only bots and admins post there.
Permissions Per Channel Category
Discord permissions have a hierarchy: server defaults, then role overrides, then channel overrides. Work top-down.
At the server level, deny "Send Messages" for the base @everyone role. Then grant it selectively per channel based on who should be talking there.
For #availability and #scrims: only bots (like Supatimer) and captains can post. Players click buttons but do not send raw messages. For #scrim-results: captain or bot posts the base result, players can add comments. For #team-chat: everyone on the roster can post. For admin channels: captain, manager, and coach only - everyone else cannot even see the category.
Bot Setup
Add bots early so you can set their permissions correctly from the start rather than retrofitting. For scheduling, Supatimer handles availability tracking, lineup generation, and scrim posts. Run /setup after adding the bot - the guided wizard takes about ten seconds and gets your time blocks, roster roles, and channel assignments configured.
For moderation, Carl-bot or MEE6 handle automod, welcome messages, and role assignment. For events, Sesh or Apollo work well for tournament dates and one-off team events.
Assign each bot a dedicated role in your server. Give that role only the permissions the bot needs. Never give bots administrator permissions unless absolutely required.
The #welcome Channel
This channel does a lot of work. Every new member sees it first. It should contain: what the server is and who it is for, how to get your team role (either self-serve via a bot or by DMing a manager), link to the team's external resources (Liquipedia, social, VOD channel), and brief rules for the server.
Keep it short. A wall of text that nobody reads is worse than a focused four-paragraph description.
Naming Conventions
Consistent naming makes navigation easier, especially for new members. Use all lowercase with hyphens: #scrim-results not #ScrimResults. Be descriptive over clever: #availability not #whos-free. Use emoji prefixes sparingly - one emoji per category header is fine, emoji on every channel name creates visual noise.
Onboarding New Players
When a new player joins the roster, have a defined checklist: assign their roles (Player, specific game role if applicable), add them to the scheduling system, point them to #welcome and #team-chat, and add them to any external tools (Google Drive, Notion, tracker accounts).
A pinned message in an admin channel with this checklist means any manager can onboard someone without having to ask the captain.
Keeping It Maintained
Competitive team servers tend to accumulate clutter - stale channels, unused bots, outdated pinned messages. Set a quarterly reminder to audit: archive channels that have not been used in two months, remove bots that are no longer active, update the #welcome channel if the roster or team structure has changed, and review role assignments for players who are no longer active.
Five minutes of maintenance every few months prevents the server from becoming confusing.