One-Click
A single button press in the verification channel. Fast, low-friction, good for smaller or community-trusted servers.
Verification and Quarantine work together: verification keeps automated accounts and alts out before they can act, and quarantine contains anyone who slips through or turns out to be dangerous after joining.
A single button press in the verification channel. Fast, low-friction, good for smaller or community-trusted servers.
A CAPTCHA rendered and answered entirely inside Discord, with adjustable difficulty, colors, and length.
An hCaptcha-compatible flow hosted off-Discord, with the extra alt-account protection below.
The web verification flow stores a hashed IP alongside each verification record. When Block Alt Accounts is enabled, a new user whose hashed IP matches an already-verified Discord account on a different ID is treated as a likely alt. This check only runs on the web CAPTCHA path, since the bot itself has no way to see a member's IP through Discord alone.
A background monitor periodically checks whether the Unverified role, Verified role, and verification channel still exist and are correctly positioned. If something's missing or broken, it recreates roles, restores settings, and repositions everything automatically, then notifies the owner.
The Unverified role's channel restrictions, and every quarantined member's channel overwrites, are continuously sanitized. If a channel is created or its permissions are edited, Ember checks whether the restrictions were removed and restores them.
Quarantine does more than add a role. Running &quarantine snapshots the member's current roles, removes them (preserving managed and integration roles it can't touch), and applies the quarantine role. If a role can't be removed due to hierarchy, Ember escalates to a ban rather than reporting a false success; if quarantine itself can't be applied, it falls back to a kick, then a timeout.
If a quarantined member leaves and rejoins, their quarantine state is recovered and reapplied. The normal autorole and verification flow is not allowed to bypass it, so "leave and rejoin" isn't an escape route.
Unverified sits directly above the highest autorole anchor, Verified sits directly above Unverified, and both stay beneath Ember's own hierarchy. Roles are re-fetched between moves so Discord's position shifting can't create gaps.
| Command | Syntax | Description | Permissions | Example |
|---|---|---|---|---|
| &verification | &verification [setup|type|disable|view|fix|verify] | Configures the verification system. Supports One-Click, Web Captcha, or In-Discord Captcha modes, IP alt-account blocking, and manual verification. | Administrator | &verification setup |
| &manualverify | &manualverify <@user|userID> | Manually verifies a user or alt account and logs the action to the verification log channel. Aliases: mverify, mverif, adminverify, forceverify. | Administrator | &manualverify @User |
| &quarantinesetup | &quarantinesetup or /quarantinesetup | Creates the Quarantine role, positions it correctly relative to the Ember Anti-Bypass role, and syncs channel deny overrides across every channel. | Administrator (in Settings Whitelist) or Owner | &quarantinesetup |
| &quarantine | &quarantine <@user> [reason] or /quarantine | Isolates a user immediately: saves their current roles, removes them, and applies the Quarantine role. Falls back to a ban if a role can't be removed. | Administrator (in Settings Whitelist) or Owner | &quarantine @Spammer Raid participant |
| &unquarantine | &unquarantine <@user> [reason] or /unquarantine | Removes the Quarantine role and restores the member's previously saved roles. | Administrator (in Settings Whitelist) or Owner | &unquarantine @Spammer Appeal accepted |
| &autorole | &autorole [bot] [<@role|roleID>] | Configures automatic role assignment for incoming users and bots, calculated with role hierarchy in mind. | Administrator | &autorole @Member |