Skip to main content

Why Are Cancelled Members in Discord Not Getting Kicked?

TL;DR: If cancelled members stay in your Discord, the LaunchPass bot likely lacks proper permissions. The LaunchPass role must be at the top of your role list and have Administrator permissions enabled.

Seth avatar
Written by Seth
Updated over a week ago

Quick Answer

Most common cause: Role hierarchy is wrong.

The LaunchPass bot role must be:

  • At the very top of your role list

  • Above all other roles (including admin roles)

  • Set as Administrator in permissions

If the role is not #1, the bot cannot kick members.

Why This Happens

How Discord Role Hierarchy Works

Discord uses a top-down hierarchy for roles.

The rule:

  • Higher roles can manage lower roles

  • Lower roles cannot manage higher roles

  • If bot role is below member role, bot cannot remove them

Example of broken hierarchy:

  1. Server Owner

  2. Admin

  3. Moderator ← Member has this role

  4. LaunchPass Bot ← Bot is here

  5. Premium Member

  6. @everyone

Bot cannot kick the member because Moderator role is above bot role.

Correct hierarchy:

  1. LaunchPass Bot ← Must be here

  2. Server Owner

  3. Admin

  4. Moderator

  5. Premium Member

  6. @everyone

Now bot can kick anyone because it's at the top.

How to Fix It

Step 1: Enable Administrator Permission

In your Discord server:

  1. Click server name dropdown

  2. Select "Server Settings"

  3. Click "Roles" in the left menu

  4. Find "LaunchPass" role

  5. Click on it

  6. Scroll down to "Permissions"

  7. Scroll all the way to bottom

  8. Toggle "Administrator" to ON (green)

  9. Click "Save Changes"

Why Administrator permission:

  • Gives bot full control

  • Can manage all members

  • Can assign/remove roles

  • Can kick members

  • Simplest solution

Step 2: Move LaunchPass Role to Top

Still in Server Settings → Roles:

  1. Look at your role list

  2. Find "LaunchPass" role

  3. Click and drag it to the very top

  4. It should be position #1

  5. Above ALL other roles

  6. Save changes

Visual check:

  • LaunchPass should be first role in list

  • Above your admin roles

  • Above your moderator roles

  • Above your paid member roles

  • Above everything except server owner

Step 3: Refresh LaunchPass Dashboard

After fixing Discord settings:

  1. Go to your LaunchPass dashboard

  2. Refresh the page in your browser

  3. This ensures LaunchPass sees the changes

  4. Connection updates

Step 4: Test It Works

Verify the fix:

Option 1: Cancel a test subscription

  • Create test subscription

  • Cancel it immediately

  • Member should be kicked from Discord

  • Happens within a few minutes

Option 2: Check existing cancelled members

  • If they're still there, manually remove them

  • Bot only auto-kicks new cancellations going forward

  • Old members who joined during broken setup stay

Common Issues and Solutions

Issue 1: LaunchPass Role Not at Top

Problem: Bot role is below other roles.

Fix:

  1. Server Settings → Roles

  2. Drag LaunchPass to position #1

  3. Must be above all other roles

  4. Save changes

Why it matters: Bot can only manage roles below it in the hierarchy.

Issue 2: Administrator Permission Not Enabled

Problem: Bot doesn't have Administrator permission.

Fix:

  1. Server Settings → Roles → LaunchPass

  2. Scroll to bottom of permissions

  3. Toggle Administrator ON

  4. Save changes

Why it matters: Without Administrator, bot may lack specific permissions needed to kick members.

Issue 3: Free Members Joined During Broken Setup

Problem: Members who joined while role hierarchy was wrong don't get auto-removed.

Fix:

  • Manually remove these members using Discord

  • Bot will only auto-kick new cancellations going forward

  • Past issues don't auto-resolve

How to manually remove:

  1. Right-click member name

  2. Select "Kick [username]"

  3. Confirm kick

Issue 4: Wrong Role Selected in LaunchPass Settings

Problem: The "Role to assign" setting in LaunchPass points to wrong role.

Fix:

  1. Log into LaunchPass dashboard

  2. Go to your invite page settings

  3. Check "Role to assign" dropdown

  4. Make sure correct role is selected

  5. Save if changed

Why it matters: If wrong role is selected, bot may not know which role to remove when members cancel.

Issue 5: Role Was Deleted or Renamed

Problem: The role LaunchPass was using got deleted or renamed in Discord.

Fix:

  1. Identify which role was linked to your LaunchPass page

  2. In LaunchPass dashboard, delete the affected invite page

  3. Recreate the page with new/correct role

  4. Don't worry - active subscriptions are not affected

Why this works: Recreating the page refreshes all role associations.

Checking Your Current Setup

Quick Diagnostic

Answer these questions:

1. Is LaunchPass role at the very top?

  • Check: Server Settings → Roles

  • Look: Is it position #1?

  • If no: Move it to top

