Slack Workspace Architecture

8.1 Rationale: Why Structured Slack Matters for Multi-Chapter Communities#

A Slack workspace is not just a messaging tool - for a global community like The AI Fellowship, it is the primary connective tissue between chapters, members, and the central team. Without intentional architecture, a multi-chapter Slack workspace becomes fragmented and noisy: conversations happen in the wrong channels, new members feel lost, important announcements get buried, and chapters operate in silos.

Structured Slack delivers five things that matter for The AI Fellowship specifically:

1. Belonging at scale. A new member joining from Lagos should feel as welcome and oriented as one joining from London. Clear channels, warm automated messages, and predictable structure remove friction from the first experience.
2. Chapter autonomy without chaos. Chapters need their own spaces to operate, but naming conventions and templates ensure the workspace remains navigable to everyone.
3. Signal-to-noise discipline. A community this distributed cannot afford notification fatigue. Thoughtful channel purpose definitions and @mention norms protect members’ attention - the most valuable resource in any community.
4. Institutional memory. Pinned messages, channel descriptions, and archiving policies ensure that knowledge doesn’t walk out the door when a Director changes.
5. Operational transparency. The center and chapters should be able to see what’s happening across the community without constant status check-ins. The right channels make activity visible.

8.2 Complete Channel List#

Legend for Table#

• Post Access: Who can send messages in this channel
• Read Access: Who can see the channel (all = all workspace members)
• Moderation Owner: Who is responsible for keeping it on-topic and handling issues

Global Channels#

Chapter Template Channels#

8.3 Onboarding Bot Flow Concept#

When a new member joins the workspace, the following automated flow fires:

Trigger: Member joins workspace

Message 1 - Immediate (within 60 seconds)#

From: @AIFellowship Bot

Welcome to The AI Fellowship, [First Name]!

We're a global community of people who believe AI can be a force for good - and that the people building it should know each other.

Here's what to do first:

1. Head to #introductions and say hello (tell us your city, what you're working on, and one thing you're hoping to learn or build here).

2. Read our Community Code of Conduct pinned in #code-of-conduct

3. Explore #projects-showcase to see what our community is building.

Your chapter coordinator will reach out within 48 hours. If you're not assigned to a chapter yet, reply here and we'll sort it out.

Glad you're here.

Message 2 - Day 2 (if no introduction posted)#

From: @AIFellowship Bot

Hey [First Name] - just a nudge! We noticed you haven't introduced yourself yet in #introductions. No pressure, but a quick hello goes a long way in a community like this. People are genuinely curious about who just joined.

Message 3 - Day 7 (First Week Check-In)#

From: @AIFellowship Bot

One week in! Here's a quick orientation checklist:

- [ ] Posted your intro in #introductions

- [ ] Joined your chapter channel (#[city]-general)

- [ ] Signed the Member Pledge (link)

- [ ] Connected with at least one other member

- [ ] Attended or RSVP'd to an upcoming event

If anything's unclear or you haven't heard from your Chapter Director yet, reply here.

Message 4 - Day 30 (Engagement Milestone)#

From: @AIFellowship Bot

30 days in, [First Name]! You're officially part of the community now.

Quick question: How's your experience been so far? Drop your honest feedback in #feedback-and-ideas - we read everything.

And if you're ready to go deeper: Is there a project you want to start? A study group you want to run? A hackathon you want to organize? Reach out to your Chapter Director. The Fellowship is what you make it.

8.4 Channel Archiving Policy#

Slack channels accumulate over time. Unarchived dead channels degrade discoverability and signal that the community is less active than it is.

Archiving process#

1. Post a final message: “This channel is being archived on [date]. Content will remain accessible but no new messages will be possible.”
2. Pin any key links or handoff notes.
3. Archive the channel.
4. Archived channels remain searchable and readable - they are not deleted.

Renaming: Channel renames require Global Admin approval. Post a notice in the channel 72 hours before renaming.

8.5 Notification Norms#

Notification fatigue is one of the fastest ways to lose engaged members. These are community-wide standards, not suggestions.

@here (notifies active members in the channel)#

• Use: Time-sensitive, channel-relevant needs. “We need 2 more volunteers for tonight’s event - who’s in?” in #london-events.
• Avoid: General questions that can wait. Information that isn’t truly urgent.
• Permission: Any member in chapter channels. Community Manager + Directors in global channels.

@channel (notifies ALL members of the channel, including inactive)#

• Use: Critical announcements affecting all channel members. Policy changes. Event cancellations.
• Avoid: Everything else.
• Permission: Directors in chapter channels. Central Team only in global channels.

@everyone / @workspace#

• Use: Reserved for Global Admin only. Extreme circumstances (safety, workspace-wide policy change).
• Avoid: Basically everything.

General Norms#

• Thread replies for all responses to a message in high-volume channels. This is not optional in #general, #help-and-questions, and #resources.
• Do not DM Chapter Directors for questions that belong in a channel. Public channels create shared knowledge.
• Avoid posting the same message in multiple channels (“cross-posting”). Choose the most appropriate channel.

8.6 Admin Hierarchy#

8.7 A Note on Slack Alternatives#

Slack is the right choice now. It is professional, feature-rich, and familiar to the technical audience The AI Fellowship serves. However, Slack’s free tier limitations (90-day message history) will become a problem as the community scales, and Slack’s per-seat cost for paid plans can become prohibitive for a volunteer-led organization.

At approximately 500+ active members, it is worth evaluating:

Recommendation: Monitor Slack costs and message history complaints at 6-month intervals. If the community crosses 500 members or Slack free-tier limitations begin causing knowledge loss, initiate a migration working group. Do not migrate reactively - plan 3 months in advance with full member communication.