Frequently Asked Questions

Click the "Add to Server" link on the site, pick a server you administer on Discord's authorization screen and approve the permissions. The bot joins within seconds; after that you sign in to the site with your Discord account and open that server's dashboard.

VeyroBot handles moderation, security, roles, channels, music and logging on its own, so the invite asks for the permissions all of that needs — that way you don't hit "the bot lacks this permission" when you turn a module on. You can switch off modules you don't use in the dashboard, and you can narrow the bot's role permissions in Discord; a disabled module takes no action in your server.

VeyroBot scans your server's security settings, protection modules and silently broken configuration with real checks, then sends the result as a direct message to whoever added it. The findings are never posted in a channel. The report has a 0-100 score, category scores and prioritized findings, and you can fix some of them with one click from the dashboard, with your approval.

You sign in with Discord, and your permission for each server is verified live against Discord; only people with the required permission in that server can see its settings. The server owner can also open dashboard access to specific roles. For actions that change Discord settings (such as security fixes), dashboard access alone is not enough — the person must also hold the permission in Discord.

Discord caches slash commands and sometimes updates them late. You can resync the commands from the dashboard, which pushes the list to Discord again. If they still don't appear, restart the Discord app and make sure the bot has "Use Application Commands" in that channel. All built-in commands work only as slash (/) commands; there are no prefix (!) text commands.

Adding and setting up the bot is free; the setup, the health report and basic use cost nothing. Which module belongs to which plan is listed in one place — the matrix on the Premium page — and it is always current, because it is generated from the bot's real access rules rather than written by hand.

You assign the license you bought to a server you administer from the dashboard, and you can move it to another server whenever you like; a license is active on one server at a time. The only exception is a license gifted by the bot owner: it stays on the server it was given to and cannot be transferred.

You can cancel at any time before the next renewal using the subscription management link in the email Polar sends after your purchase; for help, write to support@veyrobot.xyz. Within 7 days of your first purchase you can request a refund without giving a reason; in the EU, EEA and UK the mandatory statutory right of withdrawal (14 days) is reserved; nothing is deducted and the money goes back to the method you paid with. The 7-day refund guarantee does not cover automatic renewals or gifted and promotional licenses. The details are in the refund section of the Terms of Service.

No. Premium purchases are processed by Polar, which acts as the merchant of record for the sale; your card details never reach our servers. All we store is the subscription status, the order number and the expiry date.

If the join threshold you set is exceeded within the window you choose (10 seconds by default), text channels lock automatically and an alert is posted to your moderation log channel. You choose the threshold in the dashboard; nothing is hardcoded. You can also turn on an account-age check and a captcha gate for new members. You can also have the lockdown lift itself after a set time and, in panic mode, kick new joins and pause invites while it lasts; the window joins are counted over is adjustable too.

Nobody is removed from the server; only permission to post is temporarily closed. The /unlock command restores every locked channel to the permissions it had before: what was explicitly allowed stays allowed, what was denied stays denied. If your server genuinely gets a rush of joins after a stream announcement, raising the threshold reduces false alarms.

If a staff member deletes many channels or roles in a short time, mass-bans, or adds bots, VeyroBot applies the action you chose — the recommended one is removing their dangerous roles — and posts an alert with evidence to your mod-log channel. You set the limit and the time window. The server owner and VeyroBot are always exempt, and the bot cannot act on roles above its own; the Health card points that out. You can also quarantine the person: all their roles are removed, they get a quarantine role and a 28-day timeout; if it was a false alarm, one click in the dashboard releases them.

While protection is on, the permissions, category and position of deleted channels and roles are kept as a snapshot; after an incident you can rebuild them all with one click from the dashboard, and VeyroBot's settings move to the new IDs. Nothing is rebuilt automatically — the decision is yours. Deleted messages do not come back and channel IDs change: this is not a backup tool.

The score is not a guess but the result of real checks: Discord's security settings, the state of the protection modules and the consistency of your configuration are each audited and scored under security, protection and configuration. Every lost point comes with the reason and how to fix it. Silent failures — a setting tied to a deleted channel, an auto-role the bot cannot assign — are caught here too.

Yes. The Health card only lists checks that actually fail on that server and are reachable; you pick which ones to apply, and everything applied can be undone within 24 hours. The person applying it must also hold the permission in Discord — dashboard access alone is not enough.

There are separate, individually toggleable filters for Discord invite links, links outside your allowlist, profanity, rapid consecutive messages (spam), excessive capitals and mass mentions. You set each filter's sensitivity and the action taken on a violation, and you can add allowed domains to the list. For the invite link and link filters you can also choose channels where such posts are allowed (for example, invites only in a promotion channel). Edited messages are checked with the same rules. There are also filters for repeated messages, emoji spam and line spam; blocked words support the * wildcard only at the start or end, and you can write up to 10 regex patterns for advanced rules. The blocked-word, regex, invite, link and mass-mention filters run as Discord's own AutoMod rules and block the message before it is even sent; the punishment you chose is still applied by VeyroBot.

