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
An organised foundation for clubs, interest groups and volunteer-run communities, with events, a questions forum, tracked suggestions and team spaces.
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.
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.
Read-only information every member should be able to find in seconds.
Code of conduct, how to report concerns, and how decisions are made.
Official updates only. Keep them short and link to the discussion channel.
Upcoming meetups and online sessions, each with a linked Discord Event for RSVPs.
What the group does, who runs it, how to get involved, and links to your website or membership form.
Open conversation between members.
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.
Everyday conversation.
Slowmode: Add 5 seconds if the server passes a few hundred active members
Event photos and write-ups. Ask before posting photos that clearly show other people's faces.
Permissions: Allow Attach Files.
Conversation unrelated to the group's focus.
Questions and suggestions that need a trackable answer instead of a chat reply.
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
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
Guides, documents and useful links, one post each, so they can be found later.
Forum tags: Guide, Template, Link, Official
Working spaces for volunteers who organise events, communications and outreach.
Tasks, shift sign-ups and general volunteer coordination.
Planning venues, dates and run-sheets for upcoming events.
Drafting announcements, newsletters and social posts before they go out.
Voice and video for volunteer meetings.
Community calls and events.
Drop-in voice chat.
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.
Private leadership and moderation.
Leadership discussion and planning.
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.
AutoMod alerts and moderation actions.
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.
The leadership team or committee.
Enforce the code of conduct and handle reports.
Leads a volunteer team, such as events or comms.
Members who help run things. Unlocks the TEAMS category.
Everyone who has completed onboarding.
Let members get relevant pings and see optional channels.
Opt-in ping for new events and schedule changes.
Server Onboarding asks how members want to take part, so volunteers can be found early and people only receive the pings they chose.
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.
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)
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.
Useful for handing over between organisers.
Native first: The Audit Log and #decisions-log cover most needs.
Examples: Carl-bot
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.
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.
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.
Organiser → Moderator → Team Lead → Volunteer → Member → interest and ping roles.
Create it read-only, then add #rules, #announcements, #events and #about-us. Write #about-us before anything else.
Set up #questions, #suggestions and #resources with their tags. Make status tags on #suggestions moderator-only.
Restrict TEAMS to Volunteer and staff, and ORGANISERS to Organiser and Moderator. Check that each channel is still synced to its category.
Add the questions and replace the interest options with your real topics or locations.
Set verification to Medium and add the AutoMod rules with alerts to #mod-log.
Post your five most common questions with answers in #questions and tag them Answered, so new members find a useful FAQ on day one.
Use View Server As Role as Member and Volunteer, then create your first Event and share the invite with your existing members.
Add location roles and a channel per area only once each area has enough members to keep it active.
Rename #questions to #support, add a #showcase forum and a read-only #changelog announcement channel.
Add a role-gated #board category and store official documents outside Discord. Discord should not be your only record.
If membership is paid, use your membership platform's official Discord integration to sync a Member role, rather than assigning it by hand.
Need stricter or more relaxed wording? Customise these rules in the rules generator.
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.
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.
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.
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.
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.