Set up a Discord verification log channel with RestoreCord
A webhook log turns your staff channel into a live record of who verifies, who gets stopped and why. Setup takes a few minutes; getting the detail level right takes a little thought.
Short answer
Create a staff-only channel, add a Discord webhook to it, then paste the webhook URL under Security in your RestoreCord server settings and switch on Discord Webhook Logs. Run one staff verification to test. Logs are included on every plan.
Why a log channel beats checking the dashboard
Moderators live in Discord, not in a web dashboard. When RestoreCord posts each verification into a channel they already watch, problems surface while they are still small: a wave of refused alts, a member stuck behind a rule, a sudden silence on a day people normally join. It is the cheapest early-warning system a server can run, and it costs nothing on the Free plan.
Setting it up
- Create a channel such as #verify-logs and remove view access for everyone except trusted staff roles.
- Open the channel settings, go to Integrations → Webhooks, create a webhook and copy its URL. A name like RestoreCord Logs with a recognisable avatar helps staff spot the messages.
- In the RestoreCord dashboard open Servers → Manage → Security, switch on Discord Webhook Logs and paste the URL.
- Save, then verify once with a staff account and confirm a message arrives.
The four message types
| Log embed | Posted when | What moderators usually do |
|---|---|---|
| Verified | Someone completes verification | Nothing, unless several fresh accounts arrive together |
| Blocked | A check refuses the member, for example as an alt or on a VPN | Watch for the same reason repeating |
| Firewall | A firewall rule allows, denies or a password is used | Check that rules behave as intended |
| Bypass | An admin grants someone a bypass | Confirm the bypass was agreed |
Choosing how much detail to show
Each extra field is a separate switch in the Security tab, so you can match the log to how your team works.
| Option | Adds | Plan |
|---|---|---|
| Show Information in Webhook Logs | Extra verification data such as account age, connection type and device | Premium and above |
| Show IP Address and Location | Client IP, provider and location; only while IP Logging is on | Premium and above |
| Display Account Badges | The member's Discord badges | Premium and above |
| Custom log designs | Your own Message Studio embed for each of the four message types | Set per server |
Start lean. A busy server with every field switched on produces long messages that staff stop reading. Add detail when a moderator asks for it, not before.
Treat the channel as sensitive
Depending on your settings, log messages can contain IP addresses, locations and device details. That makes the channel, and the webhook behind it, worth protecting.
A Discord webhook URL is a bearer secret: anyone holding it can post into your channel. Limit who has Manage Webhooks, and if the URL leaks, delete the webhook and paste a new one into RestoreCord.
Reading it well
Look at patterns rather than names. A cluster of refusals with the same reason, several brand-new accounts within minutes, or an empty channel on a normally busy evening all deserve a second look. The raid warning signs guide covers what to do next, and the analytics guide shows how to tell a blip from a trend.
When people aren't the only audience
If you also want these events in a database, ticket system or alerting tool, Enterprise adds a custom webhook that sends signed JSON to your own endpoint. It lives in the same Security tab and runs alongside the Discord log. See receiving signed webhook events, or head back to RestoreCord Monitor.
Connect your log channel in four steps
Lock down a channel
Create a channel such as #verify-logs and hide it from everyone except trusted staff.
Create the webhook
In the channel settings, open Integrations, then Webhooks, make a new webhook and copy its URL.
Connect it to RestoreCord
Go to Dashboard, Servers, Manage, Security, switch on Discord Webhook Logs and paste the URL.
Run a test verification
Verify once with a staff account and confirm the message lands in the channel.
Log channel go-live checks
Run through these once the first test message arrives.
Channel hidden from members
Only staff roles can view the log channel, and ticket channels never receive logs.
Integration access limited
Just a few admins hold Manage Webhooks, so nobody else can copy or change the URL.
Detail level chosen on purpose
Extra information, IP and badges are on only if your moderators actually use them.
Notifications set for the channel
Staff who handle raids get pinged for new messages instead of discovering them hours later.
Test message confirmed
A staff verification produced a log message after every change to the webhook.
Data policy written down
Your rules say what member data the log shows, especially once IP logging is enabled.
Verification log questions
Give your moderators eyes on the door
Connect a webhook once and every verification shows up where your team already works.