Skip to content
MODERATORDocs

Anatomy of a Secure Server

Last updated: Apr 24, 2026View as Markdown

import { Steps } from ‘@astrojs/starlight/components’;

The visual organization and permission configuration of channels in Discord is not merely an aesthetic concern: it is your first line of defense against coordinated raids, automated spam, and member confusion.

Section titled “Recommended Category Architecture”

A clean, battle-tested server architecture isolates unverified newcomers from active community spaces:

📁 WELCOME & MANDATORY READING
   ├── 📜 #rules-and-guidelines
   ├── 📢 #official-announcements
   ├── 🧭 #server-guide
   └── ✅ #verification-gate


📁 COMMUNITY & CONVERSATION
   ├── 💬 #general-chat
   ├── 💡 #ideas-and-feedback
   ├── 🎨 #media-and-showcase
   └── 🤖 #bot-commands


📁 SUPPORT & TICKETS
   ├── ❓ #faq-and-help
   └── 🎫 #open-a-ticket (Ticket bot panel)


🔒 STAFF OPERATIONS (Hidden from @everyone)
   ├── 🛡️ #staff-chat
   ├── 🚨 #automod-alerts
   ├── 📋 #audit-logs
   └── 📜 #moderation-protocols

The Secure Onboarding Funnel

Section titled “The Secure Onboarding Funnel”
1. **Neutral Initial Access**: The `@everyone` base role must have *Send Messages*, *Add Reactions*, and *Connect* disabled across all standard community channels. 2. **Verification Gatekeeper**: Incoming accounts should only see introductory channels (`#rules-and-guidelines` and `#verification-gate`). 3. **Discord Membership Screening**: Require users to explicitly agree to your community rules using Discord's native verification screening before obtaining any chat privileges. 4. **Granting the `@Member` Role**: Upon completing verification (via button interaction, captcha bot, or onboarding flow), assign the primary base role that unlocks public channels.