COMMUNITY DISCORD TEMPLATE / FREE SETUP KIT

Community Basecamp

An organised foundation for clubs, interest groups and volunteer-run communities, with events, a questions forum, tracked suggestions and team spaces.

  • 30–2,000 members
  • Intermediate
  • ~45 min setup
  • 20 channels · 7 roles
  • Needs Community features

Is this template right for you?

Give an organisation run by volunteers a server where information is easy to find: announcements are separate from chat, questions get marked as answered, suggestions show their status, and each working team has its own space.

Best for

  • Communities with an organising team and recurring events
  • Groups that repeatedly answer the same questions
  • Communities that want members' suggestions to be visibly tracked

Not ideal for

  • A small friend group — Cozy Corner or Pixel Party are simpler
  • Study and accountability groups — The Study Club has focus rooms and subject help built in

Built for: Clubs and societies · Hobby and interest groups · Volunteer and non-profit communities · Local groups and meetups · Open-source and product communities

Categories & channels

Create each category with its permissions first, then add channels inside it and keep them synced to the category. Channel types used: Text, Announcement, Forum, Voice, Stage.

WELCOME

Read-only

Read-only information every member should be able to find in seconds.

Category permissions: @everyone: deny Send Messages and Create Public Threads; allow Add Reactions. Organiser: allow Send Messages; Team Lead: allow in #announcements and #events.

rules Text

Code of conduct, how to report concerns, and how decisions are made.

Read-only
announcements Announcement

Official updates only. Keep them short and link to the discussion channel.

Read-only
events Text

Upcoming meetups and online sessions, each with a linked Discord Event for RSVPs.

Read-only
about-us Text

What the group does, who runs it, how to get involved, and links to your website or membership form.

Read-only

COMMUNITY

Public

Open conversation between members.

introductions Text

New members introduce themselves using a pinned prompt: where they are from, what they are interested in, and how they would like to take part.

Public
general Text

Everyday conversation.

Slowmode: Add 5 seconds if the server passes a few hundred active members

Public
photos-and-recaps Text

Event photos and write-ups. Ask before posting photos that clearly show other people's faces.

Permissions: Allow Attach Files.

Public
off-topic Text

Conversation unrelated to the group's focus.

Public

HELP & IDEAS

Public

Questions and suggestions that need a trackable answer instead of a chat reply.

questions Forum

One post per question. The asker or a helper tags it Answered when resolved, which builds a searchable FAQ over time.

Forum tags: Getting started, Events, Membership, Technical, Answered

Public
suggestions Forum

One post per idea. Members react to show support; organisers update the status tag and reply with a reason.

Permissions: Make the status tags moderator-only (members with Manage Threads can apply them), require a tag on new posts, and set a default reaction for showing support.

Forum tags: New, Under review, Planned, Done, Not now

Public
resources Forum

Guides, documents and useful links, one post each, so they can be found later.

Forum tags: Guide, Template, Link, Official

Public

TEAMS

Role-gated

Working spaces for volunteers who organise events, communications and outreach.

Category permissions: Deny View Channels for @everyone. Allow the Volunteer role and staff. For confidential teams, restrict individual channels to that team's role.

volunteer-hub Text

Tasks, shift sign-ups and general volunteer coordination.

Role-gated
events-team Text

Planning venues, dates and run-sheets for upcoming events.

Role-gated
comms-team Text

Drafting announcements, newsletters and social posts before they go out.

Role-gated
Team Meeting Voice

Voice and video for volunteer meetings.

Role-gated

VOICE

Public

Community calls and events.

Community Lounge Voice

Drop-in voice chat.

Public
Town Hall Stage

Monthly community meetings, talks and AMAs, with members requesting to speak.

Permissions: Stage moderators need Manage Channels, Mute Members and Move Members on this channel. Grant them to Organiser and Moderator here.

Public

ORGANISERS

Staff only

Private leadership and moderation.

Category permissions: Deny View Channels for @everyone. Allow Organiser and Moderator.

organisers Text

Leadership discussion and planning.

Staff only
decisions-log Text

One message per decision: what was decided, by whom, when, and why. This keeps things consistent when organisers change.

Permissions: Deny Send Messages in Threads to keep entries clean.

Staff only
mod-log Text

AutoMod alerts and moderation actions.

Staff only

