Skip to main content
  1. Obtain beta access and sign in with your intended Discord account.
  2. Choose your server and complete the installation flow with an account allowed to install applications there. A dashboard login alone does not install the bot.
  3. Open Commands to check the server’s text-command prefix and available commands. The installation default is ~; use the prefix saved for your server.
  4. Open Logs to choose a reachable private moderation-log channel and configure the notifications your staff needs.
  5. Open Staff access to grant each person or role only the Pup permissions they need. Check their Discord permissions and the actor’s and bot’s role positions. See permissions and hierarchy.
  6. Open Connection status to inspect Discord permissions, required intents, command registration, and failed deliveries. Guild Members and Message Content are required for the supported member-state and text-command workflows.
  7. In a disposable server with a consenting test account, try a read-only history command, then record a warning. Open Cases and check the result and delivery.
Use Staff access → Command restrictions to control moderation availability and Warn’s shared prefix/slash policy. See the warning command policy for exclusions and warning-bot replies. Configure each feature from its own page. Start protection rules in the intended mode and verify their scope before turning on enforcement. The dashboard guide explains where to find each task. For server scans, resource inventory, and integrity checks, open Setup tools. For an active incident, use Protection overview, not the setup checks.