> ## Documentation Index > Fetch the complete documentation index at: https://hashbot.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Log Channel > Whenever Hashbot detects a match from your Blocklist (e.g. name, profile picture, or keyword), it will take action — such as banning the user — and send a report explaining **who was flagged and why**. ## Default Behavior By default, these moderation reports are sent via **DMs to the server owner**. However, we highly recommend configuring a **dedicated private log channel** within your server. You can also configure your log channel from the [Hashbot Dashboard](https://dashboard.hashbot.com) — along with all your other Hashbot settings. ## How to Set a Log Channel To direct Hashbot to post logs in a specific channel, use the following command: `/settings logging set channel:#your-log-channel` The channel must already exist before running this command. As you type the channel name, a dropdown will appear — select the channel from the list. For example: `/settings logging set channel:#hashbot-log` You can also create a log channel directly from the [Hashbot Dashboard](https://dashboard.hashbot.com) — click the **+** button next to the log channel selector to auto-create a `#hashbot-logs` channel. ### Disabling the Log Channel To stop sending moderation reports to a channel and revert to DMs: `/settings logging disable` ## Required Channel Permissions Make sure Hashbot has the following permissions **in the log channel**: * View Channel * Send Messages * Read Message History To configure this: 1. Right-click on the log channel → **Edit Channel** 2. Go to **Permissions** 3. Under the **Hashbot** role, enable the permissions listed above 4. Save changes Once configured, all moderation actions will be posted in that channel instead of via DM — making it easier for your team to track and review activity.