New members get their roles. No clicks. No waiting.
Configure up to 50 default roles for humans, 50 for bots. Optional: delay (0–3600s) against raiders who leave quickly, sticky snapshots that restore roles on rejoin (up to 90 days), verify gate integration that waits for Discord screening.
What Auto-Roles can do
Up to 50 default roles for humans, 50 for bots — Discord's `user.bot` flag decides automatically. Give bots technical roles (e.g. a "Bots" collector), humans community roles (e.g. "Member", "Unverified").
6 options: instant, 30s, 2 min, 5 min, 15 min, 1 h. Classic raiders join and leave in seconds — if your auto-roles are only assigned after 2 minutes, raider role events never fire at all.
When a user leaves and rejoins, they get their old roles back (minus excluded ones, e.g. the mute role). No more flood of tickets after an accidental leave.
Specify which roles should NOT be restored — mute role, warn role, booster role (resets naturally). Configured in the dashboard, selectively overrides sticky snapshots.
Toggle: wait to assign roles until the member completes Discord server screening. No exploit where raiders grab permissioned roles before verification.
The dashboard proactively warns you if the bot has lost the "Manage Roles" permission or if a configured role is above the bot role (Discord hierarchy error). Includes a fix hint.
In detail
Sticky snapshots in detail
On leave, we store a snapshot of all the user's roles. On rejoin within 90 days, those roles are reassigned — minus anything in your exclusion list. After 90 days the snapshot is automatically deleted.
Redis-backed delay queue
Delayed assignments are parked in a Redis queue and polled every 10 seconds. Crash-safe — even if the bot restarts, pending assignments are not lost.
One delay config for all roles
The delay applies to all human roles equally (with a separate one for bots). No per-role delay — this is intentionally kept simple because 99% of use cases share the same anti-raider logic.
Frequently asked questions about Auto-Roles
What happens with manually removed roles?
If a mod removes a role and the user later leaves and rejoins, the role is NOT restored (because it was no longer present at leave time — the snapshot reflects the current state on leave). This is intentional.
Do sticky roles work across multiple servers?
No — snapshots are per-server. If user X has the "VIP" role on server A and then joins server B with TeraOne, they do not get VIP there. Cross-guild would be a privacy issue.
Can I turn auto-roles off entirely?
Yes — master toggle in the dashboard. Or simply clear both role lists (humans + bots). Delayed assignments already in the queue will still be processed.
More modules
Ready for TeraOne?
Two clicks to set up. No onboarding, no credit card.