Skip to main content

Platform Setup

A well-structured community platform makes the difference between a space people visit daily and one they abandon after a week. This lesson covers how to set up Discord and Slack for community success, including channel architecture, roles, permissions, and onboarding.

Discord Server Structure

Discord organizes content into categories (groups of channels) and channels (individual conversation spaces). A clean structure prevents overwhelm and helps members find what they need.

Recommended category structure for a community server:

Welcome & Info

  • #welcome — read-only channel where new members land. Include a brief overview of the community, rules, and how to get started.
  • #rules — community guidelines (covered in the next lesson)
  • #introductions — members introduce themselves. This is the first interaction point and sets the tone.
  • #announcements — read-only channel for important updates from the team

General Discussion

  • #general — open conversation about anything related to the community topic
  • #off-topic — casual conversation, memes, and non-topic discussions. This channel humanizes the community.
  • #questions — a dedicated space for asking questions. Keeps #general from being overwhelmed with help requests.

Topic Channels

Create 3-5 channels based on your community's focus areas. For a marketing community:

  • #content-strategy
  • #social-media
  • #seo
  • #paid-ads
  • #tools-and-resources

Do not create too many channels at launch. Start with 8-12 channels total and add more as the community grows and members request them. Empty channels feel like a ghost town.

Voice & Events

  • Voice channels — for live discussions, coworking sessions, or casual hangouts
  • #events — schedule and promote community events like AMAs, workshops, or watch parties

Discord Roles & Permissions

Roles control what members can see and do. Set them up thoughtfully:

  • @Admin — full server control. Limit to 2-3 trusted people.
  • @Moderator — can manage messages, mute users, and manage threads. No server-level changes.
  • @Member — standard verified member with access to all public channels.
  • @New Member — limited access until they complete onboarding (e.g., only see #welcome and #introductions).

Permission tips:

  • Lock #announcements so only admins can post
  • Use slow mode on high-traffic channels (e.g., one message per 30 seconds) to prevent spam
  • Create private channels for moderators to coordinate
  • Use auto-roles so new members get the @New Member role automatically

Slack Workspace Setup

Slack's structure uses channels (public or private) and sections to organize conversations.

Recommended channel structure:

  • #welcome — pinned post with community overview and guidelines
  • #introductions — new members share who they are and what they do
  • #general — main discussion channel
  • #random — off-topic and casual conversations
  • #resources — curated links, tools, and learning materials
  • 3-5 topic channels — based on your community's focus areas
  • #feedback — members suggest improvements to the community

Slack-specific tips:

  • Use channel descriptions to clarify each channel's purpose
  • Set channel posting guidelines in the channel topic
  • Use Slack's Workflow Builder to create automated welcome messages
  • Pin important messages in each channel so new members can catch up

Onboarding Flows

The first 5 minutes after joining determine whether a new member stays or leaves. A strong onboarding flow:

Step 1: Welcome Message

When a member joins, they should immediately receive a welcome message — either from a bot (Discord) or workflow (Slack). Include:

  • A warm greeting
  • Three things to do first (e.g., "1. Read the rules in #rules, 2. Introduce yourself in #introductions, 3. Jump into #general and say hi")
  • A link to community guidelines

Step 2: Introduction Prompt

In the #introductions channel, provide a template:

  • Name and location
  • What they do (role, industry, interests)
  • One thing they hope to get from the community
  • A fun fact (optional but humanizing)

Step 3: Role Assignment

On Discord, use a bot like Carl-bot or MEE6 to assign roles based on reactions. Post a message in #welcome like: "React with the emoji that matches your interest: fire emoji for marketing, chart emoji for analytics, art emoji for design." This personalizes their experience and gives them access to relevant channels.

Step 4: First-Week Engagement

Tag new members in relevant discussions during their first week. A simple "Hey @newmember, you mentioned you are into SEO — check out this thread!" makes them feel seen and connected.

Technical Setup Checklist

Before opening your community to members:

  • All channels created with clear names and descriptions
  • Roles and permissions configured and tested
  • Welcome message and onboarding flow active
  • Community guidelines posted and visible
  • At least 10-20 seed messages in key channels (nobody wants to be the first person to post in an empty room)
  • Moderation bots installed and configured (Discord: MEE6, Carl-bot, or Dyno)
  • Invite link ready with appropriate settings (expiration, usage limits)

Seed the community with content and conversations before inviting your first cohort. A community that looks active from day one retains new members far better than one that feels empty.