Dashboard overview
A map of every dashboard page, what each one controls, and how the dashboard talks to the bot.
The dashboard at /dashboard is the control surface for your server. It talks to the bot over an authenticated websocket: every change you save is validated, applied by the bot, and confirmed back before the dashboard reports success.
Server selection#
After signing in with Discord you see every server where you are the owner or hold Administrator. Servers the bot is not in yet link to an invite page instead of a dashboard.
The pages#
| Page | What it controls |
|---|---|
| Server home | Bot enabled/disabled, command prefix, whether permission rules apply |
| Commands & modules | Module switches and per-command enable/disable |
| Moderation | Gulag role and gulag log channel |
| Logging | Log channel and the twelve log event toggles |
| Tickets | Panel appearance, categories, support roles, claim/close/transcript behaviour, departments |
| Security | Anti-invite, anti-spam thresholds, exempt roles/channels |
| Server Stats | Statistic channels, activity roles, tracking settings |
| Custom commands | List, builder, per-command configuration |
| Marketplace | Browse and install community commands |
| Settings | Read-only notice — global bot settings live on the main dashboard |
| Permissions | Read-only view of access rules |
Configuring each feature is covered in Module configuration; the switch hierarchy is explained in Module toggles; and the read-only permissions view in Server permissions.
How saving works#
- The dashboard sends a typed, size-limited update over the websocket (for example, ticket support roles are capped at 10, exempt lists at 25, statistic channels at 20).
- The bot validates every value, applies it, refreshes its in-memory state and replies with the result.
- Only then does the dashboard confirm the save.
Where the data lives#
Server configuration is stored per guild by the bot (one config document per server). Custom commands live as compiled scripts with their source kept in a content-addressed store, and marketplace listings are separate documents — see Custom commands and Community Marketplace for the details.