Applications
Control intake while keeping reviews in the team’s workflow.
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 owner can change intake from this dashboard. Keep application review channels restricted to the appropriate team.
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.
- Open recruitment: Vault creates the application panel in the configured Yume applications channel when it starts with Applications enabled. Give Vault View Channel, Send Messages, Embed Links and Read Message History there. If it is missing, ask the bot operator to check the configured channel and restart Vault. Once the panel exists, open Recruitment intake here to open or close applications.
- Review submissions: Open Moderator applications, choose a submission and review the answers. Record a reason before confirming a decision.
Check it works
Submit a controlled application through the Discord panel and confirm it appears. Check the notification receipt separately from the saved decision.
How it works
The pending count reflects the application records returned by the bot. If the service cannot load them, the dashboard shows an error instead of pretending there are zero applications.
Closing intake does not remove submissions or decide their outcome. The dashboard records application review decisions and separately reports review-message and direct-message delivery. Approval does not grant a staff role.
Review and manage intake
Review submitted answers, choose approve, deny or request information, and record a reason. Approving records the decision without granting a role. Changing intake updates an existing Vault-owned panel; create or repair a missing panel in Discord before changing intake. A failed direct message does not undo a saved decision.
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.