Cordary TeamOfficial Cordary account3 min read
Should You Give a Discord Bot Administrator? When It's Fine and When It Isn't
Many Discord bots ask for Administrator. Here's what it really allows, when it's reasonable, when to say no, and how to check what a bot can do in your server.
Updated
In this post
You find a bot you like, click Add App, and Discord shows a long list of permissions with Administrator ticked at the top. Should you leave it on?
The honest answer is "it depends on the bot". This guide explains what Administrator actually does, how to decide, and how to stay in control either way.
What Administrator actually allows
Administrator is not just "a lot of permissions". It's a master switch:
- Every permission at once, including ones Discord adds in future.
- It ignores channel overrides. A private channel that denies everyone else is still open to an Administrator.
- It's server-wide. You can't give Administrator for just one channel.
There's one thing it doesn't change: the role order. Even with Administrator, a bot can only edit, assign or remove roles that sit below its own role in Server Settings → Roles. It can never touch the server owner.
The question to ask: what is the bot for?
Most bots do one or two jobs. A music bot needs to join voice and speak. A welcome bot needs to post in one channel. A leveling bot needs to give out a few roles. None of those need Administrator, and if one asks for it, it's usually because that's the easy option for the developer.
Some bots, though, exist to manage your whole server: build and change channels, roles, permissions and settings. For those, Administrator solves real problems:
- It can reach private channels. Without it, a bot can't edit a channel that's hidden from it, and you get confusing "missing access" errors halfway through a change.
- It can grant permissions. Discord only lets a bot give a role a permission the bot holds itself. A bot that's building your staff roles needs to hold the permissions those roles should have.
So a good rule of thumb:
| Kind of bot | Administrator? |
|---|---|
| Single job (music, polls, welcome, leveling) | No. Give it what the job needs |
| Fun or game bots | No |
| Bots that build or restructure your server | Reasonable, if you trust it |
| A bot you found yesterday with no reviews | No, whatever it does |
How to judge whether you trust a bot
Before giving any bot broad powers:
- Check who makes it. Look for a website, a support server and a privacy policy.
- Read what it does with the access. Does it read messages? Does it take actions on members, like kicking or banning, by itself?
- Look for a review step. For server-management bots, the safest ones show you what they're going to change before they change it.
- See whether changes can be undone. Can you roll back what it did?
If you don't give it Administrator
That's a perfectly good choice. A few things help:
- Untick what you don't want on Discord's add screen. You can change a bot's permissions later in Server Settings → Roles, on the bot's own role.
- Expect a few gaps. If the bot can't see a private channel, it can't manage it. Give its role access to that channel, or accept the limit.
- Leave out member-punishing powers (Kick, Ban, Timeout Members) unless the bot's job is moderation.
Keep any bot's role in the right place
Wherever a bot sits in your role list decides what it can manage:
- Open Server Settings → Roles.
- Drag the bot's role above the roles you want it to manage.
- Keep your Admin and owner-level roles above the bot if you don't want it to touch them.
How to check what a bot can do right now
- Server Settings → Roles → the bot's role shows its permissions.
- View Server As Role (on that role's menu) shows you exactly which channels it can see.
- Server Settings → Audit Log shows what it has changed, and when.
Review these every few months, and remove bots you no longer use. Their roles and permissions linger otherwise.
What Cordary does
Cordary is a server-management tool, so we recommend Administrator, and say so openly when you add it. You can also choose its standard set instead, which leaves out Administrator and the power to kick, ban or time out anyone.
Either way, Cordary never changes your server until you've reviewed the plan and pressed Apply, it never reads your members' messages, and you can roll back what it applied. For more on permissions in general, see Discord roles and permissions explained.
More in #guides
How to Use Cordary's Checkup: Findings, Fix This and Scheduled Checkups
A walk through Cordary's Checkup tab. Read the findings, fix one with a change you review, dismiss what's fine, run the full checkup, and set up scheduled checkups with an optional Discord post.
How to Set Up Discord Onboarding and the Server Guide (2026)
A step-by-step guide to Discord Onboarding: default channels, questions that give roles and channels, the Server Guide, and the mistakes that stop it from switching on.