ProBot is not a desktop program you download. You add it to a Discord server by authorizing the ProBot application, then configure its features from the web dashboard. This guide covers the safe installation process, permissions, slash commands, welcome messages, logs, roles, leveling, moderation, testing, and troubleshooting.
What ProBot does
ProBot is a multipurpose Discord application for moderation, welcome and goodbye messages, server logs, auto-roles, self-assignable roles, embeds, leveling, social commands, alerts, protection features, and—according to its current site—a newer ticket module. It has a free version, while some protection, logging, role, customization, and anti-raid features require Premium.
As an Amazon Associate I earn from qualifying purchases.
See the official ProBot documentation and current command list for features that may change over time.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you need before installing ProBot
- A Discord account.
- A server where you have Administrator or Manage Server permission to authorize the bot.
- Permission to edit server roles and channel permissions.
- A private test channel where you can try commands without disturbing members.
- A plan for which permissions and modules ProBot actually needs.
ProBot’s current documentation says Administrator access is required to see a server in its dashboard. That is separate from using individual moderation commands: a moderator may be allowed to run commands without being able to configure the dashboard.
#1 Best Overall
How to add ProBot to a Discord server
- Open the official ProBot website, its official command page, or the official Discord application listing.
- Choose Add To Discord or the equivalent official invite button.
- Sign in to Discord if prompted.
- Select the server where you want to install ProBot.
- Review the requested permissions before authorizing the application.
- Complete Discord’s authorization or verification prompts.
- Open the server and confirm that ProBot appears in the member list.
Do not use copied OAuth links, unofficial invite pages, or bots with similar names. If the wrong server is selected, cancel the authorization and repeat the process from an official destination.
Set ProBot’s permissions and role hierarchy
Granting Administrator is the quickest way to avoid missing-permission errors, but it gives the application broad authority over the server. A more cautious setup grants only the permissions required by the modules you enable. The trade-off is that limited permissions require more troubleshooting.
Move the ProBot role above managed roles
Discord prevents a bot from assigning, editing, or managing roles that are at or above the bot’s highest role. In Server Settings > Roles, move ProBot above every role it must assign or manage, while keeping sensitive administrator roles protected.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsAuto-Roles cannot assign roles with administrative privileges. If roles do not appear in ProBot’s dashboard, save the role position; if necessary, move ProBot down, save, then move it back up and save again. Also check that ProBot can view and send messages in the relevant channels.
Remember that two permission checks apply to moderation: the person running the command needs the appropriate Discord permission or an allowed ProBot Mod Role, and ProBot itself needs permission to perform the action.
Open and configure the ProBot dashboard
- Go to the ProBot website and log in with Discord.
- Open the dashboard and choose your server from the left-side menu.
- Select a module, then enable it.
- Choose its channel, role, message, or command settings.
- Save the changes.
- Test the feature in Discord.
The dashboard can enable or disable modules, restrict commands by role or channel, create aliases, and control automatic deletion of command messages and bot responses. Keep moderation commands in a private staff channel and restrict them to the roles that need them.
Use ProBot’s slash commands
ProBot’s current FAQ says it uses Discord slash commands rather than a traditional command prefix. In a channel, type /, choose ProBot from Discord’s application-command menu, and select the command. Discord’s autocomplete is the authoritative source for the live options and required arguments.
Recommended Free Tools
| Command | Purpose |
|---|---|
/ban |
Ban a member |
/unban |
Remove a ban |
/kick |
Kick a member |
/timeout |
Temporarily restrict a member |
/clear |
Remove messages |
/warn |
Warn a member |
/lock and /unlock |
Restrict or restore channel messaging |
/slowmode |
Configure channel slowmode |
/role |
Add or remove roles |
/rank and /top |
View leveling information |
/server |
Show server information |
Command names and options can change. Avoid relying on old tutorials that use commands such as !ban; use the live ProBot command page and slash-command picker instead.
Configure the essential modules
Welcome and goodbye messages
- Open Welcome & Goodbye in the dashboard.
- Enable welcome messages and enter the message.
- Choose a channel or direct message destination.
- Optionally enable a welcome image.
- Configure goodbye messages and their destination.
- Save and test with a test account if possible.
The current welcome documentation supports JPG, PNG, and JPEG background images under 3 MB. GIF backgrounds are not currently supported. See the welcome module documentation for available image variables and settings.
Auto-Roles
- Open Auto-Roles in the dashboard and enable it.
- Select the role or roles for new members.
- Confirm ProBot’s role is above the target roles.
- Test with a new member account.
If the server uses Discord’s rules screening, role assignment may wait until the member accepts the rules. Administrative roles cannot be assigned through the documented Auto-Roles feature. Invite-specific auto-roles are a Premium feature. More details are available in the Auto-Roles documentation.
Logs
- Open Logs in the dashboard.
- Enable logging and select a log channel.
- Turn on only the event types your staff needs.
- Choose an embed color if desired.
- Trigger a harmless test event, such as editing a test message.
ProBot can list joins, leaves, bans, timeouts, kicks, deleted and edited messages, role and channel changes, voice events, permission changes, and moderation commands. It does not automatically guarantee a complete audit trail: permissions and premium storage limits can affect coverage. If logs fail, check Manage Webhooks; if the permission state remains inconsistent, the documented recovery step is to remove and re-invite the bot. See the logs documentation.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchEmbed messages
In Embed Messages, choose Create, configure the title, description, URL, image, thumbnail, author, color, footer, and fields, preview it, then use Send to a Channel. Save embeds you plan to reuse and use the edit control to modify a sent embed.
Current documented Discord limits include:
- Message content: 2,000 characters
- Embed title: 256 characters
- Embed description: 4,096 characters
- Maximum fields: 25
- Field name: 256 characters
- Field value: 1,024 characters
- Footer: 2,048 characters
- Total embed characters: 6,000
See the embed documentation for the current interface.
Self-assignable roles
This module depends on an embed and a sent message; it is not just a single reaction-role switch.
- Create and send an embed message first.
- Open Self-Assignable Roles.
- Add a message, edit it, and select the embed you created.
- Select the sent Discord message.
- Add buttons, select-menu options, or reactions.
- Assign a role to each interaction.
- Choose toggle, give, or take mode.
- Test using a non-administrator account.
One embed message can contain up to 25 buttons, while a select menu can contain up to 20 options according to the current documentation. Multiple roles for one option require Premium Tier 1 or Tier 2. Unused buttons or select-menu elements on the same message can interfere with reactions, and ProBot must be above every role it assigns. See the self-assignable roles guide.
Leveling
ProBot tracks member activity through its leveling system. From the dashboard, configure level behavior and any available role rewards, then let members check progress with commands such as /rank and /top. Avoid rewarding spam: review XP settings and use moderation controls alongside leveling.
ProBot’s official site describes rewards that can include roles, permissions, and channel access, but the exact settings and availability can change.
Moderation and protection
Start with Discord’s native permission system, then use ProBot’s dashboard restrictions to limit commands by staff role and channel. Test warnings, clearing, timeouts, locks, kicks, and bans in a test server or with controlled test accounts. ProBot cannot bypass Discord’s permission or role hierarchy rules.
Rank #4
Protection and anti-raid capabilities are among the features that may require Premium. Do not enable a security feature without checking what it does, which permissions it needs, and how staff will recover from a false positive.
Test ProBot before opening the server
- Create a private staff or test channel.
- Create a non-sensitive test role below ProBot’s role.
- Use a non-owner test account where possible.
- Run one slash command and confirm the response.
- Test a welcome message with a test account.
- Test role assignment.
- Edit or delete a test message and confirm the log.
- Test one moderation action in a controlled environment.
- Confirm a restricted command is denied in the wrong channel or to the wrong role.
- Review ProBot’s permissions after testing and remove anything the enabled modules do not need.
ProBot troubleshooting
ProBot is not in the server
Confirm that the invite was authorized for the intended server, that you had Administrator or Manage Server access during authorization, and that ProBot was not removed afterward. Re-invite it from an official ProBot destination if necessary.
The server is missing from the dashboard
Check that the Discord account used to log in currently has Administrator permission. A moderator role or channel-management permission may not be enough for dashboard visibility according to ProBot’s current dashboard documentation.
Commands do not appear
Type / and select ProBot from the application list. Then check whether the command or module is disabled, whether the channel has a command restriction, and whether the user has the required Discord permission or an allowed ProBot Mod Role. Reopen Discord or try another channel if the command menu is stale.
ProBot cannot assign roles
Move ProBot’s highest role above the target role, confirm the target role is not administrative, and check channel or server permission overrides. If the dashboard still does not show roles, save the hierarchy change and try the documented move-down, save, move-up, save sequence.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Logs are incomplete
Confirm the log category is enabled, a channel is selected, and ProBot can access that channel. Check Manage Webhooks. If logging remains broken, remove and re-invite ProBot.
Welcome messages are not sending
Confirm the Welcome module is enabled, the destination channel still exists, ProBot can view and send messages there, and the message or image meets the module’s limits. Test with a new account rather than repeatedly leaving and rejoining your main account.
Premium features remain locked
Check that the purchase is attached to the correct server and bot. ProBot’s premium documentation recommends kicking and re-inviting the premium bot, or removing the standard bot before inviting the premium bot again, when premium access does not appear.
Is ProBot free?
ProBot has a free version, but advanced features are paid. The ProBot pricing page displayed these figures on August 18, 2026:
| Plan | Displayed price | Typical reason to consider it |
|---|---|---|
| Premium Tier 1 | $5/month monthly billing, or $3.33/month billed yearly | Additional protection, temporary links, invite-specific auto-roles, and other premium features |
| Premium Tier 2 | $10/month monthly billing, or $6.67/month billed yearly | Tier 1 features plus anti-raid capabilities and a personalized bot |
These are a dated pricing snapshot, not a permanent promise. Taxes, currency conversion, billing terms, promotions, and feature availability may vary. Core installation and many basic features do not require Premium. Consider upgrading only after identifying a specific feature your server needs. See official pricing and Premium documentation.
ProBot alternatives
ProBot is a good fit if you want one dashboard for moderation, welcome messages, logs, roles, leveling, and related tools. It may be a poor fit if you need the smallest possible permission scope, a highly specialized ticket or analytics system, self-hosting, or dashboard access for moderators without Administrator permission.
- MEE6: Broad server growth, moderation, leveling, reaction roles, giveaways, and creator alerts.
- Dyno: General moderation and server-management tools, with giveaways and streamer-related features.
- Ticket Tool: A more specialized choice for support-ticket workflows.
They are not automatically like-for-like replacements. Compare current free limits, permission scope, slash-command support, moderation depth, anti-raid tools, role systems, logs, ticket features, pricing, privacy policies, support, and uptime before switching.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
