> ## 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.

# Server setup

> The switchboard where every Vetox feature is turned on or off, plus your server's language and timezone.

Setup is where features are switched on. It is the first place to look when something is not working.

<Warning>
  **Most features are off by default.** Configuring a feature's own page does nothing until its switch is on here. This is by far the most common cause of "I set it up and nothing happened".
</Warning>

## The screen

A **Server Setup** card holding two selectors, then a **Quick Access** grid of module cards grouped into eight categories.

Each module card shows its icon, name, a switch, a status line reading **Enabled** or **Disabled**, and — once enabled — a **Configure** link through to that feature's own page.

<Note>
  The amber **PREMIUM** markers in the sidebar mark a feature as paid — they do not tell you whether *your* server has it.
</Note>

## Language and timezone

| Setting             | Effect                                                       | Default |
| ------------------- | ------------------------------------------------------------ | ------- |
| **Bot Language**    | The language Vetox uses for messages it sends in your server | English |
| **Server Timezone** | The reference for every time-dependent feature               | UTC     |

Both selectors are searchable. Twenty-one languages are available.

<Warning>
  **There is a known bug in the language selector.** Only Arabic and English are mapped correctly. Selecting any of the other nineteen languages saves the correct language code but stores the display name as "English".

  The bot responds in your chosen language, but the stored name is wrong.
</Warning>

<Note>
  Timezone is not cosmetic. It decides when "today" ends for [Streaks](/en/engagement/streaks), when XP leaderboards roll over, and when [Reminders](/en/utility/reminders) and scheduled actions fire.

  Any IANA timezone is accepted. Set it to your community's main timezone, not your own.
</Note>

## The eight categories

<AccordionGroup>
  <Accordion title="General" icon="gear">
    Auto-Roles, Self-Roles, Reminders, Temp Voice.
  </Accordion>

  <Accordion title="Moderation" icon="shield">
    Protection, Anti-Raid, Logging.
  </Accordion>

  <Accordion title="Community" icon="users">
    Leveling, Welcomer, Giveaways, Suggestions, Starboard, Counting, Battle Pass, Streaks.
  </Accordion>

  <Accordion title="Customization" icon="palette">
    Colors.
  </Accordion>

  <Accordion title="Messages" icon="message">
    Auto-Reply, Auto-Interaction.
  </Accordion>

  <Accordion title="AI" icon="sparkles">
    AI Auto-Mod, AI Server Control. Both require **Black**.
  </Accordion>

  <Accordion title="Notifications" icon="bell">
    Twitch, YouTube, Kick, Reddit, Bluesky, Steam, RSS feeds, Podcasts. All require **Basic**.
  </Accordion>

  <Accordion title="Monitoring" icon="chart-simple">
    Server Insights.
  </Accordion>
</AccordionGroup>

## Always-on features

Six features have **no switch** because they cannot be turned off: Commands, Access Control, Auto-Moderation, Moderation Tools, Embed Messages and Dashboard Logs. Their cards render with the switch disabled.

<Note>
  Auto-Moderation being always-on does **not** mean it is filtering anything. Its eight rules still ship disabled — see [Auto-Moderation](/en/moderation/auto-mod).
</Note>

## How a locked card looks

<AccordionGroup>
  <Accordion title="Premium-gated" icon="crown">
    The switch is replaced by an amber lock reading **Premium Required**, and the card is dimmed. Clicking it does not open an upgrade dialog — go to the [pricing page](/en/premium/overview) instead.

    Gated cards: Access Control, Anti-Raid, both AI features, and all eight notification platforms.
  </Accordion>

  <Accordion title="Restricted by Access Control" icon="user-lock">
    The whole card dims and a red **No Access** pill appears. You have dashboard access but not to that section.
  </Accordion>
</AccordionGroup>

<Warning>
  **If you use [Access Control](/en/server-management/dashboard-permissions), every notification card shows "No Access" to restricted administrators** — even when you have granted them those sections. This is a bug in how the notification cards check their permission, not a reflection of your configuration.

  Those administrators can still reach the notification pages from the sidebar.
</Warning>

## A first-load quirk

Seven cards — Protection, Leveling, Welcomer, Self-Roles, Colors, Logging and Server Insights — briefly render as **Enabled** on a server that has never been configured, then flip to Disabled once the real configuration loads.

<Note>
  The Disabled state is the truthful one. Do not assume those features are on because they appeared that way for a moment.
</Note>

## Saving

Language, timezone and every switch share a single save bar. Make all your changes, then save once.

<Warning>
  **The save sends every module's state, not just what you changed.** If two people have the page open, the second save overwrites the first — including toggles the second person never touched.

  Reload before saving if the page has been open a while.
</Warning>

Turning a module on and immediately clicking **Configure** navigates before the save bar has been used. Save first, then configure.

## How a toggle reaches the bot

<Steps>
  <Step title="You save">
    The change is written and the cached configuration is cleared.
  </Step>

  <Step title="The bot is notified">
    A cache-update message goes out to every bot cluster.
  </Step>

  <Step title="The bot picks it up">
    Usually within seconds.
  </Step>
</Steps>

<Warning>
  **The bot notification is fire-and-forget.** If it fails, your save still reports success and the bot keeps the old setting until its own cache expires — up to about 10 minutes.

  If a toggle does not seem to take effect, wait ten minutes before assuming it failed.
</Warning>

## Notifications need two switches

The eight notification platforms are the most common source of confusion, because each needs **both** the platform switch here **and** the subscription configured on its own page — plus **Basic** premium. See [How notifications work](/en/notifications/overview).

## Related

<CardGroup cols={2}>
  <Card title="Commands" icon="terminal" href="/en/server-management/command-management">
    Enable, disable and restrict individual commands.
  </Card>

  <Card title="Access Control" icon="user-lock" href="/en/server-management/dashboard-permissions">
    Control who else can change these settings.
  </Card>
</CardGroup>