NebulaClawNebulaClaw

New-member Verification

Require new Telegram or Discord members to pass a challenge before they can participate

New-member verification helps stop bots, raids, and throwaway spam accounts before they can post in your community.

When verification is enabled for a group or server, NebulaClaw challenges each new joiner. Passing the challenge unlocks normal access. Failing or timing out applies the action you configure for that group.

Where to Configure It

Open the console and go to:

Agent โ†’ Group Steward โ†’ Verification

The page shows one row for each connected Telegram group and one row for each connected Discord server. Each row has its own verification settings.

For Discord, verification is server-scoped. Configure it on the Discord server row, not on individual channel overrides.

Prerequisites

Telegram

  • The Bot is added to the target Telegram group.
  • The Bot is promoted to admin.
  • The group is registered under Agent โ†’ Platforms โ†’ Telegram or Moderation โ†’ Telegram Groups.

Discord

  • Discord is connected under Agent โ†’ Platforms โ†’ Discord.
  • The Bot has been invited to the target server.
  • The server is registered in the Discord Servers list.
  • For role-based verification, the Bot role must be above the roles it assigns or removes.

Configure Verification

Choose the group or server

In Group Steward โ†’ Verification, find the Telegram group or Discord server and click Configure.

Enable verification

Turn on Enable verification for that target.

Choose a challenge mode

Pick the mode that matches your risk level:

ModeBest for
Single buttonLowest-friction communities. New members tap one button to confirm they are human.
Digit imageHigher spam risk. The Bot shows a noisy numeric image and answer buttons.
Math problemSimple challenge with answer buttons.
Multiple choiceGeneral anti-bot prompt with four answer buttons.
Alphanumeric typed captchaDiscord only. The user types the code from an image in a Discord modal.

Set timeout and failure action

Choose how long a new member has to pass:

  • 60 seconds for strict groups
  • 5 minutes for most communities
  • 10 minutes for slower onboarding flows

Then choose what happens if they fail:

  • Keep muted: user stays in the group but cannot speak until an admin intervenes.
  • Kick out: user is removed and can rejoin later to try again.

Customize messages

Choose the prompt language: bilingual, Chinese, or English.

You can customize the welcome text. Use placeholders like {handle} and {minutes} to personalize the message.

Add Discord role and panel settings

For Discord, also configure:

  • Verification channel: where the public verification panel is posted.
  • Unverified role: assigned when a member joins.
  • Verified role: assigned after the challenge is passed.
  • Panel title, description, color, and banner image: controls the Discord embed shown to new members.

The role picker can create new roles for you. You can also paste role or channel IDs manually.

Save

Click Save. Discord saves also refresh the verification panel in the selected channel.

Telegram Behavior

For Telegram groups, the Bot posts the challenge in the group. If the group uses topics, you can configure a topic for the prompt.

The Bot needs admin permissions to mute, unmute, and kick users. If it cannot perform an action, check the Bot's Telegram admin permissions.

Discord Behavior

For Discord servers, the recommended setup is:

  1. Create or select an Unverified role.
  2. Restrict normal channels so the Unverified role cannot read or send messages there.
  3. Create or select a Verified role.
  4. Allow verified members to access the normal server channels.
  5. Select a verification channel that new members can see.
  6. Save the verification panel.

When a user joins, NebulaClaw assigns the Unverified role. After the user passes verification, NebulaClaw grants the Verified role and removes the pending verification state.

Discord role order matters. If the NebulaClaw Bot role is below the Unverified or Verified role, Discord will reject the role change.

Troubleshooting

On this page