Documentation

Getting started

There is nothing to install. Log in with Discord and the dashboard shows you what you are allowed to manage.

1. Invite the bot to your server, if it is not there yet. The invite is private on this deployment, so ask in the support server for one.
2. Log in with the button in the header. Discord asks you to authorise the dashboard to read your identity and server list.
3. Open the dashboard and pick a server.

The dashboard never sees your Discord password. It stores a signed session cookie, and the list of servers it shows you is filtered by your actual Discord permissions.

Choosing a server

The dashboard lists only servers where you can act: servers you own, and servers where you hold a role with administrator or moderator permissions. Use the search box to find one by name, or the filter to narrow the list to owner, administrator or moderator.

This deployment currently reports 7 servers and 84 members.

Server settings

Each server has three tabs:

Overview

The server's identity, its owner, when the bot joined, and the effect of the current settings at a glance.

Settings

Prefixes, bot nickname, administrator and moderator roles, ignored channels, disabled commands, embed behaviour, fuzzy matching, delete delay, locale and regional format. Saving writes straight to the running bot.

Third parties

Configuration pages contributed by other cogs, when the bot has them installed.

If a field is disabled, you do not have permission to change it on that server — the dashboard shows the current value rather than hiding the control.

Aliases and custom commands

These live on the server settings page. An alias maps a short name to a full command; a custom command maps a name to one or more responses. Both are stored in the bot's configuration, and both accept the same templates the bot itself supports.

Removing an entry and saving deletes it. There is no separate delete button to hunt for.

Operator admin

Bot owners get an admin area with four sections: bot profile (name, avatar, description), bot settings (prefixes, invite visibility, colours, locale), dashboard settings (title, icon, support server, default theme) and custom pages. It also holds the lock switch, which hides the logged-in dashboard while leaving public pages reachable, and session refresh.

Cog management is separate: it lists repositories and cogs, and can install, update, pin and uninstall them. Changes there affect the running bot immediately.

Command reference

Every command the bot exposes is listed on the commands page, with the current prefixes: !.

This deployment exposes 43 commands across 4 cogs.

Troubleshooting

The dashboard says it is locked

The operator has hidden the logged-in dashboard. Public pages keep working. Ask in the support server.

A server I administer is missing

Your roles on that server do not grant administrator or moderator permissions, or the bot cannot see the server. Check your Discord permissions first, then ask in the support server.

My change did not take effect

Settings apply to the running bot as soon as they save successfully. If nothing changed, the save was rejected — a validation message appears at the top of the page.

The status page says the bot is unavailable

The dashboard has lost its RPC link to the bot. The numbers shown are the last ones received, and the detail column says how old they are. Nothing is lost; it recovers on its own when the bot reconnects.

Self-hosting

The dashboard is free software under the GNU Affero General Public License v3, so you can run your own copy. In outline: install the bot and the webserver in the same environment, expose the bot's RPC port on loopback, point the webserver at it, build the frontend, and put a TLS-terminating reverse proxy in front.

If you self-host, you are the operator of your own deployment: the privacy policy and terms on this page apply to this service, not to yours, and you will need your own.