Telegram Admin Rights: Owner, Admin and Every Permission

Somebody on your team needs to pin an announcement while you are asleep, so you open the member list, tap their name and start ticking boxes. Fourteen of them, with names that all sound roughly the same. One of those boxes hands over your channel. The rest do not, and nothing on the screen tells you which is which.

Telegram's admin model is more precise than it looks. Underneath the toggles is a fixed list of rights, each one documented, each one covering exactly one action and nothing more. Read that list once and the screen stops being a wall of switches. It becomes a set of decisions, most of them small and reversible, and one of them not.

This article goes through every permission Telegram defines, what each one actually exposes, which ones apply to a channel and which to a group, why a promotion sometimes fails with no useful message, and what transferring ownership really requires. Every claim about the platform was pulled from Telegram's own API documentation on 8 August 2026 rather than remembered, and where Telegram leaves something undefined, that is said plainly instead of filled in with a guess.

Owner, Admin and Member Are Three Different Things

The owner is a single account, not a role

A channel or supergroup has exactly one owner, the account that created it or the account it was handed to. Ownership is not a permission you can tick. It is a property of the chat, held by one user, and it carries everything: every right, plus the two things no right grants, which are deleting the chat and transferring it. When a call tries to touch an owner's rights from any account other than the owner, Telegram rejects it outright with an error that says exactly that, so this is a wall rather than a convention.

An admin is a member with a list attached

Everybody else who manages the chat is an admin, and an admin is simply a member carrying a list of enabled rights. Two admins in the same channel can have nothing in common except the label. One might only be able to pin, another only to delete, and the interface shows them both in the same section with the same badge. This is why "make them an admin" is a meaningless instruction on Telegram. The useful instruction names the rights.

It also explains a habit worth breaking. Most people promote by switching everything on, because the screen is long and the person is trusted, and trust feels like the thing being measured. It is not. The list is a description of a job, and giving somebody every right says only that nobody worked out what the job was. A moderator who removes spam needs two rights. A writer who publishes needs one. Filling the screen adds nothing they will use and quietly adds several things you would rather they could not do.

Ordinary members are governed by a separate list

Members are not admins with everything switched off. Restrictions on ordinary members come from a different structure entirely, applied either to the whole group or to one person, covering things like sending media or embedding links. Admin rights say what somebody may do beyond normal. Member restrictions say what everybody may not. Mixing the two is the most common source of "I gave them permission and it still does not work", because the block was never on the admin side at all. If a group is losing people to restrictions nobody set on purpose, that pattern is worth reading separately in our note on lifting a spam restriction.

The Content Rights, and What Each One Reaches

Post messages, which only exists in channels

The post right allows an admin to publish in the channel. It has no meaning in a group, because in a group ordinary members already write and there is nothing to grant. That asymmetry runs through the whole list and explains why the toggle screen looks different depending on where you opened it. Handing somebody the post right is handing them your voice, since a channel post carries the channel's name rather than theirs unless you have deliberately set things up otherwise.

Edit messages, which reaches other people's posts

The edit right is documented as allowing an admin to edit messages from other admins in the channel, and that phrase is the part people skip. It is not permission to edit their own work, which everybody already has. It is permission to reach into anything already published and change it, including posts made by you. A channel with several writers and loose edit rights has no reliable history, because a post can be quietly rewritten after it has been read, forwarded and quoted.

Delete messages, with the same reach

Delete carries the same wording and the same reach, covering messages from other admins rather than only the holder's own. In a group this is the right moderation actually runs on, and it is the first thing a moderation bot asks for. When a moderation bot in a group has stopped removing anything, the missing right is nearly always this one rather than the ban right, a diagnostic that both Rose and Combot surface in their own setup checks.

Change info, which is smaller than it sounds

Change info allows an admin to modify the description of the channel or supergroup, and in the clients it also governs the title and the photo. It is the appearance right. It is a reasonable one to hand out and an easy one to notice being misused, since any change is visible to everybody immediately and lands in the action log described further down.

The Rights That Decide Who Is in the Room

Invite users

