Skip to main content
By default, anyone with Administrator in Discord can configure everything in your Vetox dashboard. Access Control narrows that.
Requires the Max tier. Below it the page is replaced entirely by pricing — there is no partial or preview view.
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.

​
The problem it solves

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

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

​
What you can grant

Forty sections, grouped the same way as the sidebar: Setup and Commands · the seven moderation pages, which include the three AI Vetox Black pages · the three role pages · the six community features · the three progression features · the four communication features plus the eight notification platforms grouped with them · Support, which holds Tickets and Applications · the three monitoring pages · and the two administration pages.

​
What a section covers

A section grants its page and what that page does, including the few places a page reaches into another:
  • Feature switches follow their feature. Turning a feature on or off — on Setup or on the feature’s own page — needs that feature’s section. A Setup save that would change a switch for a section you do not have is refused as a whole, so reload Setup before saving if someone else may have changed it.
  • Setup also covers the server’s language and timezone.
  • Giveaways includes the giveaway events on its Logs tab. It does not grant Logging, and no other log event is shown there.
  • Self-Roles and Auto-Interaction can pick from your saved embed messages without granting Embed Messages.

​
How access is actually decided

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

Server blacklist

A blacklisted server is refused regardless of everything below.
2

Custom Bot owner

Owning a Custom Bot that serves this server is not a grant on its own. A Custom Bot owner reaches the dashboard only as the server owner or a Discord Administrator, exactly like anyone else.
3

Bot presence

Vetox must actually be in the server.
4

Server owner

The server owner bypasses Restrict Permissions entirely. You cannot restrict the owner.
5

Administrator check

Without Administrator in Discord, access is refused here — Section Access grants sections, it does not grant dashboard access to a non-administrator.
6

Your rules

Only now do Restrict Permissions and Section Access apply.
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. The Section Access dialog warns you when a role you select does not have it.
Overview is always reachable. Even an administrator with zero matching entries keeps Overview, deliberately, so nobody is left staring at an error page.

​
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

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.
If the permission configuration itself cannot be read, administrators get a temporary error until it can be read again, rather than being let through. A backend fault never widens access. The server owner is not affected.

​
A worked example

1

Entry for your moderators

Roles: Moderator. Sections: Auto-Moderation, Moderation Tools, Logging, Anti-Raid.
2

Entry for your community team

Roles: Community Manager. Sections: Leveling, Giveaways, Starboard, Suggestions, Welcomer.
3

Turn on Restrict Permissions

Everyone else, including other administrators, now sees only Overview.
4

Turn on Restrict Protection

Only you can change this page from now on.

Dashboard Watcher

See what your delegated staff actually changed.

Permissions

How command access and dashboard access differ.