Connect Discord and check the destination

Protect the webhook and understand which actions send messages to the channel.

Who this is for: Managers configuring the channel that receives reports.

Before you start

Management permission in DWS Stats and a channel webhook provided by someone who can administer it.
Treat the URL as a secret; an invitation link is not a webhook.

Open Discord settings from your alliance
Check the alliance and intended receiving channel. Do not paste the webhook into a public field, screenshot or support request.
Save the connection and distinguish the test
The URL is stored encrypted and then shown masked. Send test sends a real message to the configured destination; check with the channel that it is correct.
Review before sending reports
Saving a connection does not send a report. Scheduling and sending are configured separately. Disconnect acts immediately and does not delete saved reports.

The correct channel is connected and the destination check was performed knowing that the test sends a message.

The test fails: Check that the webhook is still active and that the channel administrator supplied the correct URL. Do not publish the secret to ask for help.
I want another channel: Use the new channel's webhook and check the destination. Reconnecting after disconnection requires entering the URL again; the masked reference cannot recover the secret.

Panel actions check your permissions and show the current limits. This guide does not grant access or save or send anything by itself.