General settings
Understand the workspace and when settings take effect.
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.
Only the configured owner can manage this workspace.
Set it up
- Choose your features: Open Feature availability and choose the optional modules you want to use.
- Save and apply: Save the switches first. Then open Apply feature availability and review the confirmation before applying them.
- Check the outcome: Open Change history to see the settings change and availability receipt. Inspect partial or uncertain outcomes before trying again.
Check it works
Check the enabled commands in Discord and the saved availability outcome. A saved switch alone does not confirm that it has been applied.
How it works
Features are grouped into protection, welcome and support, and engagement. Documentation remains public even when management is restricted.
Settings marked for restart are stored immediately but read by their service on startup. A pending badge means the saved value and the running value differ.
Open Settings changes in General to inspect the recorded account, authentication source, time and before/after values. History is saved in the same transaction as the settings change; a rejected stale save adds no change.
Open Availability outcomes to inspect earlier reconciliation receipts, including failed or unconfirmed results. Inspect Discord and the recorded outcome before trying another effect. Acknowledging a receipt does not repair an uncertain delivery.
The dashboard does not open staff access, change bot ownership or install Vault into another server. Those are separate access and deployment concerns.
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.