Skip to main content

Can You Remove Roles Instead of Kicking Members?

Yes. By default, canceled members are kicked from your Discord server. Use the dontKickOnCancel command in #launchpass to remove their member role instead (they stay in server but can't access member channels). Use kickOnCancel to switch back to kicking.

Patrick B avatar
Written by Patrick B
Updated this week

Understanding Member Removal on Cancellation

What Happens by Default

When a member's subscription ends:

  1. Payment fails or member cancels

  2. LaunchPass detects the cancellation

  3. Member is automatically kicked from Discord

  4. They get notification: "You were kicked from [server]"

  5. They're removed from member list

  6. They can no longer see any server content

This is the default behavior. Clean and clear.

Why Default is Kicking

Default kicking makes sense because:

  • ✅ Clear boundary between members and non-members

  • ✅ Server looks clean (no ex-members lingering)

  • ✅ Simple and straightforward

  • ✅ Professional appearance

  • ✅ Easier to manage

  • ✅ No confusion about who's active

It's the recommended approach for most communities.

Alternative: Remove Roles Instead

What Role Removal Does

Instead of kicking, you can remove their member role:

When subscription ends:

  1. Payment fails or member cancels

  2. LaunchPass detects the cancellation

  3. Member role is removed (not kicked)

  4. They stay in server (still visible in member list)

  5. They can't access member channels (role gone = no permissions)

  6. They see "no access" when trying to view channels

  7. They stay in member list but without member role

Result: Gentler approach. Less harsh than getting kicked, easier to reengage in the future.

When Role Removal Makes Sense

Consider this if you want:

  • ✅ Softer approach to member departure

  • ✅ Members to stay in community (without access)

  • ✅ Lower friction for rejoining later

  • ✅ Less confrontational (not saying "get out")

  • ✅ Option for members to lurk

  • ✅ Community still visible to them

Don't choose this if you prefer:

  • ❌ Clean server (no ex-members)

  • ❌ Clear boundaries

  • ❌ Professional appearance

  • ❌ Removing lapsed members

How to Enable Role Removal

Using the dontKickOnCancel Command

To switch from kicking to role removal:

Step 1: Open #launchpass channel

  1. Go to your Discord server

  2. Find the #launchpass channel

  3. Click on it (open the channel)

Step 2: Type the command

  1. In the message box, type exactly:

dontKickOnCancel

  1. Press Enter to send

Step 3: Verify it worked

  1. LaunchPass bot will reply

  2. The reply will say: true (or similar confirmation)

  3. You'll see confirmation like:

    • ✅ dontKickOnCancel enabled (true)

    • ✅ Setting enabled

    • ✅ Role removal mode active

Done! The command is now active.

What This Changes

Immediately after running the command:

  • ✅ Next cancellation: Role removed instead of kicked

  • ✅ New canceled members: Stay in server

  • ✅ Old behavior gone: No more kicking

  • ✅ Stays on: Until you change it back

Everyone going forward uses the new behavior.

Real Example

Before (default kicking):

Member: JohnDoe123 Status: Active member Subscription: Active Action: Subscribed → Payment fails → Kicked from server Result: JohnDoe123 gone from member list, no longer sees server

After (role removal):

Member: JohnDoe123 Status: Former member Subscription: Canceled Action: Subscribed → Payment fails → Role removed Result: JohnDoe123 still in server, can't access member channels

How to Switch Back to Kicking

If You Change Your Mind

To go back to kicking members:

Step 1: Open #launchpass channel

  1. Go to #launchpass

  2. Click on it

Step 2: Type the command

  1. In the message box, type exactly:

kickOnCancel

  1. Press Enter

Step 3: Verify it worked

  1. LaunchPass bot replies

  2. Confirmation message appears

  3. You'll see something like:

    • ✅ kickOnCancel enabled (true)

    • ✅ Kicking mode active

    • ✅ Back to default behavior

Done! Kicking is now active again.

What This Changes Back

After running kickOnCancel:

  • ✅ Next cancellation: Member kicked (default)

  • ✅ Members removed: From server completely

  • ✅ New behavior: Back to kicking

  • ✅ Previous setting: No longer active

Comparing Kick vs. Role Removal

Side-by-Side Comparison

Situation

Kick on Cancel

Don't Kick (Role Removal)

Member cancels

Kicked from server

Role removed, stays in server

Server member list

Ex-member gone

Ex-member still visible

Channel access

No access (kicked)

No access (role removed)

Can they see content?

No (removed)

No (role blocks access)

Can they rejoin?

Must re-signup

Can re-subscribe (easy)

Community feel

Professional, clean

Friendly, inclusive

Management

Simpler

Slight clutter (ex-members visible)

Harshness

Harsh (kicked)

Gentle (role removed)

Best for

Most communities

Retention-focused communities

Decision Matrix

Choose KICK if:

  • ✅ You want clean server appearance

  • ✅ You prefer clear boundaries

  • ✅ You want professional feel

  • ✅ You don't want to manage ex-members

  • ✅ You want simple, clear outcomes

Choose ROLE REMOVAL if:

  • ✅ You want gentler member experience

  • ✅ You want to keep people around

  • ✅ You're retention-focused

  • ✅ You want easier rejoin path

  • ✅ You want friendlier community feel

Recommendation: Most communities use KICK (default). It's cleaner and simpler.

How Members Experience Each Option

What Members See: Kick on Cancel

From member's perspective:

  1. Subscription active: Enjoying full access

  2. Subscription ends: Payment fails or they cancel

  3. Instant: They get kicked

  4. Notification: "You were kicked from [server]"

  5. Result: Can't access server anymore

  6. To rejoin: Must sign up again

Member feeling: "I've been removed. I need to re-signup to come back."

What Members See: Role Removal

