Start here / Watchpost
Server setup
A small, workable channel structure for your staff team.
Suggested channels
| Channel | Purpose | Audience |
|---|---|---|
| #staff-chat | Day-to-day coordination | Staff |
| #staff-logs | Moderation and configuration records | Relevant staff only |
| #session-planning | Host notes and handovers | Hosts and leads |
| #sessions | Session announcements | Community |
| #bot-testing | Test released features | Selected testers |
These names are suggestions. Keep your existing channels if they already serve the same purpose; creating them does not connect Watchpost automatically.
Assign responsibilities
Owners control installation and sensitive settings. Staff leads review cases and resolve corrections. Moderators handle the actions assigned to them. Session hosts run events. One member can hold more than one role, but each responsibility should have a clear owner.
Review before launch
- Check private channels from a normal member account.
- Make sure staff can find the current rules and escalation route.
- Decide who receives reports when a host or moderator is unavailable.
- Keep a short record of configuration changes and who approved them.
Do not put API keys, bot tokens or credentials in channel topics, pinned messages or screenshots. See data and safety for handling sensitive information.