The invite right allows an admin to bring users into the channel or supergroup, and in the clients it also governs creating and revoking invite links. Two things follow from that. The first is that anybody holding it can open a door you did not open. The second is quieter and more useful: links are traceable to the admin who made them, so a link that starts pulling in junk can be revoked on its own without disturbing anything else. Growth that arrives through one link and never converts is usually a targeting problem rather than a link problem, and the shapes to look for are in our piece on spotting a botted channel.

Ban users

The ban right allows an admin to remove users from the channel or supergroup. In a supergroup the same right also covers partial restrictions, which is how a moderator mutes somebody for an hour instead of removing them outright. This is the right most worth being careful with in a large group, because a removal is instant, visible to the person it happened to, and hard to undo in the sense that matters, which is that they now know. A moderator who is quick with this right will cost you members you would have kept.

Pin messages

Pin allows an admin to pin messages in the channel or supergroup. It looks trivial and it is the one small right worth handing out early, because a pinned message is the only part of a chat that new arrivals reliably read. The cost of a bad pin is low and the benefit of a timely one is real, particularly during a launch when the same question is arriving forty times an hour.

The Structural Rights, Which Change How the Chat Works

Manage topics

The topics right allows an admin to create, delete or modify forum topics. It only means anything in a group with topics turned on, and it is a structural right rather than a moderating one. Somebody holding it can reshape the room, merge conversations by deleting a topic, or hide the general area. Before handing it out it is worth knowing what topics do and do not separate, which we went through in our article on splitting a group that got too big.

Manage video chats

This right allows an admin to create and administer video chats and livestreams. In a large group it is the difference between anybody being able to start a call at three in the morning and only your team being able to. It also decides who can end a running call, which matters more than starting one, since a call left open in a public group fills up with people who are not there for the discussion.

Post, edit and delete stories

Stories arrive as three separate rights rather than one. Posting allows an admin to publish stories as the channel. Editing allows them to change stories posted by other admins, and deleting allows them to remove those stories. Splitting the three is deliberate and genuinely useful, because a contractor can be given posting without being able to erase the archive behind them on the way out. How many stories a channel may post at all is a different mechanic entirely, tied to boost level, and covered in our note on what boosts unlock.

There is a second reason to split them that only shows up later. Stories are the part of a channel most likely to be produced by somebody outside your team, on a phone, in a hurry, and the archive they leave behind is what the channel looks like to a visitor six months on. Posting without deleting means the record of that work survives the working relationship, which is the ordinary case rather than the paranoid one. If the content itself is being lifted and republished elsewhere, that is a different problem with a different answer, and we set it out in our guide to moving channel content properly.

Manage direct messages

This is one of the newer entries and worth knowing precisely because most guides predate it. The documentation describes it as allowing an admin to manage the direct messages area attached to a channel and to decline suggested posts. If your channel accepts messages or submissions from readers, this is the right that puts somebody else on that queue without giving them anything else at all, which makes it one of the cleanest single-purpose rights on the whole list.

The One Right That Is Not Like the Others

Add new admins is the only recursive permission

Every right on the list governs an action inside the chat except one. The add admins right is documented as allowing an admin to add other admins with the same or more limited permissions, and that single sentence is the whole risk. It is recursive. Somebody holding it can hand out everything they hold, to anybody, without asking you, and the people they create can be given the same right in turn. Thirteen of the toggles delegate a task. This one delegates the ability to delegate.

Why the ceiling does not save you

Telegram does put a ceiling on it, in that an admin cannot grant more than they hold. That sounds like a safety net and it is a thin one. If you gave somebody the full set because it was easier than thinking about it, the ceiling is the full set, and one careless promotion by them reproduces your entire configuration on an account you have never seen. The ceiling protects the chat from escalation. It does nothing about duplication, which is the failure that actually happens.

There is a cheap habit that removes most of this risk without any tooling. Keep the add admins right on the owner account and nowhere else, and when somebody genuinely needs to bring people in, have them ask. It sounds like a bottleneck and it is not, because in a normal month the request arrives once or twice. What it buys is that the admin list only ever grows through a decision somebody made deliberately, which means the list stays short enough to read, and a list short enough to read is one you will actually check.

