Community

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 access to each configured channel. Birthday role assignment requires an assignable role beneath Vault.

Set it up

1. Check feature availability: Open General settings → Feature availability. Enable this module, save, then use Apply feature availability to update the running bot.
2. Choose an activity: Open Confessions, Counting, Birthdays or Question of the Day. Start with one activity and choose its channels and optional roles.
3. Save and apply settings: Save the activity’s editor. Settings marked Waiting to apply are stored until the running configuration reloads or Vault restarts.

Check it works

Check the chosen activity in Discord. Keep anonymous submissions in their review queue and never reveal an identity just to test the page.

How it works

Confessions have separate submission and reply cooldowns, text limits and report limits. Review-required changes how new submissions are handled.

Counting’s starting number is a fallback when there is no recoverable recent sequence; it is not a button to reset an active channel.

Birthdays use the configured IANA timezone, such as Europe/London, to decide when a day begins. The birthday role is temporary.

Question-of-the-day configuration includes the channel and the role used in its permission setup. Check access before changing either.

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.

Review anonymous submissions

Use the confession and report queues to approve, deny, remove, lock replies or resolve a report. Anonymous records omit the author and reporter. Only the configured Discord owner can confirm an audited reveal; the identity is transient and clears when leaving the view. Member restrictions have recorded reasons and durations. Changing review mode applies to new submissions after configuration is applied.

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.