Echo — Community Chat
A platform designed around roles, permissions, and trust. Every feature answers a structural problem: who can do what, and how do we know it worked?
Platform Overview
Echo organises a community around two channel types: Information and Community. This separation lets members find what they need — rules and announcements sit in one place, conversation and support in another.
# Information
- #rules
- #announcements
# Community
- #general
- #creations
- #support
🎙️ Voice
- Lounge
Live metrics at a glance: The community runs 1,284 members total, with 37 currently online. Health score sits at 98.6% — a number driven by consistent moderation, clear rules, and role-based accountability. That score isn't vanity; it's feedback on whether the system is working.
Member Hierarchy & Roles
Echo gives different people different powers. This isn't gatekeeping — it's clarity. Everyone knows what each role can do, and why.
Mira
Community Lead
Sets strategy, owns health metrics, shapes culture. Mira has full visibility into moderation actions and can adjust system-wide settings.
Jamie
Creator
Posts content, engages in #creations. Can unlock special perks through friend codes. No moderation power — creator and moderator are separate roles.
Rowan
Moderator
Reviews reports, enforces rules, uses quick-action tools. Rowan's actions are logged and visible to Mira. Trust, but verify.
Everyone Else
Members
Read and write in Community channels. Can report safety concerns. Access is tiered — some members unlock Creator Lounge or other perks with codes.
The Access-Code System
Codes are the bridge between openness and control. They let the community grow without sacrificing safety or experience design.
Friend Codes
Examples: FRIEND-ORBIT, FRIEND-NOVA
Friend codes unlock perks: Creator Lounge access, exclusive welcome packs, early feature access. Each code has a limited redemption pool — they're gifts, not infinite. This creates two forces: members feel special when they receive one, and the community grows intentionally rather than explosively.
Admin Codes
These unlock the Administrator Control Center. Only authorised admins know them. They're rotated on schedule and revoked immediately if trust breaks.
The design philosophy: friend codes are meant to be shared and celebrated. Admin codes are meant to be kept, audited, and accountable. Different tools for different needs — no mixing them up.
Why this matters: A code system replaces vague "apply and maybe we'll approve you" with clear, frictionless onboarding. New members know exactly what they're getting. Moderators aren't drowning in verification requests. The community grows on its own terms.
Administrator Control Center
Where moderation happens. Every action logged, every decision traceable.
Verified as Alex Morgan
Slow Mode
Enforce a 10-second delay between messages in a channel. Use when conversation gets heated or off-topic. The delay isn't punishment — it's a pause button that lets people think.
Invite Approval
Review new member invites before they're activated. A moderator sees the invite, checks context, then approves or denies. One extra step that filters out spam and bad actors.
Media Filter
Automated scanning of uploads in public channels. Flags potential violations for manual review. Technology handles scale; humans make the call.
All admin actions are logged to an audit trail. If Rowan enables Slow Mode, Mira sees it. If a member is warned, it's timestamped and documented. This isn't about suspicion — it's about accountability. Moderators can act with confidence because their decisions are visible and defensible.
Quick Moderation Tools
Speed matters. The faster a moderator can respond to a problem, the less damage it does.
Templated Announcements
Post to #announcements with a single click. Examples: "Reminder: Keep spoilers in threads," or "This week's theme is..." Moderators don't draft messages in a panic. They select a template, maybe edit one line, and post. The announcement goes to everyone at once. Consistent tone, zero latency.
Member Safety Report Queue
Reports come in from members who see something wrong. They land in a dedicated queue. Each report shows context: the flagged message, who reported it, why. A moderator reviews, takes action (warn, mute, remove), or dismisses it. No guessing. No back-and-forth. Just facts and a clear path forward.
Design principle: Every second a moderator spends hunting for tools or drafting responses is a second the problem persists. Echo eliminates friction so moderators can focus on judgment calls, not mechanics.
What This Project Demonstrates
This isn't just a chat interface. It's a working system designed around the constraints and trust dynamics of community moderation.
Role-Based Permission Systems
Different people need different powers. The design makes those boundaries explicit and enforces them everywhere — no exceptions, no confusion.
Access & Invitation Flows
Codes, approvals, and onboarding screens that scale. You can grow a community without drowning in verification requests or sacrificing quality.
Trust & Safety Tooling
Reports, approvals, and audit trails. Every action is logged and visible. Moderators have the tools to enforce rules confidently.
Health Metrics
That 98.6% score isn't arbitrary. It's a live feedback loop showing whether the system is actually working. Is the community healthy? The number says yes or no.
This work is for teams building community platforms who understand that every feature is also a policy. The prettiest chat app fails if people don't trust it. Echo prioritises that trust through systems thinking: clear roles, limited access, documented actions, and real metrics.