Account age filter

The Account Age Filter gates joining members by how old their Discord account is. Raid accounts and ban-evasion alts are almost always brand new, so a minimum-age rule turns that shared trait into a simple, effective defense — while established members and bots pass straight through.

Beta — tested, but still young.

Set it up

1. Enable the Account Age Filter plugin in the Plugin Market.
2. On the Account Age page, set the minimum age (in days) and choose the action for accounts under it.

Setting	Range	Default
Minimum account age (days)	1–3650	7
Timeout (minutes)	1–40320 (28 days)	1440 (24 hours)

The filter only checks new joins. Members already on the server are never re-checked.

Action for young accounts

Pick one action:

• Give review role — assign a review role and hold them for manual approval (a good everyday default; nobody is auto-punished). The role only restricts what you restrict — see below.
• Timeout — let them in but muted for a cooling-off window.
• Kick — turn them away; they can rejoin once the account ages past the line.
• Ban — hardest stance, for servers under active attack.

Auto-setup

The Auto-setup button (shown when the action is Give review role) does the wiring for you. It creates an Account Review role and a 🚨・account-review channel that only CloudMod and your admin role can see, points the plugin at both, and switches the plugin on. Flagged members then show up there with Approve / Kick / Ban / Note buttons, so a human decides instead of the bot.

• Only members with Manage Server can use the review buttons.
• Approve removes the review role and then does what the join held back: auto roles, role sync and the welcome message (without the member-count milestone; {count} shows the member count at the time you approve). Kick and Ban act at once.
• Note saves a note to the member's case log. Kick and Ban add one too, so the case log shows what was decided.
• Pick the review channel yourself in the form (any text channel on your main server), or leave it empty: without one, reviews go to your moderation log channel instead.
• If a review post can't be delivered — no review channel and no moderation log channel, or CloudMod can't write there — your log says 🕓 Review post not delivered and why. The member keeps the review role; remove it by hand once you have decided.
• Auto-setup needs Manage Roles and Manage Channels on the main server.

Faster and less error-prone than building the role and the channel by hand — and it is the reason the review-role action is a sensible default.

The review role restricts nothing on its own. Discord roles only add permissions, so a member with the Account Review role still sees every channel your server opens to everyone. Restrict it yourself: deny the role View Channel (or Send Messages) on your categories, or give normal access only through a verified/member role that reviewed members get after Approve. CloudMod deliberately never rewrites your channel permissions.

What waits until you approve

While a member holds the review role, CloudMod holds back everything that could hand out access:

• Auto Roles are not given on join.
• Role Sync and Role Rules skip the member on every server: nothing is added, nothing is removed. A rule that reads the review role (if a user has Account Review → add Member) never fires for a member in review.
• The welcome message is skipped for that join.

The unverified role of the Verification Gate is the one exception. It only takes access away, so it is given right away.

So the review step can't hand out a member's normal role through an Auto Role or a rule. Press Approve instead: it removes the review role and then catches up the Auto Roles and the sync. The welcome message is not caught up, so an approved member is never greeted for that join. Take the role off by hand and the Auto Roles are never given, because they only run on join and on Approve. Sync catches up later on its own schedule.

Tell the member why

DM the user sends a short notice before the action runs, with your own DM message. It is on by default, also for a setup that was created by Auto-setup and never saved. Variables: {user_mention}, {user_name}, {guild_name}.

Without your own text, the member gets a default that fits the action: "too new to join" for Kick and Ban, "you've been muted for a while" for Timeout, and "you're in, but a moderator will review your account first" for the review role. The field shows the one that applies.

Worth turning on for the kick and review-role actions: someone who is turned away with no explanation assumes the server is broken, tries again, and ends up in your modmail. A DM that says "your account is too new, come back in a few days" costs nothing and prevents that. A DM cannot be delivered if the member has DMs from server members closed — the action still runs.

Main server or the whole network

Also apply on sub-servers is off by default: only the main server is gated. Turn it on to gate joins on the linked sub-servers too.

Leave it off if your sub-servers are meant to be easier to enter than the main one — a common setup where the main server is the gate and the rest is behind it anyway.

A ban on the main server is a network ban. With Network bans switched on in your project settings, a ban from this filter on the main server is enforced on every sub-server too. A false positive then costs the member the whole network — if that worries you, use the review role or Kick on the main server. A ban on a sub-server stays on that server.

Review role on sub-servers

A role only exists on one server, so Give review role needs a role of its own on every sub-server you want to gate. With Also apply on sub-servers on and the action set to Give review role, the form lists your sub-servers. Pick a review role and a review channel on each one:

• A flagged member on a sub-server gets that server's review role, and the review post with Approve / Kick / Ban / Note appears in that server's channel. People with Manage Server there decide — the main server never decides for a sub-server.
• At least one sub-server needs both a role and a channel before the form saves. A sub-server you leave empty is not checked: the form says so, and the log channel notes it when a too-young account joins there.
• Auto-setup only builds the role and channel on the main server. Create them on the sub-servers by hand (or reuse an existing role), then pick them in the list. The bot needs Manage Roles there, with its role above the review role.
• While a member holds the review role of their server, role sync leaves them alone on every server until you approve.
• A review role on a sub-server restricts nothing on its own either — restrict it there by hand, as described above.

Prefer not to set this up per server? Timeout, Kick and Ban work on all servers without any extra roles.

Who is never affected

• Bots are always exempt, so integrations you invite are never blocked.
• Admins and whitelisted users of your project are never affected.
• Accounts older than your threshold pass through and never notice the filter.

What gets logged

Every gated join shows up in your log as 🕓 Account too new. If CloudMod can't carry out the action (a missing permission, or the member's role sits above CloudMod's), the entry says 🕓 Account too new — action failed and the member joins normally, including auto-role and welcome message.

Setup notes

• Start modest (3–7 days) with the review role action, then tighten only if abuse slips through. Raise the threshold during an active raid, ease it back afterwards.
• Auto Roles have their own minimum account age (on the Auto Role page). A member you approve here can still be held back from auto roles by that setting — keep the two in line, or use only one of them.
• Nothing is active until the page has been saved once: a plugin you only switched on shows the default values, and the page says so.
• Requirement, depending on the action: Moderate Members (timeout), Kick Members, Ban Members, or Manage Roles (review role). Make sure the bot's role sits above the members it should act on.