Set up a RestoreCord log channel for your morning check
The daily routine is only as good as the thing you read. Ten minutes of setup gives you one private channel that tells the whole story of the night.
Short answer
Create a staff-only Discord channel, add a webhook under Integrations, paste its URL into Webhook Logs on the Security tab of your server in the RestoreCord dashboard, save, then verify with a staff account to confirm messages arrive.
Why one channel beats five dashboards
Most owners who skip their daily check don't skip it out of laziness. They skip it because the information is spread over the dashboard, Discord's audit log, a moderator's DMs and their own memory. RestoreCord's Discord webhook logs pull the most time-sensitive part of that, everything that happens at your front door, into a single channel you can scroll on your phone before you're properly awake.
Setting it up
- Create a text channel that only trusted staff can read. Lock it down before anything is posted there.
- Open the channel's settings, go to Integrations → Webhooks, create a webhook and copy its URL.
- In RestoreCord, open Dashboard → Servers → Manage → Security, switch on Webhook Logs and paste the URL.
- Save, then verify with a staff account. A Successfully Verified message should land within moments.
Give the webhook a name and avatar your team recognises, such as RestoreCord Logs. During a busy morning it stops log messages blending into chat.
What lands in the channel
RestoreCord has a separate log embed for each kind of event, so you can tell them apart at a glance while scrolling:
| Embed | When it's sent | What to look for in the morning |
|---|---|---|
| Verified | A member finished verification | Clusters of brand-new accounts minutes apart |
| Blocked | A member was stopped, for example as an alt or for account age | The same reason repeating all night |
| Firewall | A firewall rule allowed, denied or accepted a password | Password use far above your usual day |
| Bypass | An admin granted someone a bypass | Any bypass you can't match to a staff decision |
Bypass messages deserve special attention. A bypass is a deliberate exception, so every one should have an owner on your team. If nobody remembers granting it, that's the first question of the day.
Choosing how much detail to log
Show information in webhook logs
This option decides whether each message carries extra verification data or just a simple success line. Moderation-heavy servers want the detail; a small hobby server may be happier with the short version. From Premium, you can also show IP address and location and add the member's Discord account badges.
IP Logging
IP and location fields only appear when IP Logging is switched on in your server's Security settings. If it's off, read the log as a record of who came in and whether they were stopped, not where they connected from.
A Discord webhook URL works like a password: anyone holding it can post into your channel. If it's ever pasted somewhere public, delete the webhook in Discord and set a new URL in RestoreCord.
Turn the scroll into a note
Reading is half the habit; the other half is writing one short line about it. Pin a template like this in a staff thread and copy it each morning:
Daily check, Tue 07:45 (rowan_02)
Log channel: 41 verified, 6 blocked (4 alt, 2 VPN), 1 bypass
Firewall: blocked in line with last Tuesday
Snapshot: daily backup finished 07:00
#verify: message live, button works
Audit log: nothing new
Follow-up: ask who granted the 06:20 bypassA week of these notes turns a vague feeling that something is off into a pattern you can point at.
With the channel in place, the five-minute daily checklist has something to read from day one. For the people side of security, follow up with the weekly access review, or go back to RestoreCord Daily.
Connect the log channel in four steps
Create a staff-only channel
Make a text channel that only trusted moderators can read, so sensitive verification details stay private.
Create a Discord webhook
In the channel settings open Integrations, then Webhooks, create one with a recognisable name and copy its URL.
Paste it into RestoreCord
Open Dashboard, Servers, Manage, Security, turn on Webhook Logs, paste the URL and save.
Send a test verification
Verify with a staff account and confirm the Successfully Verified message arrives in the channel.
How log detail grows with your plan
Every plan gets a log channel. Higher plans add more context to each message.
| Free | Premium | Business | Enterprise | |
|---|---|---|---|---|
| Discord webhook logs | Advanced | Advanced+ | ||
| Verification logging | Minimal | Basic | Advanced | Advanced+ |
| IP address and location in logs | — | |||
| Discord account badges in logs | — | |||
| Signed custom webhook to your endpoint | — | — | — |
Log channel questions
Wake up to a log that already did the reading
Connect RestoreCord, paste one webhook URL and tomorrow's check starts with the full story of the night.