Discord

Discord bot permissions checklist for a Kingshot alliance server

What to check before you add a bot, which permissions to give it, and the posts to tell your members.

A bot on your server can read messages, post, and sometimes remove people. Give it the least it needs. Below: a checklist for before, during and after, a table of the common permissions, and two posts to copy. The one rule: refuse any bot or site that asks for a game login. A server bot never needs it.

Copy-ready
Before you invite it (staff checklist)
[ ] I know who runs the bot and where it comes from. [ ] I read its own page or help text: what it does and what it stores. [ ] It does not ask for a game login, a password or a login code, anywhere. [ ] I know which features I want. I will turn off the rest. [ ] A second admin knows I am adding it. [ ] I wrote the bot, its owner and its purpose in the staff notes.

Takes two minutes. If you cannot answer the first line, do not add the bot.

On the invite screen (permissions checklist)
[ ] I read the full list of permissions the bot asks for. [ ] Each permission matches a feature I want. [ ] I did not give Administrator. If it insists on Administrator, I said no. [ ] The bot has its own role, placed below my admin roles. [ ] I limited the bot to the channels it needs, using channel permissions. [ ] It cannot ping everyone unless I chose that.

Read the table below if a permission name is new to you.

After you add it (first-week checklist)
[ ] I tested the bot in a private staff channel first. [ ] I checked what it posts, and when. [ ] I told members the bot exists and what it does. [ ] I said plainly that it will never ask for a game login. [ ] I will review it each season and remove it if we no longer use it.

A bot nobody uses is still a bot with access. Remove it.

Post to members: a new bot is here
NEW BOT ON THE SERVER We added [BOT NAME]. It [ONE LINE: what it does, for example posts event reminders in #events-and-kvk]. It only works in [CHANNELS]. It will never ask for your game login, password or login codes. Nobody on this server will either. If any bot, site or person asks, do not answer. Show an officer. Questions: ask [OFFICER].

Post it in announcements. Say the login line every time you add a bot.

Staff alert: something asked for a login
STAFF ALERT A bot, site or member asked for a game login or login code: [WHAT, WHERE, WHEN]. Do not answer it. [ ] Remove the bot or timeout the account. [ ] Warn the server with no names. [ ] If a member already gave a login out, send them to the Account Safety guide: kingshotpro.com/guides/kingshot-account-safety.html

Keep it short. Nobody is accused in public; you act first and explain after.

Bot record (one line per bot, for the staff notes)
Bot: [NAME] Owner or maker: [WHO] Added by: [OFFICER] on [DATE] Purpose: [ONE LINE] Permissions given: [LIST] Channels: [LIST] Review on: [DATE]

Paste one block per bot in a private staff channel. It lets the next officer see what is installed and why.

Permissions in plain words

PermissionWhat it lets a bot doGive it when
View Channel, Send MessagesSee a channel and post in it.A reminder or announcement bot. Limit it to its own channels.
Manage MessagesDelete other people's messages.A moderation bot that clears spam.
Manage RolesCreate and edit roles. A bot can only handle roles below its own highest role.A bot that hands out roles. Keep its role low.
Moderate MembersTime members out so they cannot post.A moderation bot with a clear rule list.
Kick Members, Ban MembersRemove people from the server.Rarely. A mistake here removes real members.
Mention EveryonePing all members at once.Only if your reminders need it. Pings annoy people.
Manage ServerEdit the server itself.Almost never.
AdministratorAll permissions, and it ignores channel permission limits.Almost never. It removes every limit you set.

Descriptions follow Discord's own developer documentation, read 2026-11-15. Names in your app may differ slightly. Check the list on the invite screen.

Before you remove anyone

  • Look at the bot's role first. A bot can only act on members whose highest role is lower than its own.
  • Test on a spare account or a staff-only channel. Do not test on the whole server.
  • One owner per bot. Name the officer who answers for it.

Questions people ask

Should I give a Discord bot Administrator?
Almost never. Administrator gives a bot every permission and ignores channel limits. Give the permissions for the features you want and nothing more.

Does a Kingshot bot need my game login?
The Terms say not to share your password or login codes, and sharing account information lets the publisher end the account without refund. A server bot works inside Discord and has no reason to ask for it. Refuse any that does.

Can I trust a bot because other alliances use it?
Not by that alone. Check who runs it, read what it says it stores, and give it only the permissions you checked. Other servers using it does not tell you what it can do on yours.

Does this page cover tools that play the game for you?
No. This page is about bots that work inside Discord. Anything that plays the game for you is outside this page, and we do not describe how to use one.

How do I remove a bot I no longer use?
Remove it from the server, then delete its role. Tell the members so nobody wonders where it went.

Sources

The login rule: the Century Games Terms of Service, as read by our account safety page. Permission descriptions: Discord developer documentation, Permissions, read 2026-11-15. The checklists are our own advice, not the publisher's or Discord's.