Guides
Short staff checklists for each module. For full dashboard walkthroughs, open the matching page under Dashboard in the docs sidebar. For slash syntax, see the command reference.
Setup
Build the server once and keep it consistent.
- Open the dashboard → Setup → Discord Schema and apply a starter layout or keep your current channels.
- Map staff roles under Permissions so only the right people can run /mod and /security.
- Save a backup before importing, you can roll back from Setup → Templates & Backups.
Safety
Stop raids and abuse before they spread.
- Set a log channel and turn on anti-raid / account-age gates before sharing invites.
- Enable quarantine so flagged joins land in a locked role.
- Tune Content & spam (links / Domains) after Foundations is green.
Onboarding
Get new members into the right place fast.
- Pick a welcome channel and a verification role in Onboarding.
- Add reaction roles for games, regions, or pronouns after verify.
- Test with a second account so the first message is intentional.
Moderation
Keep chats clean and keep a record of what staff did and why.
- Enable word and spam filters under Safety → Content & spam; set the warn ladder under Moderation → Settings.
- Run /mod warn, /mod mute, and /mod ban, cases appear in the dashboard.
- Review Cases and Appeals during shifts; set the mod log channel under Settings.
Tickets
Support without the usual ticket-bot clutter.
- Create a panel in Tickets, then deploy where members click.
- Assign support roles so staff can claim and close.
- Point transcripts at a private log channel.
Analytics
Act on joins, leaves, and mod volume, not vanity charts.
- Enable tracking for the guild, then open Analytics for Overview / Activity / Leaderboards.
- Use Logs when you need the raw events behind a spike.
- Check both after a raid or event, that’s when the graphs matter.