Log forwarding¶
Send read-only copies of your server's moderation logs to a Discord channel you choose, usually in another server: a partner community, an allied group's staff, or your own archive. LogDog posts each copy through a webhook that the receiving server makes and gives you.
Your own logs don't change. A copy has no buttons and carries only what is safe to share outside your server (see What a copy contains).
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Administrator to add, change or remove forwards. |
| The receiving server | A webhook on the channel the copies go to, made by someone with Manage Webhooks there. Forum channels aren't supported yet. |
| Plan | Free: 2 forwards. Premium: 25. |
Events you can forward¶
A forward copies any of these seven events. All seven are picked by default, and you can change the choice at any time.
| Event | What it records |
|---|---|
| Group User Ban | Banned from the group. Can't join until unbanned. |
| Group User Unban | A ban was lifted. |
| Group Member Remove | Removed from the group without a ban. They can rejoin. |
| Group Instance Kick | Kicked from one instance by a moderator or a vote. Still in the group. |
| Group Instance Warn | A moderator warned someone in an instance. |
| Group Request Reject | A join request was turned down. They can ask again. |
| Group Request Block | A join request was turned down and the person blocked from asking again. |
A forward copies only what LogDog posts in your server. An event you've turned off in Log Routing is not forwarded either.
Set it up¶
- In the receiving server, open the channel's Settings, then Integrations, Webhooks, New Webhook, and Copy Webhook URL.
- On the dashboard, open Settings, then Log forwarding, and press Add forward.
- Paste the Webhook URL, give the forward a Label if you like (the webhook's name otherwise), and pick the Events to copy.
- Save. LogDog sends a test message to that channel first: nothing is saved unless the test message lands.
Anyone who can see that channel can read the copies
Copies go to a server you choose. Removing a forward stops new copies but does not delete ones already posted.
What a copy contains¶
| A copy shows | A copy never shows |
|---|---|
| The event's name | Anything from Discord: linked accounts, Discord names, mentions, or who added the reason |
| Your group's name and link | The person's VRChat bio |
| Who the event is about, and their VRChat user ID | Images |
| The moderator's VRChat name | Buttons |
| The world, for a kick or a warn | Anything else from your log |
| Their trust rank, except Known and Trusted (ranks VRChat lets players hide) | |
| Their age verification, as VRChat shows it to everyone | |
| When their VRChat account was created | |
| Their Group History, and for an unban, when and why they were banned | |
| The reason | |
| When it happened |
If a reason is added or changed later, LogDog updates the copies posted in the last month.
Manage your forwards¶
Each forward lists its state, how many copies it has sent, when it last sent one, and its events. Send test posts a test message, Edit changes the label and events, Duplicate starts a new forward with the same label and events (you paste its webhook), and Remove deletes it.
| State | What it means |
|---|---|
| Active | Copies are being sent. |
| Active, waiting on Discord | Discord asked LogDog to slow down. Copies resume on their own. |
| Paused | You paused it with Pause. Nothing is sent until you press Resume. |
| Paused: Premium | Your server went back to Free with more forwards than Free allows. Your oldest two keep sending; the rest wait until Premium comes back or you remove some. |
| Broken | Discord no longer accepts the webhook: it was deleted, its token was refused, or it isn't allowed to post. Copies stop, and the dashboard bell tells your admins. Press Replace webhook with a new URL, or remove the forward. |
Privacy¶
A forward shares moderation information with another server, where that server's own settings and Discord's policies apply to it. Forward only to channels whose readers are allowed to see it. See the Privacy Policy for how LogDog handles this information.