Autorole Commands

Automatically assign roles to new members when they join your server.

Overview

The autorole system automatically gives specified roles to members when they join your server. This is useful for:

  • Giving default member roles
  • Auto-verification setup
  • Basic access level assignment
  • Community onboarding

Use Case

Popular use: Auto-assign a "Member" role so new users can access most channels while maintaining a verification channel for full access.

autorole add

Adds a role to the autorole list.

Usage:

/autorole add [role]

Example:

/autorole add @Member

Requirements:

  • Role must exist on your server
  • Bot must have permission to assign the role
  • Bot role must be higher than the target role in hierarchy

Permissions Required: Manage Roles

Notes:

  • Multiple roles can be added, all will be assigned to new members
  • You can add up to your Discord limit of roles

autorole remove

Removes a role from the autorole list.

Usage:

/autorole remove [role]

Example:

/autorole remove @Member

Effect:

  • The role will no longer be assigned to new members
  • Existing members keep the role, it doesn't get removed retroactively

Permissions Required: Manage Roles

Note

This only prevents future assignments. Members who already have the role will keep it.

allautoroles

Lists all roles currently in the autorole system.

Usage:

/allautoroles

Output:

  • Shows all roles assigned on join
  • Public command, anyone can view

Permissions Required: None

Why Public?

Members can already see each other's roles, so this list is informational only.

Autorole Setup Example

Here's a complete setup example:

# Add member role
/autorole add @Member

# Add verified role (if using verification system)
/autorole add @Verified

# View the list
/allautoroles

Best Practices

  1. Minimal Default Roles

    • Only auto-assign roles essential for basic access
    • Keep it simple: typically just "Member" or similar

  2. Use with Verification

    • Auto-assign basic access
    • Require verification for full member role

  3. Hierarchy Awareness

    • Ensure bot role is higher than autorole target
    • Use lower roles for autoroles to avoid permission issues

  4. Clear Role Purpose

    • Make it obvious in role names what autorole is for
    • Example: @AutoRole-Member instead of vague names

  5. Monitor Role Assignment

    • Check logs occasionally to ensure roles are being assigned
    • Verify new members receive expected roles

Captcha Verification Integration

If Membership Captcha Screening is enabled in your anti-raid settings, Raptor will not assign your autoroles immediately on join. Instead, the roles are held back until the user successfully completes their captcha verification.

To create a secure and automated onboarding flow, we recommend the following setup:

  1. Restrict @everyone:

    • In your server settings, deny the @everyone role permission to view all channels except for your designated Verification Channel.
    • In the Verification Channel, allow @everyone to view the channel and read history.

  2. Configure Autorole:

    • Create a role (e.g., @Member or @Verified).
    • Add this role to your autoroles using /autorole add @Member.

  3. Configure Captcha Screening:

    • Configure the verification channel using /antiraid captcha enabled:On channel:#verification.
    • Post the verification prompt message using /antiraid send_captcha.

  4. Grant Access to the Autorole:

    • In all your standard text and voice channels, grant the @Member role permission to view the channels.
    • Crucial: In your Verification Channel, explicitly deny the @Member role permission to view the channel.

How it works:

  • A new member joins the server. Because Captcha Screening is enabled, the bot does not give them the @Member role. They can only see the Verification Channel.
  • The member clicks Verify Now, completes the Cloudflare Turnstile captcha on the web dashboard, and is successfully verified.
  • The bot assigns them the @Member role.
  • Because the @Member role is allowed in normal channels and denied in the Verification Channel, the member instantly gains access to the server, and the verification channel disappears from their sidebar!

Reaction-role setup and commands are documented separately in:

Troubleshooting

Roles not being assigned?

  • ✓ Verify bot has Manage Roles permission
  • ✓ Check bot role is higher than target role in hierarchy
  • ✓ Ensure role was added with /autorole add
  • ✓ Check bot didn't get rate-limited

Role list shows nothing?

  • Run /allautoroles to verify
  • If empty, add roles with /autorole add

Need to assign roles to existing members?

  • Unfortunately, autorole only works on join
  • You'll need to manually assign or use a third-party bot for bulk role assignment

Manual Assignment

If you need to assign existing roles to current members, use the Discord interface or a bulk role assignment command if available.