You can have a punishment of your choice applied automatically once a member reaches the number of warnings you set. Warnings you issue by hand — from the dashboard or with /warn — count towards that total too, and the tier still works even if the AutoMod module is off. Every punishment is collected in a single case history per member.

You can route logs to separate channels by type: moderation actions, message edits and deletions, voice channel activity, and member and server changes. If no log channel is selected, those events are not written anywhere — the Health card reports that as a gap.

XP is earned per message, and you tune the rate with a multiplier in the dashboard. If you turn it on, time spent in a voice channel with at least one other member also earns XP; sitting alone or deafened does not. You can also pick channels and roles that earn no XP. Members who reach a level you define can get a role reward automatically, and you choose which channel the congratulation message goes to. If you choose, you can also publish your server's leaderboard on a public page.

Yes. Members customise their rank card in the dashboard studio: a background from the gallery or their own image, theme colour and palette, avatar shape and ring, XP bar, font, the stat in the top-right corner, frame, Veyro's pose and a short title. For welcome and goodbye you write the message text yourself and choose whether the new member gets a notification and whether the image card is sent; welcomes can also go to the member by DM. The welcome card's design is fixed. The small VeyroBot signature in the card corner can be removed depending on your plan; details are on the Premium page.

A single menu can hold up to 25 roles, and members pick their own from a dropdown or buttons. You can optionally attach a duration: when it runs out, the role is removed automatically. That countdown keeps running even if the module is switched off, the menu is deleted or the subscription ends — the promise made to the member is kept.

When a member opens a ticket from the panel you posted, a private channel opens under the category you chose, visible only to that member and your support role. If you define up to 5 ticket types, the panel comes with a select menu and each type goes to its own category and staff role. Staff claim a ticket with the Claim button, and an optional reason is entered on close. When the ticket closes, the full transcript is sent as a .txt and a browser-friendly .html file to the ticket log channel you picked, and, if enabled, to the opener by DM. If no log channel is set, no transcript is posted to a channel.

There are achievements that unlock as members hit goals, birthdays entered by members themselves with a temporary role and a celebration message on the day, a starboard that copies messages with enough ⭐ reactions to a highlights channel, a suggestion system with 👍/👎 voting, and live channels showing your member count. Each one is switched on and off separately. Application Forms collect staff, event or whitelist applications in a Discord window, and you accept or reject them from a review channel.

It plays links and search results from YouTube and Spotify. You manage the queue either from the buttons on the "now playing" panel in Discord or from the web dashboard: skip, pause, shuffle, repeat and audio filters. If nobody is left in the voice channel, the bot waits a minute and, if it is still empty, stops the queue and leaves.

You pick a "create room" channel in the dashboard. A member who joins it instantly gets their own room and can lock it, hide it, set a user limit and rename it from the control panel posted inside. When the last person leaves, the room deletes itself, so empty channels don't pile up.

Yes. For stream and video alerts you can follow YouTube, Twitch, Kick, Reddit, Bluesky, RSS and podcast sources. Timed messages post announcements at set intervals or when the server gets busy, and reminders let you set repeating messages on the days and hours you choose. Invite tracking also reports which invite each member came from to the channel you pick. For one-off announcements, the Message Builder lets you compose a message with embeds and link buttons, send it and edit it later from the dashboard.

The assistant runs on Google Gemini. Members can talk to it with the /ai command, by mentioning the bot or by replying to its message, and the conversation continues with memory of earlier messages. You decide which channels it answers in, and you can switch the module off entirely.

Yes. In the dashboard you define a persona and a system instruction specific to your server, and the assistant answers accordingly. You can make it behave like a playful mascot, a serious moderator or a helper focused on one particular topic.

So the conversation can continue, recent messages are kept — at most 500 per server — and sent to Google Gemini to generate replies, where Google's privacy policy applies. If you switch the module off, no new conversation data is collected, and you can also request that existing records be deleted.

Only what the features need to work: your server ID and settings, user IDs for moderation and leveling records, channel and role IDs for notifications and role assignment, plus each module's own data (ticket records, achievements, suggestions, birthdays members entered themselves). When you switch a feature off, it stops collecting new data. Server statistics (daily message and join counts) are not tied to any module and are always kept. Everything lives in a local database on the server the bot runs on, and no third-party tracker is used to measure site usage.

The server's data (levels, case history, settings) is deleted automatically 30 days after the bot is removed. The waiting period exists so that servers which remove the bot temporarily and add it back don't lose their data: if the bot is added back within 30 days, nothing is deleted. If you want it deleted sooner, just ask — deletions cannot be undone.

Server administrators or members can request permanent deletion of records belonging to them or their server — warnings, logs, level data, AI conversation history and so on — through the contact form or the support server. Requests are handled within 30 days at the latest. Your rights are set out in full on the Privacy Policy page.

Autorole only applies to members who join after it is set up, so if you enabled it later, existing members never received the role. The `/roleall` command fills that gap: it distributes the role in bulk to existing members who do not have it yet. Members who already have the role are never sent a request, and members awaiting verification are skipped. The job runs in the background and can take hours on large servers; its progress is shown live on a card in the channel, it resumes where it left off even if the bot restarts, and it can be stopped at any time.