- Obtain beta access and sign in with your intended Discord account.
- 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.
- Open Setup. Use Command and logging → Configure to choose the prefix and a reachable private moderation-log channel in General settings.
- Grant staff only the Pup capabilities they need. Check their Discord permissions and both the actor’s and bot’s role positions. See permissions.
- Open Health to inspect intent readiness, command registration and delivery.
- Test a read-only history command, then a bounded warning in a disposable server with a consenting test account. Confirm the case and its delivery state.
~. An installation can use a
different configured prefix; changing a deployment default does not rewrite an
existing server’s saved prefix. Use your server’s configured prefix in examples.
The bot needs the Guild Members and Message Content intents for the supported
member-state and prefix workflows. A missing intent or command-registration
problem appears in Health. Do not grant Administrator as a substitute for
understanding a missing permission.
Optional history context menus are off by default. Enable them deliberately in
command controls and verify registration before relying on them.