Anonymous Admins, and What They Hide

What the flag does

Anonymity is its own right rather than a setting. Telegram describes it as a special admin right available to supergroup admins that hides the holder from the member list and posts their messages under the group's name instead of their own. It is not a cosmetic badge. Somebody with it speaks as the group, and a member reading the conversation has no way to tell which of your moderators is talking.

When it earns its place

It earns its place in two situations and looks strange everywhere else. The first is a moderation team that receives abuse, where speaking as the group rather than as a named person removes the target. The second is a group where you want rulings to read as decisions rather than opinions. Outside those, anonymity mostly costs you the thing that makes a moderator effective, which is being a recognisable person that regulars trust. The trade is real in both directions, so it is worth making on purpose rather than because the toggle was there.

Custom Titles and Member Tags

A title is a label, not a permission

An admin can be given a custom title that appears beside their name in place of the default one. It changes nothing about what they can do. This matters more than it sounds, because a title reading Owner on an account that holds three rights is exactly the kind of thing that reassures the wrong person. Telegram does restrict the field itself: a rank containing emoji is rejected, and so is one that fails validation, which is a small hint that the field is treated as an identity label rather than decoration.

Managing tags is a separate right again

Changing the tag on any member is governed by its own right rather than folded into change info. That separation is deliberate. Editing the labels other people wear is closer to editing the org chart than to editing the description, and it now takes a specific grant to do it.

Which Rights Exist Where

Channels get the publishing rights

Post messages, edit messages and the three story rights belong to broadcast channels, because they describe publishing. In a supergroup they have nothing to act on. The direct messages right sits here too, since it manages an area attached to a channel rather than a group conversation.

Groups get the room rights

Topics, anonymity and the restriction half of the ban right are supergroup ideas. A channel has no room to shape, no member list to disappear from in the same sense and nobody to mute. Handing somebody a group-shaped right in a channel simply has no effect, which is one reason a promotion can look successful and change nothing.

A basic group has none of this

All of it assumes a supergroup or a channel. A small basic group has a much cruder model, and it converts to a supergroup automatically once it grows or once certain features are switched on. If a group is at that boundary, the conversion behaviour and the limits around it are covered in our piece on adding members and the limits that apply.

Bots as Admins

A bot holds the same list

A bot promoted in a group or channel receives rights from the same list, with the same names and the same meanings. There is no separate bot permission model. This is why a moderation bot with no delete right sits there quietly doing nothing, and why the fix is usually one toggle rather than a reinstall.

The one thing a bot cannot do

Bots cannot edit admin privileges. The documentation is blunt about it, and the call fails with an error saying exactly that. Any tool advertising that it will manage your admin list for you is either working through a user account rather than a bot, or it is not doing what it says. That distinction matters when picking tools, and it is one of the reasons we keep bot management and account management as separate things in our own bot panel.

Give a bot the least it needs

A bot is an account somebody else wrote, running code you cannot read, holding whatever you gave it. The sensible posture is the same one you would take with a contractor: grant the single right the job needs, watch the action log for a week, and add more only when something visibly fails. Most bots ask for delete and ban and genuinely need both. Almost none of them need the right to add admins, and any that asks for it deserves a hard look, since the documentation is clear that a bot cannot use it anyway. The same restraint applies to the scripts people run against their own groups, a subject we covered in our roundup of open source Telegram scripts.

When a Promotion Fails and the Screen Says Nothing Useful

You were just made an admin yourself

Telegram returns a specific refusal for an admin who was elected very recently and immediately tries to add or modify other admins. The documented message says you were just elected admin and cannot add or modify other admins yet. There is no setting for it and nothing is broken. It is a deliberate brake on a chain of instant promotions, and it clears on its own.

Privacy settings on the other side

A promotion can fail because of the other person's privacy settings rather than anything in your chat. There are separate refusals for that, for an account that was deleted, for an account that blocked you and for one that was previously removed from the group. All of them look identical from the outside, which is a failed tap, and all of them are on their side rather than yours.