Role hierarchy & permissions

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.

  1. Organiser

    The leadership team or committee.

    How members get it
    Assigned by the owner, following your group's own process for choosing leaders.
    Display
    Shown separately · Mentionable
    Enable
    Manage Server, Manage Roles, Manage Channels, Manage Events, Manage Webhooks, View Audit Log, Ban Members, Kick Members, Timeout Members, Manage Messages
    Withhold
    Administrator — keep with the owner account
  2. Moderator

    Enforce the code of conduct and handle reports.

    How members get it
    Assigned by Organisers.
    Display
    Shown separately · Mentionable
    Enable
    Timeout Members, Kick Members, Manage Messages, Manage Threads, Manage Nicknames, View Audit Log
    Withhold
    Manage Roles; Ban Members until trusted
  3. Team Lead

    Leads a volunteer team, such as events or comms.

    How members get it
    Assigned by Organisers.
    Display
    Shown separately · Mentionable
    Enable
    Create Events, Manage Events, Manage Threads, Mention @everyone, @here, and All Roles
    Withhold
    Kick Members; Ban Members
  4. Volunteer

    Members who help run things. Unlocks the TEAMS category.

    How members get it
    Assigned by a Team Lead once someone signs up to help.
    Display
    Shown separately · Mentionable
    Enable
    Create Events
  5. Member

    Everyone who has completed onboarding.

    How members get it
    Granted by Server Onboarding: both answers to the required first question include it.
    Display
    Not separated · Not mentionable
    Enable
    View Channels, Send Messages, Send Messages in Threads, Create Public Threads, Read Message History, Add Reactions, Embed Links, Attach Files, Connect, Speak, Request to Speak
    Withhold
    Mention @everyone, @here, and All Roles
  6. Interest roles (customise, e.g. Beginners, Local Meetups, Online Only)

    Let members get relevant pings and see optional channels.

    How members get it
    Self-assigned through onboarding.
    Display
    Not separated · Mentionable
    Enable
    No permissions (cosmetic or ping role)
  7. Event Updates

    Opt-in ping for new events and schedule changes.

    How members get it
    Self-assigned through onboarding.
    Display
    Not separated · Mentionable
    Enable
    No permissions (cosmetic or ping role)

Onboarding flow

Server Onboarding asks how members want to take part, so volunteers can be found early and people only receive the pings they chose.

Question 1 · required

How would you like to take part?

  • Join conversations and events→ Member
  • I'd like to volunteer→ Member, plus a note to Team Leads in #volunteer-hub via a bot or manual follow-up
Question 2 · optional

What are you interested in?

  • Customise with your group's topics or locations→ Matching interest role
Question 3 · optional

Do you want event notifications?

  • Yes→ Event Updates
  • No→ Nothing

Default channels: rules, announcements, events, about-us, introductions, general, photos-and-recaps, off-topic, questions, suggestions

Discord requires at least 7 default channels for Community Onboarding, and @everyone must be able to view and send messages in at least 5 of them.

Suggested first steps: Read #about-us → Introduce yourself → RSVP to the next event → Search #questions before asking

Moderation setup

Verification level
Medium — Medium balances accessibility for less technical members with protection from new spam accounts.
Explicit media filter
Scan media content from all members.

AutoMod rules

  • Block mention spam (limit around 5)Block and time out for 10 minutes; alert #mod-log.
  • Block suspected spam contentBlock and alert.
  • Commonly flagged words: the Insults and Slurs and Sexual Content listsBlock and alert.
  • Custom keywords for off-platform scams common in your area, such as fake ticket salesBlock and alert.

Escalation

  1. Reminder in channel
  2. Private message from a Moderator
  3. Timeout
  4. Kick
  5. Ban, recorded in #decisions-log for serious cases
  • Publish how moderation decisions can be appealed, and who handles an appeal. Transparency matters more in member-run groups.
  • If the group runs in-person events, write down how online conduct and event conduct relate before you need to decide a case.
  • Ask consent before posting photos of identifiable people, especially if members include under-18s.

Recommended bots

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.

Event scheduling

Optional

Recurring meetups need reminders and RSVP counts.

Native first: Discord Scheduled Events let members mark themselves Interested, notify them when the event starts, and can repeat. Add a bot for sign-up lists or calendar sync.

Examples: Apollo (sign-up lists), Sesh (recurring events and calendar sync are Sesh Premium)

Forms and applications

Optional

Volunteer sign-ups and membership applications.

