web dashboard.

the panel signs a server manager in through discord. after approval, it derives access from the servers where the account has manage server and intersects that list with the servers where havoc is installed. if the discord token expires, the server refreshes it; signing out removes the session. the bot operator also has a password-based break-glass sign-in.

each server opens on an overview with member count, moderation case count, economy-account count, current music state, owner, guild id, and command prefix. the members screen supports member lookup and links into a member profile. those profiles expose account and server information used by the panel’s role, balance, and moderation tools.

the moderation workbench can apply supported moderation actions and writes resulting cases. active punishments and case history remain visible alongside it. channels can be searched and then locked, unlocked, given slowmode, or purged. member profiles can add or remove manageable roles and adjust economy balance. music has pause, resume, skip, and stop controls for the active player.

automod exposes its enabled state, links, invites, spam, mentions, caps, punishment, duration, blocked words, and whitelist. logging manages event routes and ignored channels, members, and roles. roles shows autoroles, sticky roles, temporary roles, and reaction panels. the commands screen manages the same role restrictions asrestrictcommand.

settings can change the command prefix and ai watch and command toggles. the same area contains jail and antinuke controls. values are refetched from the bot after a save so the form reflects what was actually stored, including canonicalized and deduplicated lists.

,config automod
,config logging
,config roles
,restrictcommand list

these discord commands are useful for auditing the corresponding browser changes without relying on the form that made them.

the economy page summarizes balances and accounts; it does not expose every economy game or market workflow. the roles page reports temporary assignments and configured role panels. the dashboard also surfaces bot availability and reports an offline or unreachable process rather than presenting stale controls as healthy.

the bot operator has additional fleet-wide activity, job, and aggregate views. ordinary server managers do not receive those routes. a server manager’s navigation is limited to the servers returned by discord and the bot.

the panel does not reproduce the whole command registry. giveaways, tickets, suggestions and reports, custom response authoring, most economy games and market actions, ai conversation, afk, embeds, snipes, and setup diagnostics remain discord workflows. role panel creation also remains command-led even though configured panels can be inspected in the browser.

use ,help to discover those commands and their exact permissions. the command guide explains prefix and slash paths; each module page describes its supported discord workflow.

reaching a server page requires manage server, but that is only the outer gate. the api identifies the discord actor to the bot. sensitive mutations then require the same action permission used by commands, command restrictions are checked where applicable, server-owner-only operations remain owner-only, and target hierarchy is enforced.

verify the server name and id before saving, especially when you manage several similarly named servers. read destructive confirmation text, and use discord’s audit log plus havoc’s case and logging records to review changes. if the panel reports that the bot is unreachable, wait for a healthy status rather than repeating a mutation whose result cannot be confirmed.

for a first configuration, run ,setup in discord before using browser controls. the diagnostic catches missing bot permissions, intents, and hierarchy that a successful form save cannot repair. the permissions guide explains the two layers in detail.