Ceilings you did not know you had

There are refusals for too many admins in one chat, too many bots in one chat, and for a person who already belongs to too many channels and groups. That last one is common with accounts used for outreach, since the per-account limit on joined chats is real and low enough to hit. If you run several accounts and keep bumping into it, the mechanics are in our note on managing multiple Telegram accounts.

Transferring Ownership, and What It Actually Costs

Four conditions, all documented

Handing a channel to somebody else is the only irreversible thing on this page, and Telegram guards it with conditions that are published rather than folklore. Two factor authentication must be enabled on your account. The password must not have been changed in the last twenty four hours. The session you are using must itself be more than twenty four hours old. And the person receiving it must be a mutual contact. Each of those has its own refusal message, and the two time based ones even tell you how many seconds remain.

Why the two day rule exists

The pattern behind those conditions is easy to read once they are listed together. Somebody who has just taken over an account cannot immediately give away the assets on it, because a fresh session and a fresh password both block the transfer for a day. It is not an inconvenience. It is the window in which a real owner notices and takes the account back, and it is the single most useful piece of account security Telegram builds into the product.

Plan the transfer before you need it

The practical consequence is that ownership transfer cannot be done in a hurry. If a handover is coming, turn on two factor authentication now, leave the password alone, and make sure the incoming owner is already a mutual contact. Doing that in advance turns an urgent problem into a two minute task. Leaving it means discovering the twenty four hour rules at the exact moment you cannot afford them.

One more detail catches people at the last step. If the channel is public and the account receiving it already administers a large number of public channels, the transfer is refused on that ground alone, and the fix is on their side rather than yours. It is worth asking the incoming owner to check their own list before the day of the handover, because the refusal arrives with no warning and reads like a fault in your channel when it is nothing of the kind.

The Two Things No Right Grants

Deleting the chat

No permission on the list lets an admin delete the channel or group. That stays with the owner. It is worth saying out loud to anybody nervous about handing out rights, because the worst case people imagine is usually this one, and it is not on the table.

Handing it to somebody else

Transfer is also owner only, and the refusal for attempting it from a non owner account is explicit. Between them these two exclusions define the real shape of the risk. An admin with everything can embarrass you, empty the room and rewrite the archive. An admin with everything still cannot take the room.

The Action Log Nobody Opens

Every administrative action is recorded

Supergroups and channels keep a log of administrative actions, visible to admins, covering deletions, restrictions, promotions, pinned messages and information changes. It is the answer to almost every argument about who did what, and in most groups it is opened for the first time only after something has gone badly wrong. Reading it once a week while nothing is wrong is how you learn what your own team actually does with the rights you handed out, and it is the cheapest audit available.

What it is good for, and what it is not

The log answers who and when, reliably, and that is usually the whole argument. What it does not do is tell you why, and it does not follow anybody outside this chat. An account acting oddly in one group is often acting oddly in several, and the log in front of you only knows about the room it belongs to. If the pattern looks wider than one chat, the thing to check is the account rather than the group, and the signals worth reading are the same ones covered in our note on reading engagement honestly.

When One Person Holds Several Accounts

The permission model does not stretch across accounts

Everything above governs one chat at a time. It says nothing about who on your side may operate which account, because Telegram has no concept of your organisation. Two moderators sharing one login are one identity to Telegram, and the action log will honestly report that a single account did everything, which is exactly the confusion admin rights exist to prevent inside the chat.

Where a panel sits next to it

That gap is a real one and it is where a management layer belongs, not as a replacement for Telegram's rights but beside them. Our Account Manager keeps several accounts in one place with seats and roles on our side, so who on your team may act through which account is a separate question from what that account may do inside a given chat. Both answers are needed and neither substitutes for the other. The same separation matters when a team runs outreach from several accounts through Mass DMs or grows a group with Member Adder, since the account doing the work still needs the right rights in the chat it is working on.

What the Buttons Say, and What They Are Underneath

The interface groups rights, the platform does not

