Moderation
Tools for member actions and calmer conversations.
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.
The relevant Discord permission is needed for each action, such as Moderate Members, Kick Members, Ban Members or Manage Messages. Role hierarchy still applies.
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.
- Check the policy: Read Policy & permissions before taking action. The current warning and timeout policy is fixed; this page does not create custom rules.
- Review a case: Open Cases & sanctions, choose a tab and select a record. Read the evidence and history before using any staff action.
Check it works
Confirm a known case opens and its history is correct. Use a controlled test server for destructive actions; do not ban a real member just to test setup.
How it works
Member actions include warnings, timeouts, kicks, bans and their supported reversal commands. Channel tools include purge, slowmode, lock and unlock.
A timeout has the duration choices exposed by the command. Discord owners and higher roles cannot be moderated by moving a dashboard switch.
The dashboard supports checked moderation actions, case notes and resolution. Custom aliases and an arbitrary rule builder are not available.
Review cases and linked sanctions
Use the case list, search reasons or filter by member. Open evidence and history before resolving or leaving a case note. Member actions and message removal recheck permissions and role hierarchy; protected owners, yourself and the bot cannot be targeted.
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.