From member's perspective:

  1. Subscription active: Enjoying full access

  2. Subscription ends: Payment fails or they cancel

  3. Instant: They lose member role

  4. Notification: "Your role was removed" or see restricted channels

  5. Result: Can see server but can't read member channels

  6. To rejoin: Can re-subscribe quickly

Member feeling: "I lost access but I'm still here. I can come back easily."

Best Practices

When to Use Each

Use KickOnCancel (default) for:

  • Most communities (recommended)

  • Professional/business communities

  • Communities wanting clean appearance

  • Communities wanting clear boundaries

  • Most use cases

Use dontKickOnCancel (role removal) for:

  • Community-first cultures

  • Membership-based groups

  • Retention-focused communities

  • Groups that want to stay connected

  • Communities emphasizing inclusion

Implementation Recommendations

Best practice: Start with default (kick), change only if needed.

Why: Kicking is simpler, cleaner, and what most communities need.

If you do change:

  • ✅ Make a conscious decision

  • ✅ Document your choice

  • ✅ Tell your team

  • ✅ Be consistent

  • ✅ Communicate to members (optional but good)

Member Communication

Optional: Tell members about your approach

If using KickOnCancel (default):

"When your membership ends, you'll be removed from the server. You can rejoin anytime by signing up again."

If using dontKickOnCancel:

"When your membership ends, you'll lose access to member-only channels but can stay in the community. You can resubscribe anytime to regain access."

Troubleshooting

"Command Didn't Work"

Why this happens:

  • Typed wrong channel name

  • Typo in command

  • Bot offline (rare)

  • Permissions issue

What to do:

  1. Verify you're in #launchpass

    • Right-click channel

    • Check name is exactly "launchpass"

    • No emojis or capital letters

  2. Check command spelling

    • Lowercase: dontKickOnCancel (not DontKickOnCancel)

    • Or: kickOnCancel (not KickOnCancel)

    • Exact spelling required

  3. Try again

    • Type slowly and carefully

    • Copy-paste if available

    • Press Enter to send

  4. If still doesn't work

"How Do I Know It's Active?"

Verify your setting:

  1. In #launchpass, type:

dontKickOnCancel

  1. Or type:

kickOnCancel

  1. Bot replies with the current status (should say true)

  2. Check reply message - confirms setting is active

If you're unsure which is on:

  • Try both commands separately

  • Each one will report its status

  • One will say "true" (active)

"Can I Check the Current Setting?"

To see which mode you're in:

Type either command and see what the bot replies.

If you type dontKickOnCancel and bot says true:

  • Role removal is ACTIVE (not kicking)

If you type kickOnCancel and bot says true:

  • Kicking is ACTIVE (role removal off)

Real-World Scenarios

Scenario 1: Community Manager Wants Gentler Experience

Situation: Manager wants members to feel valued even if they leave.

What they do:

  1. Type dontKickOnCancel in #launchpass

  2. Bot confirms it's active

  3. Next canceled member: Role removed (not kicked)

  4. Ex-member stays in server, can rejoin anytime

  5. Community feels more inclusive

Result: Better retention, friendlier community feel.

Scenario 2: Premium Community Wants Clean Appearance

Situation: Premium/exclusive community wants clear member status.

What they do:

  1. Keep default (kick on cancel)

  2. Or type kickOnCancel to confirm it's on

  3. When members cancel: They're kicked

  4. Server stays clean

  5. Clear distinction: Members vs. non-members

Result: Professional appearance, clear boundaries.

Scenario 3: Community Changes Minds

Situation: Started with role removal, now wants to switch to kicking.

What they do:

  1. Type kickOnCancel in #launchpass

  2. Bot confirms it's now active

  3. Next canceled member: Will be kicked

  4. Previous ex-members (with removed role) stay in server

  5. Going forward: Kicking mode on

Result: New behavior starts immediately, old members stay as is.

What Happens to Ex-Members

With Kick on Cancel

Ex-member status:

  • ❌ Not in server anymore

  • ❌ Not in member list

  • ❌ No access to anything

  • ✅ Can re-signup anytime

  • ✅ Starting fresh if they return

With Role Removal

Ex-member status:

  • ✅ Still in server

  • ✅ Still in member list

  • ❌ No member role

  • ❌ Can't read member channels

  • ✅ Can see public channels (if any)

  • ✅ Can re-subscribe easily

If You Switch Between Modes

What happens to existing ex-members:

If you switch FROM kick TO role removal:

  • Old kicked members: Still kicked (setting doesn't apply retroactively)

  • Only affects NEW cancellations going forward

If you switch FROM role removal TO kick:

  • Old ex-members with removed role: Still in server (setting doesn't retroactively kick them)

  • Only affects NEW cancellations going forward

Manual cleanup: You'd need to manually kick old ex-members if you want them gone.

Related Resources

Key Takeaways

✅ Default behavior: Members are kicked when subscription ends

✅ Alternative: Use dontKickOnCancel to remove role instead

✅ Role removal means: Member stays but loses access to channels

✅ Switch back: Use kickOnCancel to return to kicking

✅ Commands: Type in #launchpass channel only

✅ Verify: Bot confirms with "true" reply

✅ Immediate: Changes apply to next cancellation

✅ Most communities: Use default kick (recommended)

✅ Gentler communities: Use role removal

✅ Your choice: Pick what fits your community culture

Need Help?

Have questions about kick vs. role removal?

Email LaunchPass support: [email protected]

We can help with:

  • Understanding kick vs. role removal

  • Setting up either option

  • Changing between options

  • Troubleshooting commands

  • Member management questions

  • Community strategy advice

  • Any automation questions

Response time: Usually within 24 hours

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?
Why Are Cancelled Members in Discord Not Getting Kicked?
Can We Enable Community on Discord?
Did this answer your question?