> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pup.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your server

> Install and configure pup with deliberate access and a safe first test.

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 **Setup**. Use **Command and logging → Configure** to choose the prefix
   and a reachable private moderation-log channel in General settings.
4. Grant staff only the Pup capabilities they need. Check their Discord permissions
   and both the actor's and bot's role positions. See [permissions](/permissions).
5. Open **Health** to inspect intent readiness, command registration and delivery.
6. 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.

Use **Modules** to find available workspaces and their supported destinations.
The presence of a module entry does not mean every planned feature is available.

The installation default for text commands is `~`. 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.