Prerequisites
The bot role must be above every role it manages. Configure channels and role targets before enabling member-facing panels.
Email verification gate
Servers with enabled Verified Access can configure Email Verification from **Members & Roles > Verification** when the rollout is enabled for that server. Members prove control of an eligible email in private Discord modals and receive the configured access role only after the six-digit code succeeds.
- **Build a gate** creates a Verified role and protects the selected public resources while preserving private and staff-only areas.
- **Use an existing gate** controls membership of one selected role without changing that role's permissions or claiming that unrelated roles cannot provide equivalent access.
- Join invitations use DMs when enabled, while the fallback verification channel remains available when DMs are closed.
- Reminder campaigns show a recipient preview and require confirmation. Discord can report a DM as sent, but not read or delivered.
The server owner or a Discord Administrator must apply, repair, or restore a server-wide gate. Create new channels inside a protected, permission-synced category; standalone channels can be visible briefly before Discord delivers the creation event to Abhi.
Email addresses are encrypted and shown to staff only in masked form. Account limits apply per server, and revoking verification does not release an email slot. A personal-data deletion erases the member's verification records and can remove roles controlled by Email Verification, so the member may need to verify again.
When available on your deployment, [External API eligibility](/docs/features/verification-api) connects your existing directory instead of importing addresses. Save and test a draft before switching sources; existing verification and Discord permissions stay unchanged.
Safer bulk work
- Define the target population.
- Preview additions, removals, and hierarchy conflicts.
- Apply the bounded operation.
- Review partial failures before retrying.
Dedicated Role Automations
Supported triggers are one-time and recurring schedules, member join, screening completion, server boost, and role gained or lost. Rejoin, invite code, first message, activity window and inactivity window are unavailable in the dedicated Role Automations engine. Saved unsupported rules remain readable and can be paused or archived.
Supported member scopes are one member, all members, people, bots, members in a role, and matching role filters. Activity-based scopes and nonzero cooldowns are unavailable. The separate onboarding engine supports a different set of signals; its supported welcome and onboarding controls remain available.