In what order does OriusBot process a new member (anti-raid, captcha, roles, welcome)?
When someone joins, OriusBot applies its checks in a precise order. Understanding it explains why a member does or doesn’t get a role, a welcome message or a kick.
- Return through member backup A person brought back by member backup isn’t treated as a new join: no anti-raid, no captcha, no auto-role, no welcome message.
- Return of a wrongly kicked member With their personal invitation, they get their roles back with no anti-raid or captcha (see this article).
- OriusBot blacklist An account the OriusBot team has identified as a raider is kicked before anything else, unless it is on your server’s whitelist.
- Anti-raid Minimum account age, crowd analysis, lockdown (for people, not bots).
- Honeypot “caught elsewhere” alert If the account was caught in a trap on another server of the network, you are informed in the log, with no sanction.
- Captcha The “Unverified” role is given until the challenge is passed.
- Automatic roles Given right away, unless the captcha is enabled: they then wait for it to be passed.
- Welcome Sent after the captcha is passed if the wait option is ticked, otherwise right away.
Practical consequence
A member who fails the captcha receives neither an automatic role nor a welcome: this is intended, so the welcome channel isn’t flooded with joins that fail.
Still stuck?
Contact support with the title of this article, the step where you are stuck and what you see on screen.
Contact support More articles: ProtectionLast checked: 13 November 2026.