Free esports Discord server template with private team channels, scrim planning, match-day workflows, safe roles, onboarding and setup guidance.
Run a competitive roster like an organisation, not a general gaming chat. Players, coaches and managers get private spaces for availability, practice, scrims, VOD review, strategy and match-day decisions; trial players and community members only see the areas staff deliberately grant.
Create each category with its permissions first, then add channels inside it and keep them synced to the category. Channel types used: Text, Voice.
The authoritative rules, schedule and organisation information every approved member needs.
Community conduct, competitive integrity, confidentiality, reporting and the team policies that members must confirm.
Roster updates, deadlines and operational notices. Use an ordinary read-only text channel; Community features are not required.
Staff contacts, roster structure, game and region, time zones, league links and the process for requesting team access.
One maintained schedule for official matches, practice blocks and check-in times, backed by Discord Scheduled Events where useful.
Private day-to-day coordination for signed players, substitutes and competitive staff.
Daily roster coordination that does not belong in strategy, scheduling or review threads.
Weekly polls for practice, scrim and match availability. Players answer by the team deadline and update staff when circumstances change.
Current compositions, playbooks and tactical decisions. Pin the current version and archive obsolete plans.
Permissions: Limit to the active roster and competitive staff. Remove access immediately when someone leaves; never expose this channel to Trial Player or Member.
One post per review with a VOD link, focus points and owner. Put timestamped discussion in a thread and mark the review complete.
Approved guides, map notes, warm-up routines and team documents that support practice without mixing into live strategy.
A focused workflow for this team's own practice and scrims—not a cross-team opponent marketplace.
Confirmed scrims for this roster: opponent, date, check-in time, format and staff contact. Finding opponents belongs in a future dedicated scrim server.
One factual result entry per scrim with maps, score and three review takeaways; continue discussion in its thread.
Legitimate observations from public matches and prior scrims. Never request leaked strategy or confidential material from another team.
Practice goals, drills, assignments and follow-up actions. Keep attendance expectations aligned with the published team policy.
Short-lived operational information for an official match.
Opponent, format, lobby details, check-in deadline and official links for the next match. Replace or archive it after the fixture.
Confirmed starters, substitutes, roles and staff responsibilities. Manager or Coach posts; players acknowledge.
Time-sensitive match-day coordination and technical updates. Results move to #announcements only after staff approve them.
A controlled application and trial area that never grants access to private team strategy.
Open positions, eligibility, application steps, deadlines and what the team assesses. State where applications are submitted privately.
Instructions and a private application route. Do not ask candidates to post personal details publicly.
Scheduling and practical questions for accepted trial players; no roster strategy or private player evaluations.
Separate practice, review and official-match conversations so teams do not collide.
Everyday team conversation and short coordination calls.
Practice and approved tryouts. Set a user limit appropriate to the game plus coaches.
Screen-shared review sessions.
Permissions: Allow Video for Coach and Analyst; use Priority Speaker only when the review lead genuinely needs it.
Optional isolated voice room for official matches. Add it only if Team Room cannot serve this purpose.
Private management, coaching, recruitment decisions and auditable access changes.
Roster decisions, contracts or eligibility processes, scheduling ownership and organisation administration.
Practice plans, performance themes and review preparation. Keep personal feedback need-to-know.
Upcoming lineups, opponent preparation and decisions not ready for the roster.
Role changes, trial start/end dates, warnings, roster moves and access removal, with the staff member and reason.
A deliberately small public area for supporters or prospective players. Delete it for a fully private team HQ.
Low-stakes conversation about the team. Keep roster operations and recruitment decisions elsewhere.
Slowmode: 10 seconds during busy match periods
Approved results and public highlights after a match. Never publish private comms, strategy or unannounced lineup information.
Create roles in this order, from the top of the role list down. A role can only manage roles below it, and bot roles must sit above any role they assign.
Different staff setup or bots? Adapt this hierarchy in the roles generator.
Identity for the organisation owner. The owner account already has full control.
Owns roster access, scheduling, recruitment operations and server structure.
Runs practice, review and competitive preparation.
Handles conduct and reports in any public community area; does not control roster decisions.
Coordinates the active lineup and team communication without becoming a server administrator.
Prepares VOD notes, opponent research and performance summaries.
Signed active-roster access. Create a separate Player role per roster only when the organisation actually has multiple teams.
Approved substitute access for practice and matches, with strategy limited only where the coaching staff has a real need.
Temporary access to recruitment and approved practice sessions only.
Community or prospective-player identity with no competitive access.
Opt-in reminder for confirmed team scrims.
Opt-in reminder for official match starts or approved public broadcasts.
No Community features are required. Competitive access is approval-based: a Manager assigns Player, Substitute, Trial Player, Coach or Analyst after confirming the person's status. Onboarding may offer Member and opt-in Match Ping only; it must never unlock team categories.
Try Discord's built-in features first. Bot names are examples to evaluate, not endorsements; CordNexa has no affiliation with any bot. Review the permissions a bot requests before adding it.
Knowing who can play before you book a scrim.
Native first: Discord polls (up to 10 answers, running up to a week) handle weekly availability, and Scheduled Events show matches with an Interested button. Add a sign-up bot only if you need rosters per event.
Examples: Apollo (sign-up lists)
Some teams like results and stats posted automatically.
Native first: The #scrim-log format works without a bot. Only add a stats bot that officially supports your game.
These steps are specific to this kit. For the reasoning behind each stage — permissions, onboarding, testing and launch — see how to make a Discord server.
Turn on multi-factor authentication (2FA) for the owner account. This private-first layout uses text, voice, polls and Scheduled Events, so Community features are not required.
Owner → Manager → Coach → Moderator → Captain → Analyst → Player → Substitute → Trial Player → Member → ping roles. Manager must sit above every access role it assigns; no role needs Administrator.
Start with #rules, #announcements, #team-info, #match-schedule, #team-chat, #availability, #strategy, #vod-review, #scrim-schedule, #scrim-results, #match-info, #lineup, Team Room, Practice Room, VOD Review, #management, #coaches and #staff-log. Add recruitment, opponent notes, practice notes, match chat, Match Room, private planning and public community channels only when the workflow exists.
Deny View Channel for @everyone and Member in TEAM, PRACTICE & SCRIMS, MATCH DAY, VOICE and STAFF. Grant only the roles listed for each category, then keep child channels synced unless a documented exception is needed.
Publish application instructions without exposing personal details, then have staff assign Trial Player only after acceptance. Trial Player sees recruitment and an approved practice session, never #strategy, opponent notes, match-day planning or staff evaluations.
Use #scrim-schedule for confirmed fixtures and #scrim-results for concise review records. Use #match-info and #lineup for the next official match. This server coordinates one team's work; opponent discovery and multi-team scheduling belong in a dedicated scrim server.
Fill #rules and #team-info with confidentiality, reporting, attendance and voice expectations. Mark attendance, practice frequency and response deadlines as your team's customizable policy rather than universal esports rules.
Invite players and staff, verify their role with the Manager, and record assignments plus review dates in #staff-log. Do not grant competitive access through a public onboarding answer.
Use View Server As Role for Player, Substitute, Trial Player, Member and a role-less account. A trial player must not see team strategy, scrim notes, match-day planning or STAFF; a Member must see only TEAM HQ, public recruitment instructions and the optional community area.
Duplicate TEAM, PRACTICE & SCRIMS and MATCH DAY only when another active roster needs separate access. Give it a distinct Player role and keep STAFF shared.
Add a read-only #eligibility channel and a staff-only #compliance channel for academic or league requirements.
Delete COMMUNITY (OPTIONAL) and keep @everyone limited to the read-only TEAM HQ entrance until staff assigns access.
If players stream, pair this with the Streamer Community template in a separate public server rather than mixing fans into the team server.
Need stricter or more relaxed wording? Customise these rules in the rules generator.
Welcome to the team HQ. Read #rules and #team-info first, then ask the Manager to confirm your Player, Substitute, Trial Player or staff access—competitive roles are never self-assigned. Check #match-schedule for official dates; approved roster members use #availability, #scrim-schedule and Practice Room. Questions or access issue? Message the Manager or Moderator.
Want a shorter, professional or bot-ready version? Try the welcome message generator.
Start with rules, team information, a maintained schedule, team chat, availability, strategy, VOD review, confirmed scrims, match information, lineup, three focused voice rooms and a small staff area. Add recruitment and a public community area only when the team uses them.
Use Owner and Manager for administration, Coach and Captain for competitive leadership, Player and Substitute for roster access, Analyst for review work, Trial Player for temporary recruitment access, Moderator for community conduct and Member for public areas. Keep access staff-assigned.
The competitive area should not be. Keep strategy, scrims, match-day planning, recruitment decisions and staff categories hidden from @everyone. A small public community area is optional; many teams keep it in a separate server.
The compact setup in this kit uses 18 channels covering essential information, team coordination, scrims, match day, three voice rooms and staff operations. Add recruitment, opponent notes and public community channels only when they have an owner and active workflow.
Post one entry per VOD in #vod-review with the link, owner and focus points, discuss timestamps in its thread, and use VOD Review for live screen sharing. Mark the review complete and move follow-up actions into #practice-notes.
Use #scrim-schedule only for confirmed fixtures and #scrim-results for a concise score plus review takeaways. Keep opponent discovery, multi-team matchmaking and cross-team scheduling out of this team HQ; those workflows need a dedicated scrim server.
Post a weekly Discord poll in #availability with one answer per slot. Polls allow up to 10 answers and can run for up to a week, which fits a weekly scrim schedule.
It should not. Competitive access reveals private operations and must be assigned by a Manager after roster or application checks. Public onboarding can assign Member or opt-in notification roles only.
No. Publish your own realistic expectations for practice frequency, availability deadlines, absence notice and consequences. Label them as team policy and review them whenever the roster or competition schedule changes.
Remove Player, Substitute and specialist roles the same day, record the change in #staff-log, and review who can see #strategy and shared documents. Channel security only works while access roles stay current.
CordNexa is independent and not affiliated with or endorsed by Discord. Discord features change over time; this kit was last reviewed on 2026-10-04.