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

# Adding Vetox to your server

> Invite Vetox, place its role correctly, and get through first-time setup in a few minutes.

<Steps>
  <Step title="Invite the bot">
    <Card title="Add Vetox to Discord" icon="discord" horizontal href="https://discord.com/oauth2/authorize?client_id=707333425685856316&permissions=8&integration_type=0&scope=bot">
      Opens Discord's authorisation screen.
    </Card>

    You need the **Manage Server** permission in the server you are adding it to. Pick your server from the dropdown and confirm.

    The invite requests **Administrator**. Vetox spans moderation, roles, channels, webhooks and emojis, and a single permission covers all of it without granting them one at a time. If you prefer narrower permissions, edit the Vetox role in **Server Settings → Roles** after inviting — features whose permissions you remove will stop working.
  </Step>

  <Step title="Move the Vetox role up">
    Go to **Server Settings → Roles** and drag **Vetox** near the top of the list.

    Discord will not let any bot act on a member whose highest role sits **above** the bot's own role. If Vetox is below your moderator roles it cannot ban, mute, or assign roles to them — and the failure looks like a bug rather than a permission problem. This is the single most common setup mistake.
  </Step>

  <Step title="Open the dashboard">
    Go to [vetox.io/dashboard](https://vetox.io/dashboard) and sign in with Discord. Your servers appear automatically. Select the one you just added Vetox to.
  </Step>

  <Step title="Turn on the features you want">
    Open the **Setup** page. Every feature is listed there with its own switch, and **most are off by default**. Nothing happens until you enable it here.

    See [Server setup](/en/server-management/setup).
  </Step>

  <Step title="Configure what you enabled">
    Each enabled feature gets its own page in the sidebar. Work through the ones you turned on — every option is documented in this site.
  </Step>
</Steps>

<Warning>
  Placing the Vetox role too low in your role list is the most common cause of "the bot is not working". Discord silently refuses actions against members ranked above the bot.
</Warning>

## What to set up first

You do not need to configure everything. A sensible order for a new server:

<CardGroup cols={2}>
  <Card title="1. Logs" icon="scroll" href="/en/moderation/logs">
    Free, and it records what happened before you need to look it up.
  </Card>

  <Card title="2. Auto-Mod" icon="filter" href="/en/moderation/auto-mod">
    Free. Enable the rules that match your community's problems.
  </Card>

  <Card title="3. Welcomer" icon="door-open" href="/en/utility/welcomer">
    Greet new members so the server feels alive from the first minute.
  </Card>

  <Card title="4. Leveling" icon="chart-line" href="/en/engagement/leveling">
    Rewards activity and gives members a reason to come back.
  </Card>
</CardGroup>

## Verifying it works

Run `/ping` in any channel. If Vetox replies, it is connected and responding.

<AccordionGroup>
  <Accordion title="Commands are not showing up">
    Discord can take a few minutes to sync commands to a newly added bot. Fully quitting and reopening Discord usually forces a refresh.

    Also confirm Vetox has **Use Application Commands** permission in the channel you are testing in.
  </Accordion>

  <Accordion title="Vetox is offline">
    Check [vetox.io/status](https://vetox.io/status). If everything is operational there, remove and re-invite the bot.
  </Accordion>

  <Accordion title="A command replies that I lack permission">
    Vetox checks permissions itself rather than relying on Discord's command visibility, so every command is visible to everyone but only runs for those allowed.

    Server owners and members with Administrator always pass. You can also grant specific roles access per command — see [command management](/en/server-management/command-management).
  </Accordion>
</AccordionGroup>

<Note>
  All Vetox commands are **server-only**. None of them work in direct messages.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Dashboard overview" icon="gauge" href="/en/dashboard">
    How the dashboard is organised and what lives where.
  </Card>

  <Card title="Permissions" icon="user-lock" href="/en/permissions">
    Who can run commands and who can change settings.
  </Card>
</CardGroup>