To set up ProBot, add it to your server from probot.io using an account that has Manage Server. Then log in to its dashboard, pick your server, turn on the welcome and logs modules, and choose a channel for each. Before you test anything, drag ProBot's role above every role you want it to give out. When ProBot "isn't working", the cause is usually role order or a private channel the bot can't see, not a bug.
Checked on each bot's own site or docs on 3 November 2026. We make PeakBot. Nobody paid to be in this post.
Before you start
- You need Manage Server. Discord only lets members with this permission add an app to a server. If your server doesn't show up in the list when you add the bot, this is the reason.
- Use a computer if you can. ProBot's dashboard is a website at probot.io, so a phone browser works. Dragging roles and editing long messages is still easier on a bigger screen.
- Make your channels first. Create a public channel for welcomes (for example #welcome) and a private one for logs (for example #mod-logs). The steps below assume both exist.
Part 1: Get the Discord side right
These are Discord's own permission rules. They apply to every bot, ProBot included, so sort them out first.
- Add ProBot to your server. Go to probot.io and use the button there to add it to Discord. Discord then asks you to pick a server and approve the permissions the bot asks for. Keep those permissions and confirm.
- Move ProBot's role up the list. On desktop, click your server name, open Server Settings > Roles, and drag the ProBot role above every role it should hand out (welcome roles, reaction roles, level roles). On mobile, open Server Settings > Roles and use the reorder option to drag the role by its handle. Mobile labels change between app versions, so look for "Reorder" or a drag handle.
- Know why the order matters. Discord's permission rules say a bot can only give, edit or sort roles that sit below its own highest role. It can only kick, ban or change the nickname of members whose highest role is below the bot's. A new bot's role usually lands near the bottom of the list, which is why fresh installs often can't give roles.
- Don't expect Administrator to fix it. Administrator grants every permission and skips channel permission overrides, but Discord's docs don't say it gets around role order. A bot with Administrator still can't give a role that sits above its own.
- Let the bot into the private logs channel. Open the logs channel's settings, go to Permissions, add the ProBot role, and allow View Channel, Send Messages, Embed Links and Read Message History. Per-channel overrides don't follow role order. Discord applies them in a fixed sequence: @everyone deny, @everyone allow, role deny, role allow, member deny, member allow. So if you denied @everyone on the channel, the bot is locked out until its role gets its own allow.
- Check the welcome channel too. The bot needs View Channel, Send Messages and Embed Links there, plus Attach Files if you plan to use a welcome image.
The Discord Help Center has Discord's own guides on roles and permissions if you want more detail on any of these.
Part 2: Set up ProBot's dashboard
- Log in. On probot.io, log in with Discord and choose your server. If the server isn't listed, ProBot usually isn't in it yet, or your account lacks Manage Server.
- Welcome messages. Open the welcome section in the sidebar (older guides call it "Welcome & Goodbye"). Pick your #welcome channel, write the message, and use the placeholders the dashboard lists to mention the new member. ProBot has welcome images, so add one if you want it. Save, then test with a second account or ask a friend to rejoin.
- A role on join. If you give new members a role when they join, check that it sits below ProBot's role. When ProBot won't give the welcome role, role order is the first thing to check.
- Logs. Open the logs section and point the events you care about (deleted messages, edits, joins, leaves, moderation actions) at #mod-logs. Save, then delete a test message and check that the log shows up. If nothing appears, go back to step 5 of Part 1.
- Reaction roles. Open the reaction roles section, choose the channel and message, then pair each emoji with a role. Members can only react to a message they can see, so check that the channel is visible to everyone who should use it.
- Roles missing from the dropdowns. ProBot's setup docs (on probot.io) say to drag its role to the top. If roles still don't show in the dashboard, they say to drag the role down, save, then drag it back up and save again.
Troubleshooting checklist
| Symptom | Most likely cause | Fix |
|---|---|---|
| Welcome or auto role not given | That role sits above ProBot's role | Drag ProBot's role higher in Server Settings > Roles |
| Roles don't appear in the dashboard | Dashboard hasn't picked up the role list | Move ProBot's role down, save, back up, save |
| No logs in a private channel | A channel override hides it from the bot | Allow View Channel and Send Messages for the ProBot role |
| Welcome message posts with no image | Bot can't attach files or embed links there | Allow Attach Files and Embed Links for the bot's role |
| Some reaction roles work, others don't | The failing roles sit above ProBot's role | Move ProBot's role above every reaction role |
| Some members can't use reaction roles | They can't see the channel, or an override blocks them from reacting | Check that channel's permissions for the roles those members hold |
| Can't kick or ban a member | Member's highest role is at or above ProBot's | Move the bot's role above that member's highest role |
How PeakBot does the same jobs
PeakBot covers the same three jobs from its web dashboard. The role order and channel permission rules above apply to it too, because they are Discord's rules, not ProBot's.
- Welcome: Dashboard > Welcome Messages. Plain text or a rich embed, posted in a channel or sent by DM, with an image. It can show who invited the new member. The DM and the image need a paid plan (Starter is $5.75/month or $48/year per server). Goodbye Messages works the same way.
- Logs: Set up on the Auto Moderation page. It logs message edits and deletes, joins and leaves, voice activity, and every manual mod action. Voice activity logs need a paid plan.
- Roles: The Roles page holds auto roles on join, self-assign roles and if/then role rules in one place.
- No setup command. Welcome messages, verification, auto moderation and the rest are configured on the dashboard, not by a command, and the dashboard shows you the result before anything posts. The getting started guide walks through adding the bot.
For a full side-by-side, see PeakBot vs ProBot. If you're also weighing MEE6, see ProBot vs MEE6.
Quick comparison
| Job | ProBot | PeakBot |
|---|---|---|
| Welcome images | Yes | Yes, on Starter |
| Welcome by DM | See probot.io | Yes, on Starter |
| Leveling | Yes | Yes. Message XP and standard voice XP free |
| Tickets | Yes | Yes. Transcripts free, auto-close on a paid plan |
| Temporary voice channels | Yes | Yes |
| Verification, anti-nuke, anti-raid | See probot.io | Yes, free |
| AI moderation | See probot.io | Pro |
| Cheapest paid tier | Premium Tier 1: $40/year per server | Starter: $48/year per server |
ProBot's first paid tier costs less per year than PeakBot's Starter. If ProBot already does what you need and you've fixed the role order, you don't need to switch. PeakBot fits better if you want verification, anti-raid, backups and analytics on the free plan, or AI moderation on Pro. PeakBot has no music or economy features.
Frequently Asked Questions
Why won't ProBot give the welcome role or auto role?
The role sits above ProBot's own role in Server Settings > Roles. Discord only lets a bot assign roles below its highest role. Drag ProBot's role above the welcome role and test again.
Why don't my roles show in the ProBot dashboard?
ProBot's docs say to drag its role to the top of the list. If roles still don't appear, drag the role down, save, drag it back up and save again.
How do I make ProBot log deleted messages in a private channel?
Turn on deleted-message logging in ProBot's logs section and choose the channel. Then open that channel's permissions, add the ProBot role, and allow View Channel, Send Messages and Embed Links. Channel overrides ignore role order, so the bot's role needs its own allow.
Does ProBot need Administrator?
Discord doesn't require it. A bot can work with the specific permissions its features use: Manage Roles for roles, Kick and Ban Members for moderation, and View Channel, Send Messages and Embed Links where it posts. Administrator also doesn't get around role order, so it won't solve role problems.
Why do reaction roles work for some members but not others?
Whether a bot can give a role depends on where that role sits, not on the member. So if a role fails for everyone, it sits above ProBot's role. If it fails only for some members, they usually can't see the channel or are blocked from reacting there. Check that channel's permissions for the roles those members hold.
Can I set up ProBot from my phone?
Yes. The dashboard is a website, so open probot.io in your phone's browser. Reorder roles in the Discord app under Server Settings > Roles using the reorder option. A computer is still easier for longer messages and dragging roles.