The toggle screen is a friendly arrangement of an unfriendly list. Clients collapse several underlying rights into one switch where that reads better, split others across screens, and leave out anything that does not apply to the chat you happened to open. None of that changes what is stored. Underneath there is one flat set of flags, and a right either is or is not set on that account.

This is worth knowing for one practical reason. When you read a guide, a support answer or an angry forum post, the names will not match your screen, and the temptation is to assume your client is out of date or the feature is missing. Usually the feature is there under a different label, or it is genuinely absent because you are in a channel and the right only exists in groups. Checking which of those it is takes a moment and saves an afternoon.

Why two people see different switches

An admin editing another admin only sees the rights they themselves hold, because they cannot grant more than they have. So a moderator setting up a new moderator will see a shorter list than the owner does, with no explanation on screen for the difference. This causes a specific and very common argument, where one person insists a toggle does not exist and another insists it does, and both are looking at the same chat and telling the truth. The answer is always that the shorter list belongs to the person with fewer rights.

Taking Rights Back

Demoting is immediate and quiet

Removing an admin's rights takes effect at once and the person is not notified with any kind of announcement. Their badge disappears, their toggles stop working, and the demotion lands in the action log. Anything they already did stays done: posts they published remain published, members they removed remain removed, and messages they deleted are not restored. Demotion closes the door, it does not undo the evening.

What can be undone afterwards is narrower than people expect. Invite links created by that admin can be revoked individually, which is the single most useful cleanup step after a departure, because a link left live is the one thing that keeps working when the account no longer does. Anything published under the channel's name is now the channel's, and correcting it is an editing job rather than an access job.

The account you forgot about

The admin list of a two year old channel is usually longer than its owner expects, and the extra entries are rarely malicious. They are the contractor from a launch, the friend who helped for a weekend, the second account somebody made and stopped using. Each of them still holds whatever it was given, and an abandoned account is worth more to somebody else than an active one, because nobody is watching it. Reading the list once a quarter and removing everything that no longer has a job takes five minutes and closes the most likely way a channel is lost. If a channel has already been copied by somebody who should not have had access, the recovery path is a different subject and we covered it in our piece on how channel cloning actually works.

Frequently Asked Questions

How many admins can a Telegram channel have

Telegram does not publish the number, and there is a specific refusal for exceeding it, so the honest answer is that a limit exists and you will meet it as an error rather than as documentation. In practice it is high enough that a normal team never approaches it, and hitting it usually means admin rights were handed out as a courtesy rather than for a job.

Can an admin delete my channel

No. Deleting the chat is owner only, and no combination of admin rights grants it. The same is true of transferring ownership.

Can an admin remove the owner

No. Attempting to edit the owner's rights from any other account is refused with a specific error. The owner can only be replaced through a deliberate transfer performed by the owner.

What is the difference between an admin and the owner

The owner is one account holding every right plus deletion and transfer. An admin is a member holding a chosen subset of rights, which can be as small as one. Two admins in the same chat can have completely different powers while looking identical in the interface.

Why can I not promote somebody I just added

Most often because you were made an admin very recently yourself, which Telegram blocks with a documented refusal saying you cannot add or modify other admins yet. It clears on its own. The other common cause is the other person's privacy settings, which produce a different refusal for the same visible outcome.

Do bots follow the same permission list

Yes, with one exception. A bot receives rights from the same list with the same meanings, but bots cannot edit admin privileges at all, so no bot can promote or demote anybody.

What does an anonymous admin actually hide

It hides the account from the member list and posts its messages under the group's name rather than the person's. It hides identity, not activity, and administrative actions still appear in the action log.

Does a custom admin title give extra power

No. The title is a label shown beside the name and it changes nothing about what the account may do. A rank containing emoji is rejected outright.

What do I need before transferring ownership

Two factor authentication enabled, a password that has not changed in the last twenty four hours, a session older than twenty four hours, and the incoming owner already a mutual contact. Each condition has its own refusal message, and the time based ones report how long is left.

Which single right is the most dangerous to give

The right to add new admins. Every other right delegates one task, while that one delegates the ability to delegate, up to whatever the giver holds. It is the only entry on the list that can reproduce your whole configuration on an account you have never seen.