Auto moderation
Understand the protection policies running in Yume.
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.
Automatic actions need the same Discord permissions and role hierarchy as the corresponding manual actions.
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.
- Understand enforcement: Read Policy & permissions for the message and account policy, including the effect of each appeal decision.
- Inspect the review queues: Open Appeals and switch between appeal reviews, enforcement cases and sanctions. Read linked evidence before deciding an appeal.
Check it works
Inspect an existing case or appeal. An empty queue means there is nothing to review; it does not prove every enforcement rule was tested.
How it works
Vault includes the message policy and moderation lifecycle implemented for Yume, including fresh-account handling and timed actions.
Enabling a module does not let you create new custom rules in this dashboard. Existing rules and enforcement behavior remain defined by the current bot implementation.
If a legitimate member is affected, review the specific action and use the existing appeal or moderation workflow. Do not disable all protection as a substitute for understanding an individual case.
Review an appeal
Open the appeal, read its linked case and sanction, then choose an explicit decision and factual reason. Head Moderator or above is required by the shared review policy. An accepted active temporary-ban appeal waits until the original expiry; denial makes that linked ban permanent.
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.