Welcome messages
Greet new members, assign a join role and say goodbye.
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 View Channel and Send Messages in the chosen channel. Join roles require Manage Roles and a role below Vault.
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.
- Choose your greeting: Open Join messages, choose a channel, turn on Welcome messages and write your greeting. The example updates as you type; it does not post to Discord.
- Add a member role: Open Join roles and select the role new members should receive. Leave the field empty if you do not want automatic assignment.
- Save each change: Choose Save changes in the editor. Leave messages and Direct messages are separate options; configure them only if you want those messages.
Check it works
Use a controlled member join to check the greeting and role. Direct messages can be blocked by the member’s privacy settings.
How it works
Welcome and goodbye messages are sent by their corresponding member events. Bots are skipped. The welcome flow also respects the existing fresh-account policy.
Example: Welcome {user} to **{server}**! You are member #{member_count}. The preview uses example names and counts, not real member data.
Direct messages may not arrive if a member blocks them. A welcome message in a channel and a direct message are separate settings.
Turning off message delivery does not necessarily turn off an independently configured join role. Clear the role selection if you want to stop automatic role assignment.
| Setting or command | What it means |
|---|---|
| Welcome messages | Enable or pause the public greeting. |
| Welcome channel | Destination for new-member greetings. An unset channel may use the existing server default. |
| Welcome message | Up to 2,000 characters; supports the message variables reference. |
| Join role | Optional assignable role for new members. |
| Direct message greeting | Optional private greeting; delivery depends on member privacy settings. |
| Goodbye messages | Enable only after choosing a valid goodbye channel. |
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.