A premium Discord server only works when access matches who is paying. The moment expired users keep their perks, the value drops, paying users notice, and moderators get dragged into manual moderation work instead of building the community.
You can prevent that with Suby. Suby links payment to roles, manages access automatically, and can auto kick Discord users who stop renewing. It removes human error, cleans up access, and protects trust.
This guide shows you how to use Suby to assign roles automatically, run an auto kick system, post renewal reminders, and handle members who fail to renew. You will also see how to configure kick command behavior, permission order, and moderation rules so your paid Discord bot setup feels premium and stays healthy.
We will cover everything you need to run a Discord bot setup that is predictable, transparent, and fair.
Why unpaid access quietly erodes your premium space
When expired members stay inside your premium Discord server, a few things start happening immediately:
- Scarcity fades. The group stops feeling exclusive if people who did not renew still talk in premium channels.
- Paying users ask tough questions. They notice when other users are getting the same premium content for free.
- Moderators end up doing support instead of moderating. They chase proof of payment screenshots, resolve renewal disputes, and burn hours on role cleanup.
This is not only a revenue leak. It slowly damages trust.
Your community needs a clear rule: you pay, you get access. When you stop paying, you stop having access. That rule needs to hold automatically, not only when someone on the team remembers to run a manual kick command.
Suby enforces that rule for you. Suby maps active subscriptions to Discord roles, removes expired roles after a grace period, and can automatically kick users who are no longer paying. It also sends renewal reminders to help users avoid losing access in the first place. This makes the system feel consistent instead of personal.
How Suby keeps access precise
Suby connects a product plan to a Discord role. If the plan is active, the bot assigns the premium role. If the plan expires and the grace period ends, Suby removes the role. If you enable auto kick, Suby can also automatically remove the account from the server when the renewal fails.
That means:
- No guessing
- No spreadsheets
- No manual kick command spam in mod chat
Suby moderation logic is based on roles, not vibes. The bot looks at the paid role you mapped, checks payment status, and updates that role automatically. This protects your staff, keeps moderation predictable, and avoids fights with users who claim they already paid.
Suby also supports notification messages that announce new subs, renewals, and cancellations. That creates visible proof that moderation and access rules are enforced consistently.
Now let’s walk through setup.
Step 1: Link Suby to Discord and create a paid role
The first step is to connect the Suby bot to your Discord server, create a premium role, and map that role to a live plan so that members who pay automatically get assigned.
1. Invite Suby and connect your server
- Add the Suby bot to your Discord server.
- Approve the requested permissions.
- Make sure Suby has the Manage Roles permission. Without Manage Roles, the bot cannot assign roles or remove roles.
If the bot does not have permission to assign roles, you will see a loading error or a permissions error during setup. Fix that before moving forward.
2. Create a paid role
Inside Discord, go to Server Settings → Roles and create a role such as Premium or Members Pro.
Keep it simple. This is the role paying users will receive automatically. Do not overload it with moderation powers. It should be for access, not for staff control.
3. Link the paid role to your plan
Inside your server, run /start to open the setup card. Click “Link role to plan.” Select the paid role and the plan from the dropdown, then confirm.
Suby automatically links them, no IDs or manual setup needed. Just make sure the Suby bot has Manage Roles permission and sits above the paid role in your server’s role list.
4. Put Suby above paid roles in role order
Discord only allows a bot to assign or remove roles that sit below the bot in the role hierarchy.
Your role order should look like this:
If the Premium role is above the Suby bot role in the list, Suby will fail to assign and fail to remove. You will see something that looks like a permissions error even if payment was successful. Fix the order and retest.
5. Avoid permission leaks
A few basic rules keep moderation clean:
- Do not give @everyone access to premium channels.
- Do not accidentally give staff powers to Premium.
- If you have multiple tiers, label them clearly. For example: Basic, Plus, Pro. Each tier should unlock different channels.
This is important for moderation. If access leaks, you cannot confidently auto kick because you lose track of who should see what.
Step 2: Enable Auto-Kick Discord and set a fair grace period
Now that your paid role is mapped, you can turn on automatic access control. This is where Suby really replaces manual cleanup.
Suby automatically handles access when a renewal fails and removes the paid role once the renewal window ends.
This happens automatically, no manual cleanup or commands needed.
How the grace period works
Suby includes a short, automatic grace window for members whose renewal fails.
During this window:
- The member is marked as pending.
- Suby automatically sends renewal reminders.
- Access remains active until the window ends.
If the member renews within the window, nothing changes. If they don’t, Suby automatically removes the paid role when the window closes.
This keeps your premium group consistent without requiring any manual cleanup.
What happens at each step
Here is a sample timeline for a 48 hour grace period:
Why this matters for moderators:
- You do not have to manually run a kick command
- You do not have to argue with users about whether they renewed
- You do not have to watch billing channels all day
The moderation feature is applied consistently. Everyone gets the same clock.
Step 3: Manage channels with correct permissions
Roles control who should have access. Channels control what that access actually means.
Set up clear channel permissions so that only active Premium users see premium areas.
A good structure looks like this:
- A public welcome or rules channel
- A Premium category for paying users
- An internal Staff category for moderators and admins
- A billing log or proof channel that shows payment activity and renewal events
Here is a permission matrix you can adapt:
Important details:
- Keep Staff separate. Do not ever give Premium moderation powers like Ban Members or Manage Messages.
- Test permissions with an account that only has Premium and nothing else. If you cannot test on a second account, assign a teammate the Premium role temporarily and ask them to confirm what they can see.
If you skip this test, you risk a silent permission leak where @everyone can view a premium channel or where Premium can view Staff. That becomes a moderation problem later.
Step 4: Use notifications for transparency and trust
Transparency helps both growth and moderation. Suby can post events when someone subscribes, renews, or cancels. These notification messages are created with three core commands:
- /notifnewsub to announce a new paying user
- /notifrenew to announce successful renewals
- /notifcancel to announce cancellations or end of term
You choose which channel receives these messages. Some servers post them publicly in a proof channel to create social proof. Other servers post them privately to a billing-log channel only staff can see.
Examples of clean notification messages:
- New member: "Welcome {user}. Role granted: {role}. Enjoy premium access."
- Renewal: "{user} renewed. Access stays active."
- Cancel or expiry: "{user} ended their subscription. Access will end at {date} after the grace period."
Why this helps:
- Users see that there is active demand. That increases conversion.
- Staff get clear billing history that matches Suby analytics.
- Moderators have evidence if a user complains after being auto kicked. You can point to the cancellation log in billing-log.
These announcements also make it obvious that the Discord bot is in control of access. That reduces pressure on human moderators.
Step 5: Build your reminders and subscription channels
Suby separates two important channels in your Discord server. You should create both.
Reminder channel
Create a public channel like #reminders. Give the Suby bot permission to Send Messages there.
Run /setupreminders and pick that channel.
This is where Suby will post renewal reminders. The reminder acts like a gentle nudge. It helps members renew before auto kick triggers. Members see it in real time directly inside Discord. No lost emails. No buried DMs.
This is important for retention. Renewal reminders lower churn, keep revenue predictable, and reduce sudden access loss.
Subscription channel
Create a channel like #subscription. Give the Suby bot permission to Send Messages and post embeds.
Run /setupsubscriptions and select that channel.
Suby will post a button members can click to subscribe. When a user clicks, Suby gives them a personal sign up link. They choose email, confirm with OTP, and pay with either wallet connect or deposit from an exchange. After payment, the Premium role is assigned automatically.
If permissions are wrong in either channel, Suby will throw an error instead of posting. Fix channel permissions, then rerun the setup command.
Step 6: Keep moderation consistent with automation
Manual cleanup creates conflict. Automation creates policy.
Here is why you want Suby doing this work instead of moderators doing it by hand:
- Predictable rules reduce argument in DMs.
- Role assignment and removal happen automatically.
- Grace period and auto kick run the same way for every user.
- Moderators no longer need to manually kick or un-verify people at 2 a.m.
- Billing reminders go out automatically, so you are not chasing failed payments.
This is more than convenience. It protects the perceived fairness of your community. Members respect rules when those rules clearly apply to everyone.
Suby also gives you visibility. Owner notifications tell you when someone subscribes, renews, or cancels. You can watch the flow without having to check spreadsheets.
Step 7: Payment flow for members
Here is what the user experience looks like from the buyer side once everything is configured:
- User goes to your #subscription channel.
- Suby shows available plans, including plan name and recurrence.
- User clicks the plan they want.
- Suby gives them a personal link. This link is private to that user.
- User enters email and confirms with OTP.
- User chooses how to pay:
- Wallet Connect Works with 100+ wallets
- Deposit Send crypto from any exchange or existing wallet
- User selects chain and token:
- Supported assets include USDC, USDT, ETH, SOL, and BNB
- Supported networks include Solana, Base, Arbitrum, Ethereum, and BSC
- Payment completes.
- Suby assigns the Premium role automatically and grants access inside Discord without delay.
This solves a big conversion leak. Before, you had to manually confirm wallet transfers and run a kick command to manage access. Now Suby manages the whole flow and updates roles automatically.
Because Suby supports both Wallet Connect and Deposit, even users who are not comfortable with advanced wallet setups can still pay. Deposit works with exchanges and common wallets, which is extremely important for accessibility.
FAQ and common edge cases
Q: What if a member upgrades from Basic to Pro mid cycle?
Give each paid tier its own role and map each plan with /setuprole. When the user upgrades, Suby can remove the old role and assign the new role. Make sure Pro has all Basic permissions plus any extra channels. Test both directions to avoid permission overlaps.
Q: How do I prevent Suby from auto kicking moderators or collaborators?
Create a Staff or Mod role that sits above Premium. Do not map Staff to any Suby plan. Suby only manages the roles you explicitly mapped. That means Staff will not be kicked even if they have no active plan, and they will not be touched by automated removal.
Q: What if a user is paying for multiple plans at once?
Some servers sell access to more than one product. You can map multiple roles in Suby. Decide if you want each plan to stack, or if you want higher tier to replace lower tier. Document it for staff so moderation stays consistent.
Q: What happens if Discord is down when Suby tries to update roles?
Suby queues the update. When Discord comes back, Suby assigns or removes roles as needed. Notification messages may post slightly later, but final role state will still match payment status. This prevents you from having to manually redo changes after Discord downtime.
Q: Can a user rejoin after being auto kicked?
Yes. If they rejoin without paying again, they will not get the Premium role. If they subscribe again through the Suby flow, Suby will automatically assign the Premium role and restore access. You do not have to run a command.
Q: What if a user says they paid but they still do not have access?
Check role order and bot permissions. The usual cause is that Suby cannot assign the Premium role because the bot role is below Premium in the hierarchy, or Suby does not have Manage Roles permission. Fixing role order instantly resolves most of these complaints.
Troubleshooting checklist
If something is not working, walk through this list in order:
- Role order Is the Suby bot role above every paid role it needs to assign? If not, move it up.
- Bot permissions Does Suby have Manage Roles and Send Messages in every reminder and subscription channel? If permissions are missing, Suby will fail to post and you may see an error.
- Role mapping Did you run /setuprole with the correct role ID and plan ID? One wrong ID creates a silent break where the subscription exists but the Premium role never gets assigned.
- Channel permissions Are premium channels locked for @everyone and open to Premium? If @everyone can see premium chat, your value collapses and auto kick feels pointless.
- Overlapping roles Do any other roles accidentally unlock premium channels? For example, if an old VIP role still grants View Channel in the paid category, expired users might still see content after auto kick is supposed to remove them. Clean that up.
- Grace and auto kick Are your grace period settings and auto kick settings actually turned on in the configuration? If they are off, Suby will not remove users or enforce expiry.
Quick setup in 10 minutes
Use this checklist to go from nothing to working access control:
- Invite the Suby Discord bot and grant requested permissions.
- Create a Premium role in Server Settings → Roles.
- Run /setuprole with your Premium role and plan ID.
- Move the Suby bot role above Premium in the role list.
- Lock premium channels to Premium only. Block @everyone.
- Create #reminders, allow Suby to post, and run /setupreminders.
- Create #subscription, allow Suby to post, and run /setupsubscriptions.
- Confirm Suby has Manage Roles and sits above all paid roles. If a renewal fails, Suby sends reminders and removes the paid role after its built in grace window.
- Turn on /notifnewsub, /notifrenew, and /notifcancel in a channel like #billing-log or a public proof channel.
- Pin an onboarding post in #welcome that explains pricing, access rules, and what happens if payment fails.
From that point on, Suby automatically assigns roles, sends reminders, removes access, and kicks expired accounts. Your moderators stop doing repetitive cleanup. Your users understand the contract. Your premium server keeps its value.
Final word
Running a paid Discord is not only about content. It is also about structure. If people can sit inside your premium server without paying, you are training your audience to ignore renewals. That hurts conversion, hurts retention, and burns out moderators who are forced to enforce rules by hand.
Role based access with Suby fixes that. You get reliable moderation without drama, automated role assignment, an optional auto kick feature that removes expired users, and renewal reminders that give people a fair chance to stay in.
When you protect access, your paid role actually means something. New members see proof that everyone there is a paying member. Returning members feel good about renewing because they know the space is not flooded with free riders. Mods stop doing accounting. And you finally get to focus on running a premium server instead of constantly chasing payment screenshots.