Skip to content
GuardBot
Open dashboard

Support

Dashboard help and data controls

The dashboard is currently a development preview. These steps cover the supported self-service recovery and removal paths without requiring a permanent cloud session.

Connect or reconnect

  1. Sign in with Discord and choose a server where you have Manage Server permission.
  2. Opening a paired server automatically rings its data-free wake doorbell. If that first attempt fails, select Connect to retry.
  3. If the bot cannot receive the wake, run /dashboard connect <code> in that Discord server using the one-time code shown by the dashboard.

The management relay closes after browser inactivity and a short reconnection grace period. Reconnecting later creates a new short-lived management session.

Check the installation

Run /dashboard status for a private diagnostic covering pairing, the wake doorbell, management relay, and protocol version. Confirm GuardBot is running and its license validation is healthy before pairing again.

If a dashboard request fails, copy the exact Support reference shown with the error. It identifies only that short-lived relay request and contains no configuration, message, statistic, or credential. Send the reference together with the private status output; do not send pairing codes, relay tickets, cookies, or screenshots containing private server data.

Log out or remove a pairing

Log out from the dashboard user menu to delete the browser sign-in cookie. To revoke website management for a server, use the dashboard's unpair action or run/dashboard unpair. Unpairing removes the cloud routing relationship and revokes the installation's local dashboard authority. To move a server to another GuardBot installation, unpair the current installation before redeeming the new bot's pairing code; the dashboard will not silently replace one installation with another.

Remove GuardBot data

Configuration, messages, statistics, and moderation records live in the operator's local bot database, not on the website. The installation operator controls retention, backup, and deletion of that database. Unpair first, stop GuardBot, then follow the installation's local removal procedure. Review the privacy page for the exact cloud data boundary.