Invites
See recorded invitation activity without overstating certainty.
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.
Invite information must be accessible to Vault through its configured Discord permissions.
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 invite access: Check Vault’s server permissions in Discord and read Policy & permissions for attribution limits.
- Inspect joins: Open Joins & invite leaderboard and switch between member joins and attributed invite credit.
Check it works
Check a controlled join through a known invite. Discord cannot reliably identify every join; do not reset a member’s credit to test setup.
How it works
Invite tracking compares Discord invite observations to attribute joins when possible. It is not guaranteed to identify an inviter for every member.
Vanity links, removed invites, bot downtime and unavailable invite data can produce unknown attribution. An unknown value is not evidence that someone has never invited a member.
The dashboard includes recorded joins, departures and the attributed inviter leaderboard. Resetting one inviter clears their stored invite credit in this server while preserving join history and Discord invite links.
Review attributed joins
An unknown inviter stays unknown and is excluded from attributed rankings. A confirmed reset clears one member’s invite credit in this server while preserving recorded joins and departures and all Discord invite links.
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.