2. Does LaunchPass role have Administrator?

  • Check: Click LaunchPass role → Permissions

  • Scroll: To bottom of list

  • Look: Is Administrator toggled ON?

  • If no: Enable it

3. Are cancelled members actually cancelled?

  • Check: Your Stripe dashboard

  • Verify: Subscription status is "Canceled"

  • Sometimes: They may still have access until period ends

4. How long ago did they cancel?

  • Auto-kick: May take a few minutes

  • Grace period: Check your settings

  • Immediate: Or end of billing cycle

If all settings are correct and members still aren't kicked, contact [email protected].

Understanding Auto-Kick Behavior

When Members Get Kicked

By default, members are kicked when:

  • Subscription cancels

  • Payment fails after all retries

  • Refund is issued

  • Trial expires without payment

Timing:

  • Usually within a few minutes of cancellation

  • May be delayed if Discord is slow

  • Check #launchpass channel for notifications

When Members Keep Access

Members may keep access if:

  • They cancelled but billing period hasn't ended yet (access until period end)

  • You have grace period enabled (they get extra time)

  • dontKickOnCancel is enabled (removes role but doesn't kick)

  • Bot doesn't have proper permissions (the problem this article fixes)

Alternative: Remove Role Instead of Kicking

If you don't want to kick members:

Use the dontKickOnCancel command in your #launchpass channel.

What this does:

  • Members stay in your Discord

  • But their paid role is removed

  • They lose access to premium channels

  • They can still see public/free channels

To enable:

  1. Go to your #launchpass channel

  2. Type: dontKickOnCancel

  3. Bot responds: dontKickOnCancel: true

To disable (go back to kicking):

  1. Type the command again: dontKickOnCancel

  2. Bot responds: dontKickOnCancel: false

Preventing Future Issues

Best Practices

✅ Keep LaunchPass role at top always

  • Check it monthly

  • After adding new admin roles

  • After any role changes

  • Make it a habit

✅ Don't create roles above LaunchPass

  • When adding new staff roles

  • Place them below LaunchPass

  • Maintain hierarchy

✅ Test after changes

  • Any time you adjust roles

  • Create test subscription and cancel it

  • Verify auto-kick works

  • Catch problems early

✅ Monitor #launchpass channel

  • Check for notifications

  • Watch for errors

  • Bot will report issues

  • Stay informed

✅ Train your team

  • Admins should know about hierarchy

  • Don't move LaunchPass role down

  • Don't disable Administrator permission

  • Document the setup

What If It's Still Not Working?

Additional Troubleshooting

Try these steps:

1. Disconnect and reconnect Discord

  • In LaunchPass dashboard

  • Disconnect your Discord server

  • Reconnect it

  • Reauthorize permissions

  • Test again

2. Check for Discord outages

  • Visit Discord status page

  • Sometimes Discord has issues

  • May cause delays

  • Wait and retry

3. Verify bot is in your server

  • Look for LaunchPass bot in member list

  • If missing, reconnect Discord

  • Bot must be present to kick members

4. Check bot is online

  • LaunchPass bot should show as online (green)

  • If offline (gray), there's a connection issue

  • Contact support

5. Review your LaunchPass settings

  • Check auto-kick is enabled (not using dontKickOnCancel)

  • Verify grace period settings

  • Check all invite page configurations

When to Contact Support

Contact [email protected] if:

  • LaunchPass role is at top with Administrator permission

  • Bot is online and present in server

  • Members still aren't getting kicked after cancellation

  • You've tried all troubleshooting steps

  • Issue persists for more than 24 hours

Include in your message:

  • Your Discord server name

  • Screenshot of role hierarchy

  • Screenshot of LaunchPass role permissions

  • Example of member who should have been kicked but wasn't

  • Their Discord username and email

Response time: Usually within 24 hours on business days.

Quick Reference

Fix Checklist

  • ✅ LaunchPass role at very top of role list

  • ✅ LaunchPass role has Administrator permission enabled

  • ✅ Saved changes in Discord

  • ✅ Refreshed LaunchPass dashboard

  • ✅ Tested with new cancellation

  • ✅ Manually removed old members who joined during broken setup

Role Hierarchy Reminder

Correct order (top to bottom):

  1. LaunchPass Bot ← Must be #1

  2. Your admin/owner roles

  3. Moderator roles

  4. Paid member roles

  5. Other roles

  6. @everyone

Commands to Know

In #launchpass channel:

dontKickOnCancel Toggle between kicking and role removal only

Bot responds:

  • true = Don't kick, just remove role

  • false = Kick member from server (default)

Related Articles

Related Articles
How Discord Admins Get Member Email and Username Information
Can You Use Discord With LaunchPass?
When Using Discord, Do You Assign a Role?
Troubleshooting: Bot Commands Not Working in the #launchpass channel on Discord
How Do I Manage Roles for Users Not Present in My Discord Server?
Did this answer your question?