Running it

How to make a Telegram bot an admin, and which rights to grant

By the Botable team

Promote a bot through group info, Administrators, Add Admin, then enable individual permissions. Grant only what its features require — Telegram rejects unpermitted actions silently, which is why a bot that does nothing usually has a permissions problem.

The short version

Telegram admin permissions for bots are granular and fail quietly, which is a combination that produces a lot of wasted debugging. A bot promoted to administrator does not receive a general capability; it receives exactly the individual rights you toggle — delete messages, restrict members, ban users, pin messages, invite users, manage the chat, and so on. An action attempted without the matching right is refused by Telegram, and the refusal surfaces as an API error your bot may not display anywhere a user can see. From the group's perspective nothing happened. The right approach is to grant the minimum a feature needs and to verify by reading the bot's entry in the administrator list rather than by assuming the promotion covered everything. Admin status has a second effect worth knowing: an admin bot receives all group messages regardless of its privacy-mode setting.

Step by step

How do you promote the bot?

Open group info, go to Administrators, choose Add Admin, and select the bot from the member list. The bot must already be a member — you cannot promote something that has not joined. You then get the permission toggles.

Which permissions map to which features?

Delete messages for spam filtering and cleanup; restrict members for muting and captcha gating; ban users for enforcement; pin messages for announcements; invite users for generating invite links. Enable each only where a feature needs it, and leave everything else off.

Why do actions fail with no error?

Telegram rejects the API call, but nothing in the chat says so. Unless your bot logs and surfaces the failure, the symptom is that a command produced no effect. If a moderation feature does nothing at all, check the permission before you read a line of code.

What changes about message visibility?

An administrator bot receives every message in the group regardless of privacy mode. That is convenient for moderation and is also a reason not to promote a bot that does not need it — promotion silently widens what it can read.

What catches people out

  • The bot must be a member before it can be promoted
  • Permission failures are silent; "nothing happened" is the symptom, not a null result
  • Promoting to admin bypasses privacy mode, so an admin bot sees everything whether or not you intended it

Questions

Can a bot promote other admins?

Only if it has the right to add administrators, and it can only grant rights it holds itself. This is deliberate — a bot cannot escalate beyond its own permissions.

Can it be admin in a channel?

Yes, and in a channel it must be, since bots cannot be ordinary channel members. Posting to a channel requires the post-messages right.

Want a bot that does this?

Describe it in plain language and Botable writes the code, gives the bot its own database, deploys it and keeps it running. Everything on this page is handled for you — the token, the webhook, the storage, the hosting.

Build a bot

Keep reading

Bots that use this

All twenty-five guides