Setting up a second admin who cannot remove you

Why this question comes up

If you run a Telegram group or channel with any real size, you eventually need a second person with admin rights. Maybe you’re asleep when a spam raid hits, maybe you’re traveling, maybe you just want someone to handle day to day moderation so you’re not the single point of failure. The moment you consider it, the obvious fear shows up: what stops that admin from turning around and locking you out of the thing you built?

This comes up a lot with people running managed communities on top of our hosting, and the good news is that Telegram’s permission model already answers the question, with no workaround required. What you need is to understand what “admin” actually means versus what “owner” means, because they are not the same role and Telegram treats them very differently under the hood.

Creator, admins, and members are not a spectrum

It’s tempting to think of Telegram roles as a ladder: member, then admin, then “super admin,” then owner. That’s not how it works. There are really only two structural tiers that matter for control: the creator (owner) of the group or channel, and everyone else, including admins with full rights.

The creator is set at the moment a group or channel is made, tied to whichever account did the creating. That status doesn’t move unless the creator explicitly transfers it. No permission toggle, no admin right, no combination of settings lets another admin become the owner or strip the owner of their role. An admin with every single right enabled, including the ability to add other admins, still cannot demote or remove the creator. That’s baked into how Telegram’s client and servers enforce roles, well below the level of anything you get to configure.

This is the part people miss when they worry about “giving someone too much power.” You can give a second admin nearly every capability a group has to offer, and they still sit below you structurally, because admin rights and ownership are different axes entirely.

What the “add new admins” toggle actually controls

When you promote someone to admin, Telegram lets you turn on or off a specific right usually labeled something like “add new admins.” People assume this is the dangerous one, the one that lets someone take over. It isn’t, not in the way they think.

That toggle controls whether this admin can promote other members to admin themselves. It does not let them touch you, and it does not let them promote someone above their own rank. If you leave it off, the admin can moderate but can’t build a chain underneath themselves. If you turn it on, they can add more admins, but only with rights equal to or less than what you gave them, and only the creator can ever manage rights unrestricted by that ceiling.

So the toggle is about whether your second admin can deputize others, not about whether they can push you out. Those are separate risks and only one of them is yours to manage through this setting.

The seniority rule nobody explains

Here’s the mechanic that actually protects you day to day, separate from the creator/admin split: Telegram enforces a seniority rule on who can demote whom. An admin can generally only be demoted by the person who promoted them, or by someone above that person in the chain, ultimately tracing back to the creator. A peer admin who didn’t promote them, even with identical rights, typically can’t touch their standing.

Practically, this means if you personally promote your second admin, you are the one who can demote them, and they cannot demote each other into a stalemate or gang up to strip your rights, because none of them sit above you in that chain. This is the same design that stops one admin from quietly removing another admin’s access out of spite in a large group with several moderators. It’s structural, enforced by Telegram rather than left to courtesy between admins.

Ownership transfer is the one door that actually exists

There is exactly one way control of a group or channel changes hands: an explicit ownership transfer, initiated by the current owner, from inside the group or channel settings. It requires your two factor authentication password, and it requires the recipient to accept. There is no silent version of this. No admin right escalates into ownership. No bug in the permission model lets someone route around the transfer flow, because ownership is a separate field tied to the entity, sitting outside the permission system entirely.

If you never touch that transfer flow, your ownership doesn’t move, full stop. The entire “can they lock me out” question collapses down to one very simple operational rule: don’t transfer ownership unless you mean to, and don’t 2FA-approve anything you didn’t initiate yourself.

Setting it up

In practice, adding a second admin who genuinely cannot remove you takes a few minutes:

1. Open the group or channel’s admin list from the info panel.
2. Add the person as a new admin from there, not by giving them a role through some other side channel.
3. Go through each right individually rather than accepting a default set. Turn on what they actually need to moderate: deleting messages, banning users, pinning, managing invite links, whatever fits their job.
4. Leave “add new admins” off unless you specifically want them building out a moderation team of their own. If you do want that, understand it caps at their own rights, not yours.
5. Leave ownership exactly where it is. There’s no step here, because you’re not touching the transfer flow at all.

That’s the whole setup. There’s no extra “protect the owner” checkbox to hunt for, because the protection is the fact that ownership and admin rights are different mechanisms entirely.

Which rights to actually hold back

Granularity is your friend here. A few things are worth thinking about before you hand out full rights by default.

Anonymous admin posting hides who made a change, which is fine for a brand voice but makes it harder to audit who did what if something goes wrong later. Turn it on deliberately, not by habit.

Managing video chats and invite links matters a lot in larger communities, where invite links get shared outside the group and become a spam vector. If your second admin doesn’t need to generate links, don’t give them the right.

Pin messages is low risk and usually fine to hand over freely.

Add new admins, as covered above, is really about delegation depth. It’s still worth being deliberate about who can build under them.

None of these choices change whether they can remove you. They change how much operational surface they control, which matters for a different reason: the more rights an account has, the more damage a compromised version of that account can do, which is the real risk worth planning for.

Bots follow the same rules, with one wrinkle

If you run a moderation bot as an admin, which is common once a group gets large enough to need auto-moderation, the bot sits in the same hierarchy as a human admin. Whoever added the bot functionally occupies the “promoter” slot for it. The bot can’t out-rank the creator any more than a person can, and it’s subject to the same demotion rules. The wrinkle is that bot tokens are a separate credential from the group’s permission structure entirely, so losing control of a bot’s token is an account safety problem, not a permissions problem, and it’s worth treating it that way in how you store and rotate tokens.

The actual failure mode is losing your own account

Everything above assumes your own account stays yours. The real way people lose control of a group they own is losing the account itself: a stolen session, a forgotten 2FA recovery email, a SIM swap on the phone number tied to the account, or a ban triggered by activity that looked automated from Telegram’s side. A rogue admin is almost never the cause. None of the permission structure discussed here protects against that, because at that point the problem is an account that belongs to whoever is holding it, which no amount of creator rank can fix.

That’s a separate discipline from admin permissions: keeping your 2FA password and recovery email current, keeping sessions audited, and not routing your primary owner account through infrastructure that risks flags or bans. It’s worth treating as its own checklist rather than folding it into “who has admin rights,” because the fixes are completely different.

Bottom line

A second admin, set up correctly, cannot remove you: Telegram separates ownership from admin rights as a matter of design, and enforces a seniority chain on top of that for anyone below the owner. There’s no special setting to find, just how the hierarchy works. Your actual job is picking sensible rights for the role you need filled, and keeping your own account secure enough that the ownership question never becomes relevant in the first place.

If you’re setting up admin structure for a community running on hosted infrastructure and want a second opinion on what rights make sense for your setup, come find us here.

Get new guides and videos first — join the Telegram channel.