New-account join gate
The only automod category that fires on member join, not on message. Refuses to admit accounts younger than a configured age.
When you'd use it
- Block raid waves coming from fresh throwaway accounts
- High-security communities that require members to have at least a few days of Discord history
- Drive raid attempts toward Verification instead of letting them straight into the server
Settings
| Setting | What it does |
|---|---|
| Minimum account age (days) | Reject accounts younger than this. Common values: 1 (just-yesterday), 7 (a week), 30 (a month). |
Actions
The action chain applies to the join event:
kick— kicks the joining member (they can re-join from a new server invite when their account ages enough)ban— permanent ban (use carefully — they can't appeal once banned)log_only— write a hit + alert staff without auto-acting
warn / timeout / delete don't apply (no message yet) and are silently skipped.
Tips
min_age_days = 1is the lightest-touch setting: a one-day-old account is the typical raid-account profile. Real new users tend to join Discord and bounce around for a day before stumbling into your server.- Combine with Verification instead of banning outright. Set the gate to log_only and let a captcha do the actual filtering.
- Mass-raid mitigation: use this with Anti-Raid and Verification together. Anti-raid catches the wave; new-account-gate slows the trickle; Verification gates the few that make it.
Behaviour
- Calculated from Discord's account-creation timestamp (Discord exposes this — it's in the snowflake).
- A member who joins, leaves, and re-joins is checked again. If they crossed the age threshold between joins, they pass on the second.
- Exempt roles cannot apply here — they don't have roles yet (they're joining).
Related pages
- Automod overview
- Security → Anti-Raid — for "many joins in a short window"
- Security → Verification — for gating new joins with a challenge
- Security → Firewall — for richer join-time rules (avatar required, bot-account blocking, etc.)