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

# Access Control

> Delegate dashboard access to specific roles and people, section by section, without granting Manage Server. Max tier.

By default, anyone with **Manage Server** in Discord can configure everything in your Vetox dashboard. Access Control narrows that.

<Info>
  Requires the **Max** tier. Below it the page is replaced entirely by pricing — there is no partial or preview view.
</Info>

<Warning>
  **The sidebar shows this entry from Basic, but the page requires Max.** A Basic-tier administrator can click it and land on a paywall. That is a gating inconsistency, not a lapsed subscription.
</Warning>

## The problem it solves

Manage Server is a blunt instrument. Giving it to a moderator so they can tune Auto-Moderation also lets them edit your server, and gives them every other Vetox page.

## The two switches

Both save **immediately** — there is no save bar on this page.

| Switch                   | Default | Effect                                                                                                            |
| ------------------------ | ------- | ----------------------------------------------------------------------------------------------------------------- |
| **Restrict Permissions** | Off     | Only roles and people listed in Section Access can use the dashboard. Off means any administrator has full access |
| **Restrict Protection**  | Off     | Limits this page itself to the server owner, so nobody can grant themselves more access                           |

<Warning>
  Turning on **Restrict Permissions** with no Section Access entries locks every non-owner administrator out of everything except Overview.

  Add your entries first, then enable the restriction. The server owner always retains access.
</Warning>

## Section Access

Up to **25 entries**. Each combines roles, individual users, and the sections they unlock.

An entry must name at least one role **or** at least one user — an entry with neither is rejected.

<Tip>
  Prefer roles over individuals. A role-based entry keeps working when staff change; an individual entry has to be edited every time someone joins or leaves.
</Tip>

### What you can grant

Thirty-four sections, grouped the same way as the sidebar: Setup and Commands · AI · the four moderation pages · the eight community features · the four customization features · the four communication features · the eight notification platforms · Tickets · Applications · and the four administration pages.

## How access is actually decided

Understanding the order matters, because several things bypass your rules entirely.

<Steps>
  <Step title="Server blacklist">
    A blacklisted server is refused regardless of everything below.
  </Step>

  <Step title="Custom Bot owner">
    If you own a Custom Bot serving this server, you get **full access with no Discord permission check at all**.
  </Step>

  <Step title="Bot presence">
    Vetox must actually be in the server.
  </Step>

  <Step title="Server owner">
    The server owner bypasses Restrict Permissions **entirely**. You cannot restrict the owner.
  </Step>

  <Step title="Administrator check">
    Without Administrator in Discord, access is refused here — Section Access grants sections, it does not grant dashboard access to a non-administrator.
  </Step>

  <Step title="Your rules">
    Only now do Restrict Permissions and Section Access apply.
  </Step>
</Steps>

<Warning>
  **Section Access cannot grant dashboard access to someone who is not already a Discord administrator.** It only narrows what an administrator can reach. To give a non-administrator access, they need Administrator in Discord first.
</Warning>

<Note>
  **Overview is always reachable.** Even an administrator with zero matching entries keeps Overview, deliberately, so nobody is left staring at an error page.
</Note>

## Restrict Protection

When on, only the server owner can open this page — unless an entry explicitly grants the Access Control section to someone, which overrides it.

## Two things worth knowing

<AccordionGroup>
  <Accordion title="Hidden sidebar entries are cosmetic" icon="eye-slash">
    Sections a user cannot reach are hidden from their sidebar, but the real enforcement happens server-side on every request. Someone typing the URL directly is still refused.
  </Accordion>

  <Accordion title="It fails open on its own errors" icon="triangle-exclamation">
    If the permission configuration itself cannot be read, access falls through to unrestricted rather than locking everyone out. The blacklist and Administrator checks still apply.

    This is a deliberate availability choice, but it means a backend fault temporarily widens access rather than narrowing it.
  </Accordion>
</AccordionGroup>

## A worked example

<Steps>
  <Step title="Entry for your moderators">
    Roles: `Moderator`. Sections: Auto-Moderation, Moderation Tools, Logging, Anti-Raid.
  </Step>

  <Step title="Entry for your community team">
    Roles: `Community Manager`. Sections: Leveling, Giveaways, Starboard, Suggestions, Welcomer.
  </Step>

  <Step title="Turn on Restrict Permissions">
    Everyone else, including other administrators, now sees only Overview.
  </Step>

  <Step title="Turn on Restrict Protection">
    Only you can change this page from now on.
  </Step>
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="Dashboard Watcher" icon="desktop" href="/en/server-management/dashboard-watcher">
    See what your delegated staff actually changed.
  </Card>

  <Card title="Permissions" icon="user-lock" href="/en/permissions">
    How command access and dashboard access differ.
  </Card>
</CardGroup>