Quick diagnosis
Pick a symptom and we will show the usual cause and the repair steps. If your problem is not on the list, write to us on the support server.
Support tracks
Help with Verify, VenonSec, the logs, AutoMod, LinkShield and anti-raid scenarios.
Support with tickets, reports, the moderation desk, reviews and operator work.
Onboarding for the engagement modules: leveling, reaction roles, suggestions, reminders and statistics.
Help after rollout mistakes and problems with permissions, the API, the runtime or the web panel.
The fastest answers come when the report already carries the basic technical and operational context.
Say which area the problem concerns: security, moderation, the dashboard, the API or the community.
Name the module or command that misbehaves and what has already been configured.
If it is a bug, describe the symptom briefly and when it appears.
For urgent matters, go straight to the support Discord.
Discord is the best path for rollouts, urgent bugs and live iteration. Email suits asynchronous and formal contact.
Guide
Click “Add the bot” on the Venon Security Discord home page, pick a server where you hold administrator permissions and confirm the permission scope. Once added, the bot appears in the member list, and you configure it either in the web dashboard or with the /venonsec-panel command.
Open the panel and go to Security → Raid protection, or use the /venonsec-panel command. Set the “Join wave (joins/min)” and “Message spam (msg/5s)” thresholds, choose the response plan (slowmode, a proposed lockdown), switch RaidWatch on under Monitoring and alerts and point it at an alert channel, then turn Venom Shield on in approval mode on the Emergency mode screen — it carries out the plan. On public servers it is worth enabling the protection right after adding the bot. Full instructions: the guide “How do you protect a Discord server against a raid?”.
You enable AutoMod in the panel under Security → Content protection. The Detectors section configures anti-spam, the mention limit and caps detection; the Word blacklist and Regex blacklist sections take your own patterns; and Response to a violation picks the action (delete the message, warn, mute) and the log channel. The response needs no moderator present.
In the panel open Community → Onboarding and verification, turn “Verification active” on, choose the “Verification type” (a button or a captcha) and point it at the verification channel and the role granted afterwards. You can add a “Minimum account age (days)” and starter roles. If you have neither a channel nor a role yet, use the Auto-configure button and then Publish the panel. Unverified accounts then never see the rest of the server.
You configure the ticket system with the /ticket-crm command (it requires the Manage Guild permission) and in the panel under Moderation → Tickets. There you set the categories, the handling roles and the channel where members open a ticket. Tickets can be claimed, handed over, extended and closed with a summary.
Make sure the Venon Security Discord bot role sits high in the role hierarchy — above the people it is meant to moderate. Depending on the modules you use, the bot needs permissions such as Ban Members, Kick Members, Manage Messages, Manage Roles and Moderate Members. You set them in the Discord server settings under Roles.
Slash commands can appear with a delay after the bot is added. Check that the bot holds the “Use Application Commands” permission, refresh the Discord client (Ctrl+R) and make sure you have not restricted the commands in the server's integration settings. If the problem persists, remove the bot and add it again with the full scope.
The usual cause is the role hierarchy: the Venon Security Discord bot has to hold a role above the person it is trying to ban. Check also that the bot has the Ban Members permission and that the target does not hold a protected role. Once the hierarchy is fixed, the /ban command works.
In the panel open Moderation → the Logs tab and pick the channels, or click Auto-configure, which creates the full set of channels in one category and sets the permissions. The bot records moderation actions (ban, kick, mute, warn, message deletion) and server events in separate categories. Set the “Log viewer role (ID)” too, so the channels are not visible to @everyone. The history of panel configuration changes lives under Server → Change log.
Combine several layers: AntiRaid (join wave thresholds), RaidWatch (alerts to the staff channel), AntiFake (risk scoring for new accounts), entry verification, plus LinkShield and AutoMod on the content. During an attack turn slowmode or a lockdown on, and use /ban with the raid option to ban the members of the wave. The guide “How do you prepare a Discord server for an attack?” walks through it step by step.
Guides
FAQ
Click “Add the bot” on venon-sec.xyz, pick a server where you hold administrator permissions and confirm the scope. You configure the bot in the web dashboard or with the /venonsec-panel command.
In the panel, under Security → Raid protection, set the “Join wave (joins/min)” and “Message spam (msg/5s)” thresholds, choose the response plan (slowmode, a proposed lockdown), switch RaidWatch on under Monitoring and alerts and point it at an alert channel, then turn Venom Shield on in approval mode on the Emergency mode screen — it carries out the plan.
Check the “Use Application Commands” permission, refresh the Discord client and review the server's integration settings. Commands sometimes appear with a slight delay after the bot is added.
Put the bot's role high in the role hierarchy and grant permissions such as Ban Members, Kick Members, Manage Messages, Manage Roles and Moderate Members — depending on the modules you use.
AutoMod, from the Security → Content protection screen, detects spam, excessive mentions and caps, handles a word blacklist and regular expressions, and carries out the chosen action (delete the message, warn, mute) together with a log entry — without a moderator.
You configure tickets with the /ticket-crm command and in the panel under Moderation → Tickets: the categories, the handling roles and the channel where tickets are opened. Tickets can be claimed, handed over, extended and closed with a summary.
Verify grants an access role once someone passes the verification (optionally with a CAPTCHA and a minimum account age). Bots and unverified accounts never see the rest of the Discord server.
Yes. Venon Security Discord was built in Poland and with Polish communities in mind — the commands, the panel and the bot's replies are fully available in Polish. A server can switch to English just as well: one setting changes the language of the bot and the panel at once.
Yes. The Venon Security Discord bot combines the AntiRaid, RaidWatch, AntiFake, Verify and LinkShield modules, which together defend the server against raids, spam, flooding and dangerous links.
Yes. Venon Security Discord ships a full web dashboard for configuring every module, the analytics, the logs and the permissions — without having to remember each slash command.