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

# Getting Started

> Invite Warden, connect ER:LC, and enable your first modules.

This guide walks you from a fresh invite to a working setup. Most servers finish in under fifteen minutes if you already have an ER:LC API key.

## Before you begin

<Check>Discord **Server Administrator** permission</Check>
<Check>Warden [invited](https://discord.com/oauth2/authorize?client_id=1506630562113130657) with the permissions the invite requests</Check>
<Check>ER:LC **API key** ready if you want moderation, logs, or sessions — see [ER:LC Integration](/configuration/erlc-integration)</Check>

## Quick setup

<Steps>
  <Step title="Invite and verify the bot">
    After inviting Warden, run **`/ping`** in any channel. A response confirms the bot is online and can read messages there.
  </Step>

  <Step title="Assign staff tiers">
    Open **`/config`** → **Permissions** and set your **Staff**, **Admin**, and **Management** roles. Nearly every command checks these first. Details: [Permissions](/modules/permissions).
  </Step>

  <Step title="Link ER:LC (optional but common)">
    Run **`/erlc link`** with your private server API key. Skip this step only if you are using Discord-only modules like verification or applications.
  </Step>

  <Step title="Enable modules one at a time">
    In **`/config`**, pick a module from the dropdown, flip it to **Enabled**, and fill in the channels and roles it asks for.
  </Step>

  <Step title="Smoke-test">
    Try one command from each enabled module — for example **`/verify`**, **`/shift manage`**, or **`/punish`** — using the [command reference](/configuration/commands).
  </Step>
</Steps>

## Suggested order for new servers

Not every server needs every module. This order avoids rework:

| Order | What                                                 | Why                                                       |
| ----- | ---------------------------------------------------- | --------------------------------------------------------- |
| 1     | [Permissions](/modules/permissions)                  | Unlocks the correct command access for your team          |
| 2     | [ER:LC Integration](/configuration/erlc-integration) | Required before moderation, logs, or sessions             |
| 3     | [Verification](/modules/verification)                | Gate access before opening staff tools to everyone        |
| 4     | Everything else                                      | Pick modules based on how your staff team runs day-to-day |

## Working with the config panel

All Warden settings live in Discord. Run **`/config`** or **`w!config`** anytime to reopen the panel.

<AccordionGroup>
  <Accordion title="How settings are saved">
    Most toggles and dropdowns save as soon as you interact with them. Flows that involve writing messages — shift types, log templates, embeds — show an explicit **Save** button. Click it before leaving the screen.
  </Accordion>

  <Accordion title="Who can open /config">
    Only members with **Server Administrator** can run the config command. Delegate day-to-day work through Staff/Admin/Management roles instead of sharing admin access.
  </Accordion>

  <Accordion title="Where to go next">
    Deep-dive into [Configuration](/modules/configuration) for a module-by-module overview, or jump straight to the module page you just enabled from the sidebar.
  </Accordion>
</AccordionGroup>