Setting Up a Discord Server for Your ERLC Community

The most common Discord setup mistake is creating channels without a plan. Define your channel categories first:

• Information channels: Read-only channels where leadership posts announcements, rules, and reference documents.
• Community channels: General conversation, off-topic, and member-to-member interaction.
• Operations channels: Channels tied to specific department functions — patrol discussion, dispatch, radio logs.
• Staff channels: Private channels visible only to staff for coordination and moderation.
• Application and ticket channels: Where members submit applications, appeals, or support requests.

Roles control access and represent identity. Design your role structure to serve both functions:

• Create roles that map directly to your rank hierarchy — every rank gets a role.
• Create department roles that give access to department-specific channels without duplicating rank roles.
• Use a guest or member role for new joiners that grants limited access until they verify or are processed.
• Assign role colors intentionally — colors should signal rank tier, not be assigned arbitrarily.

Overly permissive servers are harder to moderate. Set permissions at the category level to reduce duplication:

• Apply base permissions at the category level so all channels in a category inherit the same access rules.
• Override at the channel level only when a specific channel needs different access from the rest of its category.
• Revoke @everyone's ability to send messages in announcement and rules channels — these should be read-only.
• Restrict voice channel access to members who have been properly onboarded — do not leave it open by default.

A small set of well-configured bots handles most routine moderation and utility tasks:

• Moderation bot: Handles automatic warning logs, anti-raid protection, and spam filtering. MEE6, Carl-bot, or Dyno are common choices.
• Ticket system: For member support requests and applications. Ticket Tool or its equivalents are widely used.
• Verification bot: Prevents bot raids by requiring new members to verify before accessing the server.

Do not add bots for every function. Each additional bot increases the surface area for permission errors and outages.

New members should not have to figure out how your server works on their own:

• Create a #start-here channel as the first channel visible to new members. It should explain what the server is, what the member needs to do first, and where to go for help.
• Use a rules-acceptance gate — require members to react to the rules before accessing the full server.
• Keep your welcome message brief. A wall of text is ignored. Three to five sentences is sufficient.

Discord servers accumulate structural debt — unused channels, outdated pins, role bloat:

• Audit your channel list every 60 days. Remove or archive channels that have been inactive for more than 30 days.
• Review role assignments monthly — members who have left may still hold roles.
• Keep pinned messages current. Outdated pinned messages reduce trust in the information that is there.
• Update the server icon and banner when your branding changes. Visual inconsistency signals neglect.