A Discord bot that does not ask for Administrator
Thirteen permissions, each for something the bot actually does. You can read the invite link and see exactly what you are granting.
Why Administrator is the easy answer
Administrator is one checkbox that grants everything, for ever, including things the bot has no use for: deleting your server, banning you, changing the owner's roles. It is asked for because listing the real permissions takes work and because a missing one produces a support ticket. The cost of that convenience is that you cannot tell what the bot will do, and neither can anybody auditing it.
What thirteen permissions look like
Manage Roles, because level rewards and automatic roles assign them. Manage Channels, because the server builder creates them. Kick, Ban and Timeout, because moderation does those things. Read and send messages, add reactions, use application commands. No Administrator, no Manage Server, no Manage Webhooks. If a module needs a permission you have not granted, the dashboard says which one rather than failing quietly.
The operator has no access either
Our own account has no automatic access to your server's members, logs or configuration. It passes the same check as anybody else. What we can do across every server is billing: see the subscription and grant, extend or revoke it. If you want hands-on help, you grant it the way you would to any helper, in Discord, and you revoke it there.
On the free tier
Every module runs on the free tier. What differs is where each one stops.
Premium is $9 a month. The free tier needs no payment and is not a trial.
Questions
- Can I check the permissions before inviting?
- Yes. The invite link carries a permissions number, and Discord shows the list on the consent screen before you confirm. Nothing is granted until you press the button.
- What happens if I remove a permission later?
- The module that needed it stops and says so on its page, naming the permission. Nothing else is affected.