Logging
Route important events into channels your team can follow.
Before you start
Dashboard changes are currently restricted to the configured Yume owner. Sign in with Discord and choose Yume. Public documentation is available to everyone.
Vault needs View Channel and Send Messages in each log destination. Do not make a log channel public simply to resolve a permission error.
Set it up
- Check feature availability: Open General settings → Feature availability. Enable this module, save, then use Apply feature availability to update the running bot.
- Choose log channels: Open Log destinations and choose a channel for moderation, message and member events. An empty destination is not a configured log channel.
- Save and inspect: Save the destinations, then open Recent log messages to inspect the entries Vault can read.
Check it works
Check a harmless test message edit in Discord. Deleted-message content may be unavailable if Discord did not provide it.
How it works
Message logging covers supported edits and deletions. Content is only available when Discord provides it to the bot; older or uncached messages can have incomplete information.
Member logging covers joins, departures and role changes. The moderation log destination covers the supported ban and unban events.
Leaving a destination unset stops delivery for that category. Logging records can include private content and identifiers: review channel visibility before enabling them.
| Setting or command | What it means |
|---|---|
| Moderation log | Ban and unban events. |
| Message log | Supported message edits and deletions. |
| Member log | Member joins, departures and role changes. |
Staff actions, privacy and refresh
Staff actions require Discord sign-in and current authorized server access. Recovery sign-in supports settings only. Review the exact confirmation before submitting; changes and partial deliveries have a request receipt.
An uncertain outcome is not a confirmed failure. Check the receipt, record and Discord before acknowledging it. Acknowledgment does not retry an effect or remove the server’s duplicate-action protection. Safe notes and other records remain usable; unresolved effects require owner investigation.
Active workspace pages refresh every 30 seconds and Overview every minute while visible. Refresh pauses for drafts or focused controls. Manual refresh preserves edits; a changed staff record requires explicit review before keeping its draft. Private drafts remain in this tab and are not saved in browser storage.
Use Save after editing. If a change is marked as requiring a restart, it is stored but will only apply when Vault next starts. Refresh after the restart to check the pending indicator.
If something is not working
Check that the feature is enabled, that the selected channel or role still exists, and that Vault has the required Discord permissions. A higher role cannot be assigned or moderated by a bot below it.
If the dashboard cannot load or save, keep your edits on the page, check Status, then try again. An expired session requires signing in again. Do not repeatedly submit an action whose result is uncertain.