This guide explains what to configure first, where daily work happens, and which tool to use when something needs attention. Start small, verify each system, then add the features your server needs.
Both surfaces operate on the same VERTEX systems and the same selected server data.
Inside Discord
Moderate a member, play music, open a setup flow, inspect status, or configure a feature while you are already in the server.
On the web
Review state, change configuration, work through tickets, manage giveaways, and inspect live bot or Lavalink health.
Do these steps in order. Role hierarchy and channel permissions are easier to solve before members start using the systems.
Use the official invite and choose a server where you can manage bots.
Move it above every member role it must assign, remove, moderate, or verify.
/setupReview the readiness report. It identifies missing core systems and points to the commands that configure them; it does not change settings itself.
Enable logs, AutoMod, anti-raid, and verification before community extras.
Create ticket panels, welcome messages, reaction roles, giveaways, levels, and creator alerts as needed.
Run /status, /health status, and /ping. Test one real workflow before opening it to everyone.
Sign in with an approved Discord account and confirm the correct server appears as the active workspace.
A permission allows an action. Role hierarchy decides whether Discord will actually let that action succeed.
| Permission | Used by |
|---|---|
| Manage Server | Required from the human operator for setup, configuration, insights, and dashboard server access. |
| Manage Roles | Verification, reaction roles, level rewards, and automated role assignment. |
| Manage Channels | Tickets, lockdowns, channel configuration, and permission updates. |
| Manage Messages | Clear, AutoMod cleanup, and moderation workflows. |
| Moderate Members | Timeouts and automatic punishment escalation. |
| Kick / Ban Members | Manual moderation and configured AutoMod or anti-raid responses. |
| View Audit Log | Executor detection, security events, and server structure logs. |
| Send Messages / Embed Links / Attach Files | Panels, logs, transcripts, alerts, and rich command responses. |
| Connect / Speak | Music playback through Lavalink. |
Open dashboard.botvertex.pro, sign in with Discord, and select a server you own or can manage.
Bot, database, Lavalink, service readiness, recent activity, and a full /serverinfo profile.
Design the welcome message and preview, then review the latest five deliveries with member context.
Configure panel and DM copy, CAPTCHA routing, verified roles, logs, and recent verification activity.
Set the level-up message and channel, then add reward roles for specific levels.
Monitor multiple creators with routing, resolver status, and a custom message per creator.
Monitor multiple channels with routing, resolver status, and a custom message per channel.
Review, claim, reply, close, reopen, delete, and download transcripts.
Warnings, timeouts, kicks, bans, unbans, logs, health monitoring, history, and snapshot recovery.
Create in a real Discord channel, monitor, end, and reroll winners.
Edit core rules, escalation, anti-raid settings, presets, and history.
See Lavalink readiness, current playback, queue, loop, volume, voice channel, and runtime statistics.
Jump between modules, servers, and operational records without hunting through menus.
Use reasons consistently. The next staff member should understand what happened without reconstructing the conversation.
/warnAdd a persistent warning and moderation record./unwarnDeactivate an active warning by ID./warnsReview a member's active warnings./historySee a member's moderation history./caseOpen a specific moderation case./timeoutTemporarily restrict communication./kickRemove a member from the server./banBan a member with a recorded reason./clearRemove a controlled number of channel messages./lock / /unlockClose or restore channel messaging./slowmodeSet channel message rate limits.Start with logging and mild enforcement. Add escalation only after watching how real members behave.
Anti-links, anti-invites, caps filtering, blocked words, and configurable ignored roles or channels.
Message limits and time windows tuned to the pace of the server.
Automatic warnings with configurable timeout, kick, and ban thresholds.
Join and audit-action thresholds, lockdown, emergency verification, owner alerts, and dangerous permission detection.
/automod statusReview the current configuration./automod wordsAdd, remove, list, clear, enable, or disable blocked words./automod spamSet anti-spam limits./automod punishmentSet automatic escalation thresholds./automod antiraidEnable integrated anti-raid protection./automod antiraid_unlockRelease lockdown and restore emergency verification state.Ticket panels create private channels. Staff can claim work, reply, preserve transcripts, close cleanly, and reopen when necessary.
Discord
Use /ticket to configure panels and work with ticket controls in the server.
Dashboard
Claim, reply, close, reopen, delete, and download transcripts from one server-scoped view.
Captcha-based access with role assignment, expiry, logging, session reset, and emergency anti-raid integration.
/verificationCustom welcome channel, message, image, member count, optional role, preview, and test flow.
/welcomeCreate panels or connect emoji-to-role assignments to existing messages, with add/remove behavior.
/reactionroleCreate timed giveaways, choose winner count, track participants, end early, and reroll.
/giveawayMember profiles, leaderboard, role rewards, level-up channel, resets, and staff adjustments.
/levelMember reputation, leaderboard, controlled staff adjustments, role rewards, and configuration.
/karmaLive notifications with channel, optional mention role, custom message, status, and manual check.
/twitchUpload notifications with channel, optional mention role, custom message, status, and manual check.
/youtubeJoin a voice channel, run /music play, and use the same command group for queue control.
playskipstoppauseresumedisconnectclearshuffleremovequeuenowplayingvolumeloopstatusconfig
Moderation, messages, members, voice activity, server structure, roles, channels, and configured system events.
/logsActivity, joins, leaves, staff actions, support load, and operational trends collected per server.
/insightsQuick server and member context for staff and support work.
/serverinfo /userinfo/pingDiscord latency, bot response, memory, SQLite, and Lavalink signals./statusCurrent service, manager, database, and runtime overview./healthOwner health checks, alert channel, memory threshold, and service alerts./backupOwner-only manual backup, status, and recent backup list.Type a command in Discord to see its current subcommands and required options.
/automod /backup /health /logs /reactionrole /setup /status /twitch /verification /welcome /youtube
/ban /case /clear /history /kick /lock /slowmode /timeout /unlock /unwarn /warn /warns
/music
/about /giveaway /guide /help /insights /invite /karma /level /ping /serverinfo /support /ticket /userinfo
These are the checks staff usually need before opening a support request.
Confirm commands were deployed and the bot was invited with the applications.commands scope.
Move the VERTEX role above the target role and confirm Manage Roles is enabled.
Use an approved Discord account and confirm that account owns the server or has Manage Server.
Confirm the user is in voice, the bot can Connect/Speak, Lavalink reports ready, and the channel is not blocked.
Confirm commands were deployed and the bot was invited with the applications.commands scope.
Move the VERTEX role above the target role and confirm Manage Roles is enabled.
Check the staff member, target member, bot role hierarchy, and the exact Moderate/Kick/Ban permission required.
Check Manage Channels, category permission overwrites, staff roles, and the configured ticket category.
Check Attach Files, Send Messages, Embed Links, and the transcript or ticket log channel.
Confirm the user is in voice, the bot can Connect/Speak, Lavalink reports ready, and the channel is not blocked.
Reduce thresholds and add intentional ignored roles or channels. Avoid disabling every layer at once.
Use an approved Discord account and confirm that account owns the server or has Manage Server.
Confirm VERTEX is in the selected server, your account can manage it, and the relevant channels or roles still exist. Re-authenticate after permission changes; if the problem remains, share the affected module and approximate time in the official support server.
Run /music status and /ping. If the service remains unavailable, no server setting can repair the managed audio service; report the time and server in official support.
Logs, AutoMod, verification, and backups should exist before a growth push.
Separate logs, tickets, health, welcome, giveaways, and creator notifications.
A good moderation trail is understandable days later, not only in the moment.
Open a ticket, verify a test member, create a giveaway, and join voice before launch.
Check bot, SQLite, managers, Lavalink, dashboard, and one Discord-backed selector.
A smaller configuration your team understands is better than every feature turned on.