Native first: Link an external form from #about-us, or ask in the onboarding flow and follow up manually.

Moderation logging

Optional

Useful for handing over between organisers.

Native first: The Audit Log and #decisions-log cover most needs.

Examples: Carl-bot

Step-by-step setup

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.

  1. Agree who owns the server

    Decide which person or shared account owns the server, and record that in #decisions-log. Turn on multi-factor authentication (2FA) for the owner account.

  2. Enable Community features

    Enable Community (Discord requires a verified-email verification level, the explicit media filter set to scan all members, a rules channel and a community updates channel). Set #rules and #organisers. Later, in Server Settings → Onboarding, add a Server Guide with new-member to-dos pointing to #about-us, #events and #questions.

  3. Create roles in order

    Organiser → Moderator → Team Lead → Volunteer → Member → interest and ping roles.

  4. Build the WELCOME category

    Create it read-only, then add #rules, #announcements, #events and #about-us. Write #about-us before anything else.

  5. Create the forums with tags

    Set up #questions, #suggestions and #resources with their tags. Make status tags on #suggestions moderator-only.

  6. Create TEAMS and ORGANISERS

    Restrict TEAMS to Volunteer and staff, and ORGANISERS to Organiser and Moderator. Check that each channel is still synced to its category.

  7. Configure Onboarding

    Add the questions and replace the interest options with your real topics or locations.

  8. Configure AutoMod and verification

    Set verification to Medium and add the AutoMod rules with alerts to #mod-log.

  9. Seed the forums

    Post your five most common questions with answers in #questions and tag them Answered, so new members find a useful FAQ on day one.

  10. Test and launch

    Use View Server As Role as Member and Volunteer, then create your first Event and share the invite with your existing members.

Make it yours

Local groups

Add location roles and a channel per area only once each area has enough members to keep it active.

Open-source and product communities

Rename #questions to #support, add a #showcase forum and a read-only #changelog announcement channel.

Formal organisations

Add a role-gated #board category and store official documents outside Discord. Discord should not be your only record.

Paid memberships

If membership is paid, use your membership platform's official Discord integration to sync a Member role, rather than assigning it by hand.

Community rules

  1. Treat everyone with respect. No harassment, discrimination, hate speech or personal attacks.
  2. Stay on topic in each channel, and search #questions before asking.
  3. No spam, unsolicited advertising or fundraising without organiser approval.
  4. Respect privacy: ask before sharing photos of people, and never share personal information.
  5. Disagree with ideas, not people. Use #suggestions for proposals and keep criticism constructive.
  6. Report concerns to a Moderator or Organiser privately. You can appeal decisions by messaging an Organiser.
  7. Follow Discord's Community Guidelines and any code of conduct for our in-person events.

Need stricter or more relaxed wording? Customise these rules in the rules generator.

Welcome message

Welcome to Community Basecamp! Start with #about-us to see what we do and how to get involved. Introduce yourself in #introductions, check #events for what's coming up, and search #questions if you're wondering about something — if it isn't there yet, ask! Want to help run things? Tell us in onboarding and a Team Lead will reach out.

Want a shorter, professional or bot-ready version? Try the welcome message generator.

Community Basecamp FAQ

Why use forum channels for questions and suggestions?

Forums keep each question or idea in its own post with a status tag. Answers remain searchable, and members can see what happened to a suggestion instead of it scrolling away in chat.

How should volunteers be managed on Discord?

Use a Volunteer role that unlocks a TEAMS category, and give Team Leads event permissions without moderation powers. Keep leadership and moderation discussion in a separate staff category.

Can I use this for a local in-person group?

Yes. Use #events with Discord Events for RSVPs, add location interest roles, and set a clear policy for photos and conduct at in-person events.

Version history

  • v2.1 · 2026-09-28
    • Checked against Discord's Help Center: replaced the retired Welcome Screen with Server Guide, listed Discord's Community requirements, and expanded onboarding default channels to meet Discord's minimums.
  • v2.0 · 2026-09-27
    • Added questions, suggestions and resources forums with status tags, a volunteer TEAMS category and a decisions log.
    • Added onboarding for volunteer recruitment and an appeals-aware moderation plan.
  • v1.0 · 2026-09-27
    • Initial layout with shared starter channels and roles.

CordNexa is independent and not affiliated with or endorsed by Discord. Discord features change over time; this kit was last reviewed on 2026-09-28.