Greetings
Key features
First welcome flow
Send a configured welcome message when a non-bot member joins, and optionally assign a first role immediately or after a delay.
Second welcome flow
Send a follow-up message when a configured trigger role is newly added, and optionally remove another role as part of that handoff.
Message templates and media
Welcome messages use the shared message builder, supported member tokens, and synced message images.
Delayed role assignment
Delayed first-role work re-checks the current settings before assigning a role.
Best for
Welcoming new members with rules, role selection, introductions, or next steps.
Post-application or post-verification handoffs triggered by a role.
Assigning starter roles after a delay without staff intervention.
How it works
Admins configure both flows
Staff choose the first welcome message/channel/role behaviour and the second welcome trigger role, message, and optional role removal.
A member joins
Nox skips bots, reads the saved greeting settings, sends the first welcome when enabled, and assigns or schedules the configured first role.
A trigger role is added
On role update, Nox checks for the newly-added trigger role. If it matches, Nox sends the second welcome and removes the configured follow-up role when enabled.
Failures are shown in Errors
Channel send, role add, role remove, and delayed role failures record greeting errors so staff can repair channel or role permissions.
Setup checklist
Choose welcome channels where Nox can view, send, and embed messages.
Add message content before enabling either welcome flow.
Select valid roles for first role assignment, trigger role, and role removal when those branches are enabled.
Grant Manage Roles and place Nox above any role it should add or remove.
Use a first-role delay from 0 to 604800 seconds when delayed assignment is enabled.
Important notes
Greetings has no slash commands, buttons, select menus, modals, public API routes, or backfill for members who joined while the feature was disabled.
The second welcome fires only when the configured trigger role is newly present in a role update.
Delayed role work re-checks the latest settings before changing roles, so old pending role assignments can safely do nothing after settings change.
Welcome messages are not tracked after delivery. Deleting them in Discord does not change the greeting configuration.
Missing members or roles during delayed assignment can exit quietly, while other Discord failures are recorded on the Errors page.
Troubleshooting
The welcome message did not send
Confirm the relevant flow is enabled, has a channel and message content, and that Nox can send in the channel.
A role was not assigned or removed
Check Manage Roles permission, role hierarchy, and whether the role still matches the current greeting config.
The second welcome did not trigger
Confirm the trigger role was newly added in that update. Existing roles from before the update do not trigger the second welcome.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
