Choose the right server.
Before adding the bot
Use a Discord account that can manage the server. Review the permissions shown in Discord before you approve the installation.
Your first /audit
Add GuildAudit.
Read your first sample.
You will start in Discord, then read the report with your moderators. You do not need a paid plan to try the first audit.
In order
Keep the first run simple.
These instructions describe the starting path. The examples on the website are fictional; your report depends on the activity that is actually sampled.
Run /audit in Discord.
Your first command
Start with the free audit. It produces a report from an activity sample, which may not cover the entire server.
/auditRead what was sampled.
With your moderators
Look at the messages and participants in the report. Ask which channels, times or events might explain what you see.
After the report
Use it to ask a better question.
A small sample does not establish retention, explain why someone left or prove that an intervention worked.
Add the context only staff knows.
A quiet sample could reflect a quiet time of day, a specialised channel or a recent event. Check those possibilities before choosing an action.
Ask for help if something is unclear.
Tell support which command you used and what the report or error showed. Do not include private conversations, tokens or member information.
Join support →You may see /report, /history and paid concepts in the site’s design examples. Those illustrations do not verify current command availability or demonstrate improvement. Start with /audit.
Ready when you are
Start in the server you manage.
Review the requested permissions in Discord. Once GuildAudit is added, run /audit and read the sample with your moderators.