Telegram logoTelegram
Group Management
Group Ownership
Admin Rights
Permission Transfer
Member Management
Group Settings
Role Assignment

How to Transfer Telegram Group Ownership to Another Member?

Telegram Official Team
November 20, 2026
how to transfer telegram group ownership, change telegram group owner, transfer ownership to another member, telegram group admin rights, assign new group owner telegram, telegram transfer ownership option missing, telegram group permission settings, manage telegram group members and roles, can you transfer group ownership without losing members, telegram group ownership transfer not working how to fix
Learn how to transfer Telegram group ownership safely: the exact member-list path on each platform, pre-checks, side effects, rollback, and FAQ.

If a Telegram group you created now lives under decisions you can no longer make, the fix is a single, narrow operation: transfer Telegram group ownership to another member. It is not hidden behind a support ticket, and it cannot be approximated by handing out administrator rights — the owner role is a distinct slot on the group itself, and Telegram treats it that way. This guide is built as a troubleshooting walkthrough: start from the symptom, diagnose which role is actually blocking you, follow the shortest reachable path on each client, and then verify that the handover actually landed and understand what can and cannot be undone.

The Core Problem: Ownership Is a Separate Slot From Admin Rights

Most people who arrive at this topic describe the same symptom in different words. Someone can still pin messages, delete spam, and ban troublemakers, but the switches that matter — adding new administrators, configuring the group, deleting the group entirely — either fail or do not appear. Others reach the topic because of a departure rather than a permission wall: a founder is leaving a company, a volunteer is stepping back from a community, or the account that originally created the group is about to be closed or reassigned. One group is blocked by permissions, the other by timing, but both arrive at the same question.

The diagnosis is identical in both cases. Administrator permissions are a bundle of capabilities, and the bundle is configurable: change group info, delete messages, ban users, invite users, pin messages, manage video chats, remain anonymous, add new admins. Ownership is not part of that bundle. It is a single, unique position attached to the group, held by exactly one account at a time. Another administrator cannot demote the owner, cannot strip the owner's rights, and in most clients cannot even see an action that would do so. That asymmetry is why "just promote me to admin" never solves the problem — it grants capability, not control.

A second symptom follows from the same root cause. When an owner's account disappears — deleted by the user, closed through the inactivity policy configured under account settings, or simply abandoned — the group does not automatically promote its most senior administrator. Depending on the situation, the group can end up without a functioning owner while a full admin team remains in place. This is the scenario that turns a two-minute task into a support investigation, which is precisely why the transfer should happen before the departure, not after.

The Core Problem: Ownership Is a Separate Slot From Admin Rights
The Core Problem: Ownership Is a Separate Slot From Admin Rights

What Transfer Moves — and What It Leaves Behind

Before touching any menu, be clear about the object being transferred. Ownership is a property of the group as an entity, not a property of your account. When you hand the group over, the recipient receives the entity itself: its message history, its member list, its administrators and their individual permission bundles, its invite links, its public username if it has one, its pinned messages, its settings such as slow mode or content-saving restrictions, and its position in the search directory if it is public. Your personal account is untouched. You do not lose your own chats, your contacts, or your other groups.

The boundaries with similar-sounding features matter here, because confusing them is the most common source of wasted effort. Promoting someone to administrator gives them a configurable subset of capabilities but leaves you in the owner slot. Adding a bot as an administrator gives the bot a scripted subset of capabilities — and a bot cannot occupy the owner slot at all. Transferring to a different group or migrating members to a new group and deleting the old one is a completely different operation that loses history and links. And simply leaving the group is not a transfer; the owner role persists with the account, not with the seat in the member list.

A Short Comparison of What Changes

Element After promoting to admin After transferring ownership
Message history Unchanged Unchanged — stays with the group
Ability to add or remove admins Possible if the "add new admins" right is granted Becomes the recipient's decision
Ability to delete the group Generally not available to standard admins Moves to the recipient
Public username and invite links Unchanged Unchanged — they belong to the group
Owner badge in the member list Stays with the original account Moves to the recipient

The table reflects the behaviour commonly observed across current clients as of this writing. Exact labels and the visibility of certain actions vary by client build and by locale, so treat the left-hand column as stable and the right-hand column as something to confirm on your own installation rather than take on faith.

The Shortest Reachable Path, Platform by Platform

Telegram's clients share the same data model but not the same layout. The entry point is always the member list of the group, and the action is always attached to the person you want to hand over to — not to a global settings page. The wording of the action is localized, and some builds place it inside the member's action menu while others surface it only after the member has been promoted to administrator. If you do not see it on the first attempt, promote the member first, then reopen the same menu; that is the single most useful habit to develop here.

Desktop: Telegram Desktop and the Native macOS Client

On Telegram Desktop the fastest route is a right-click on the group in the chat list to open Manage Group, then the Members tab. Search for the person by name if the list is long, click their row to open the member's context menu, and look for the ownership action. If it is absent, promote the member to administrator, close the panel, and reopen their entry — the option commonly appears at that point because the client only renders it for accounts that already hold an admin role.

The native macOS client follows the same logic with slightly different chrome: open the group, click the group name in the header to reach the info panel, switch to Members, then open the member's context menu. On both desktop variants, a confirmation dialog appears before the change is applied, and it is worth reading rather than dismissing — it states what you are giving up.

Android

In the Android app, open the group and tap the group title at the top of the chat. That opens the group profile. Tap Members, locate the person, and tap their row to open the member's action sheet. For an owner, the sheet contains both the promotion option and the ownership action; when only the promotion option is visible, promote first and then reopen the sheet. Long-pressing the row usually surfaces the same menu, which is a useful fallback when a tap opens a profile preview instead.

iOS and iPadOS

On iOS the path is the same shape: open the group, tap the title to enter the group info screen, open Members, tap the member, and use the overflow control in the member's screen. On iPadOS in a wide layout, the member list may sit beside the chat rather than replacing it, but the controls are identical. If the group is large, use the search field at the top of the member list rather than scrolling.

Web Clients

Browser-based clients mirror the desktop layout closely, and the same shortcut applies: click the group name to open the info column, then Members, then the member's context menu. Because web clients update on their own schedule, a given web build may lag the installed desktop app by a few interface revisions. If the ownership action is missing in the browser but present in the desktop app, that is a client difference, not a permission problem — the underlying account still holds the owner role.

Tip: The ownership action is only rendered for the account that currently holds the owner slot. If you are an administrator with the "add new admins" right, you can build the admin team but you should not expect to see the transfer control. Verify by checking whether the promotion menu lets you demote the person marked as the current owner — if it does not, you are not the owner.

Pre-Flight Checks Before You Press Anything

A transfer is quick, which is exactly why it deserves a moment of preparation. Five checks cover almost every failure mode people report afterwards, and each one takes under a minute.

  1. The recipient must already be a member. You cannot transfer to someone who is not in the group. If the person left recently, re-invite them first and confirm they appear in the member list.
  2. The recipient must be a user account, not a bot or a channel. Bots can hold administrator rights but cannot occupy the owner slot. Bots also cannot be group owners in any client, so a handover to a bot is structurally impossible rather than merely disallowed.
  3. The recipient's account must be reachable and active. Handing ownership to an account that is about to be deleted simply moves the problem. Ask the recipient to confirm they intend to keep the account.
  4. Your own rights should be decided in advance. Decide whether you will remain an administrator afterwards or whether you should be removed. Doing this deliberately beats discovering the answer later.
  5. Any linked entities should be listed. If the group is the discussion group of a channel, or the channel is linked to a group, note both. They are separate entities with separate ownership and are transferred separately.

The reason to do this before rather than after is simple: once the transfer lands, the ability to fix a mistake moves to the new owner. If you forget that a bot was the only thing holding a moderation workflow together, or that a linked discussion group still points at the old setup, you will be asking the new owner for permission to repair it. Checking first keeps that request hypothetical.

Warning: Rehearse in a disposable group first. Create a throwaway group with two accounts or with a colleague, perform the transfer, and observe what happens to the former owner's rights and to the admin list. The observations below are based on current clients as of this writing, but the cost of confirming them yourself in a test group is a couple of minutes, and the cost of being surprised in a live community is much higher.

A Worked Example: Handing Over a 4,000-Member Community

Consider a hypothetical but realistic scenario. A volunteer has run a hobby community of roughly 4,000 members for several years. The group has eight administrators with different permission bundles, a public username, a linked discussion arrangement with an announcements channel, a handful of pinned onboarding messages, and a moderation bot that greets new members and removes join-request spam. The volunteer is stepping back and has nominated a long-standing moderator to take over.

The naive approach — "promote them to full admin and remove my own rights" — fails in three ways. It leaves the owner slot with an account that is about to become inactive, it does not transfer the ability to add or remove administrators in the long run, and it leaves the departing volunteer unable to fix anything if the new owner misconfigures a permission. The correct sequence is shorter and more deliberate. First, the moderator is promoted with the full administrator bundle, so that both accounts can see the same controls during the transition. Second, the transfer is performed from the member list. Third, the departing volunteer verifies the new owner's badge appears in the member list and that the promotion menu no longer offers actions against them. Fourth, the volunteer decides explicitly whether to stay as an administrator for a cooling-off period, and if not, removes themselves deliberately rather than simply going silent.

Two details in this example deserve separate attention. The moderation bot is unaffected by the transfer — it keeps its administrator rights and keeps running, because bot rights belong to the bot, not to the owner. That is convenient, but it is also the reason a departing owner should review what the bot can actually do: an automated tool that can delete messages and ban users is a standing capability that will now sit under someone else's authority. The second detail is the announcements channel. If it is linked to this group, it is a separate entity. Transferring the group does not transfer the channel, and the departing volunteer should either transfer both or document clearly that only one is changing hands.

What Changes the Moment the Transfer Lands

The immediate and reliable change is the badge. The recipient becomes the account the client marks as the group's owner, and the promotion menus in every client stop offering actions against that account. This is the single fastest verification you have: open the member list, confirm the label has moved, and confirm that the previous owner can now be demoted by the new one.

The less predictable part is the former owner's residual status. Empirical observation across current clients suggests the departing owner commonly remains an administrator with their previously configured rights rather than being dropped to a regular member, but the exact behaviour is client- and build-dependent and should not be assumed. The practical consequence is that you should check rather than guess: after the transfer, open the administrator list and look at your own entry. If you intend to leave, remove yourself deliberately. If you intend to stay for a transition period, reduce your own bundle to the minimum you actually need — typically nothing beyond what a moderator needs — so that an unattended dormant account is not holding wide permissions.

Message history, invite links, and the public username do not change at all. They belong to the group. Members do not receive a notification that the group changed hands in most builds, which is a social consideration rather than a technical one: for a community of any size, a pinned announcement from the incoming owner explaining the change is usually the difference between a smooth transition and a week of confused questions.

Exceptions and Side Effects You Should Expect

The operation itself is a single step, but the surrounding system has edges. The most consequential one is that the transfer is effectively one-way from your perspective unless the new owner cooperates. There is no visible "undo" for the former owner, because undoing it would require the new owner to transfer it back. If you are handing a group to someone you do not fully trust, that trust is the actual currency of the transaction, and no setting substitutes for it.

A second edge concerns the recipient's consent. Some clients present the change as a confirmation that you perform, with the recipient simply notified afterwards; others route a confirmation to the recipient. Treat the exact handshake as build-dependent, and settle it before the moment of transfer by telling the recipient what to expect and asking them to confirm that the badge appears on their side. If nothing appears on their end after you confirm, the most likely explanations are that they were not a member, that the action targeted the wrong account, or that their client was showing a stale member list — pull to refresh or reopen the group before assuming something worse.

A third edge involves the account inactivity policy. Telegram accounts can be configured to self-delete after a period of inactivity, and the default is measured in months. If the new owner disappears and their account is eventually removed by that policy, the group can be left without an owner in the same way the original problem arose. For any group that matters, at least two people should know about this setting, and the owner's account should not be a purely secondary identity that nobody monitors.

Groups, Channels, and Linked Discussion Groups

Telegram has more than one container type, and the handover logic differs subtly between them. Basic groups and supergroups both have an owner slot and both support transfer through the member list. Channels also have an owner and support transfer through the subscriber list, and the mechanics are close enough that the same habit applies: find the person, check whether they are already an administrator, then use the ownership action from their entry.

The trap is the linked pair. An announcement channel and its discussion group are two entities, each with its own owner and its own administrator list. Setting up a discussion link does not merge them into one object, and transferring one does not transfer the other. If you run both, decide deliberately whether both change hands. If the channel goes to one person and the group stays with another, the link still works, but two different people now control the two halves of a single community experience, which is a configuration that only makes sense if they coordinate.

Group type also affects which other features are available. Supergroups unlock the administrator log — in many clients labelled along the lines of Recent Actions — which records administrative events such as bans, promotions, and permission changes. Channels have a comparable log. Basic groups are more limited. This matters for verification, because the log gives you an independent record of whether the transfer and the surrounding permission changes actually occurred, rather than relying on the badge alone.

When the Owner Is Unreachable or the Account Is Gone

This is the scenario that sends people searching for a hidden setting that does not exist. If the account holding the owner slot is gone and no transfer was ever performed, there is no in-app control that lets an administrator claim the role. Administrator rights do not escalate to ownership, and no client surfaces a "claim group" action. Be suspicious of any instruction that claims otherwise, because the mechanism it describes does not exist in the product.

What remains is administrative rather than technical. In some situations, people report that contacting Telegram's official support channels results in assistance with a stranded group, typically where the group is clearly identifiable and the admin team is clearly legitimate. Empirical observation suggests this assistance is inconsistent and case-dependent rather than a documented, guaranteed procedure, so it should be treated as a last resort that may or may not succeed, never as a plan. The practical fallback is structural: stand up a replacement group or channel, reuse the public username if it becomes available or pick a new one, migrate the member base through an announcement in the old group while it remains readable, and accept that history does not move with it. Communities that do this successfully usually keep the old group read-only for a while so latecomers can find the pointer.

The prevention is unglamorous and effective. For any group that matters, designate a successor now and record — outside Telegram, in whatever your team actually uses for documentation — who the owner is, who the administrators are, what the moderation bots do, and whether there is a linked channel. Groups do not fail because people forget the transfer step. They fail because nobody wrote down that the transfer step existed.

Automation Boundaries: Bots, the Bot API, and Least Privilege

Automation is where expectations most often outrun the product. Telegram's bot platform exposes methods for managing member status, including promoting and restricting members within the rights a bot itself has been granted. It does not expose a method for transferring group ownership. A bot cannot become the owner of a group or channel, and a bot cannot be an owner's successor. Any third-party service or bot that advertises "automatic ownership handover" is doing something other than what the name suggests — most likely reassigning administrator rights, which is a different and weaker thing.

That said, bots are genuinely useful around a handover, and the guiding principle is least privilege. A moderation bot that only needs to delete spam and mute repeat offenders does not need the ability to add administrators, and it certainly does not need the ability to change group info. A third-party archiving bot that mirrors messages into a backup channel needs to read messages, which is a different and broader capability than moderating them. Before or immediately after a transfer, review each bot in the administrator list and ask what would happen if its credentials leaked. If the answer is "it could remove the new owner's admins," that right should probably be revoked.

Note also that bot permissions do not survive a bot being re-added as a new entity. If a moderation bot is removed and re-added during a transition, its rights are configured from scratch, and any workflow that depended on its earlier configuration will break silently until someone notices the spam. Keep a short written note of every bot's required rights and custom title so the reconfiguration is mechanical rather than archaeological.

Troubleshooting: Symptom, Cause, Verification, Fix

The following patterns account for most reported difficulties. Each is written so that you can verify the cause yourself rather than take it on trust, because client builds differ and a diagnosis that works on one device may not describe another.

Troubleshooting: Symptom, Cause, Verification, Fix
Troubleshooting: Symptom, Cause, Verification, Fix

Symptom: The ownership action is not in the member's menu

The likely cause is that the account you are using does not hold the owner slot, or that the client only renders the action after the member has administrator status. Verify by opening the administrator list and checking whether your own entry is marked as the owner, and by attempting to demote the person you believe is the owner — if the option is greyed out or absent, you are not the owner. The fix is either to switch to the account that does hold the role, or to promote the target member to administrator first and then reopen their member entry.

Symptom: The transfer appears to succeed but the badge does not move

The most common cause is a stale member list rather than a failed operation. Verify by closing and reopening the group, or by opening it from a second client signed into the same account. If the two clients disagree, the one that has just re-fetched the data is the accurate one. A second possible cause is that the action targeted a different account with a similar display name; search the member list by username rather than by name where possible.

Symptom: The recipient says they see no change on their side

Ask them to reopen the group and check the member list from their own device, and to confirm which account they are signed into — people frequently maintain two accounts and are signed into the wrong one in one app. If they still see nothing after a refresh, and the transfer produced no error on your side, the practical check is the administrator log: if the event is recorded there, the state changed and the issue is display-side; if it is not recorded, the operation did not complete.

Symptom: The group has no owner and admins cannot fix it

This is the stranded-group case. Verification is straightforward: no account shows the owner label, and no administrator can demote anyone else's owner-level status because there is nothing above them to demote. There is no in-app resolution. Treat support contact as a possibility rather than a guarantee, and in parallel begin the replacement-group plan so that the community is not blocked on an uncertain outcome.

Verification and Observation Methods You Can Reproduce

Because client behaviour varies, the following steps are written so that any reader can confirm the outcome on their own installation rather than relying on a description. They take a few minutes in a test group and can be repeated verbatim in a live one.

  1. Establish a baseline. In a disposable group with at least one other account, open the member list and note which account carries the owner label and which carries administrator rights.
  2. Perform the transfer. Use the shortest path for your platform as described above, and read the confirmation dialog rather than dismissing it.
  3. Check the badge from two clients. Sign the same account into a second client, or open the browser version, and confirm both agree that the owner label has moved. Disagreement indicates a stale cache rather than a permission problem.
  4. Check the former owner's residual status. Open the administrator list and look for your own entry. Note whether you still appear, and with which rights. This is the single most build-dependent observation in the whole process.
  5. Check the action log. In a supergroup or channel, open the recent administrative actions view and confirm the handover event is listed. This gives you an independent, dated record.
  6. Check that bots are unaffected. Confirm each bot in the administrator list still holds the rights it needs. If a bot was re-added during the change, its rights will be at their defaults and will need reconfiguring.

One further verification applies to any group with a public username. Search for the username from a third account that has no connection to the group. The search result and the group's identity should be unchanged, which confirms that the entity moved rather than being recreated. If the username were somehow released, that would be a serious problem, and this check catches it in seconds.

Rollback: Can You Get Ownership Back?

There is no unilateral rollback. The former owner has no control that reclaims the role, because such a control would make ownership meaningless. The only path back is the new owner transferring it in return, which is exactly the same operation run in the opposite direction. This asymmetry is the reason the pre-flight checks matter more than the transfer itself: the correctness of the handover is determined before the action, not after it.

If you need a reversible arrangement, do not use ownership transfer at all. Keep the owner slot where it is and grant the other person a broad administrator bundle instead. You retain the ability to reverse course, at the cost of the other person's inability to fully control the group — a trade-off that is often correct for a temporary absence, a trial run of a new lead, or a handover that has not been fully agreed yet. The transfer is for the moment the arrangement becomes permanent, not for the period while it is being tested.

A partial mitigation is sequencing. Perform the transfer, keep both accounts as administrators for an agreed cooling-off period, and only then reduce the departing account's rights. This does not create a rollback mechanism, but it does keep two people with the ability to correct mistakes during the window when mistakes are most likely.

Applicable and Non-Applicable Scenario Checklist

The transfer is the right tool in a narrower set of situations than people assume. The following admission criteria are worth working through honestly before you start.

Transfer ownership when: the person leaving will not return to a role that requires control; the recipient is a verified, active, long-term participant or colleague; the group's history and username must be preserved under new leadership; and there is a documented successor list for the future. This is the standard case for a departing founder, a company offboarding, or a volunteer stepping back after a long tenure.

Do not transfer when: the arrangement is temporary or being trialled — use full administrator rights instead; you do not have a durable way to identify and trust the recipient; the group is likely to be superseded by a new one anyway; or the transfer would leave the group's moderation tooling under an account nobody monitors. In these cases, the costs of an irreversible handover exceed its benefits, and the correct answer is usually a permission change rather than a role change.

Two further boundaries apply to organisations. If your group belongs to an entity with real retention obligations, take an export of the chat history from a desktop client before the handover, so that the record does not depend on the new owner's cooperation. And if the group's public identity is used in marketing or documentation, update those references in the same week rather than assuming someone else will notice that the contact point has changed.

Best Practices Checklist for a Clean Handover

Distilled to decision rules, a clean handover looks like this. Confirm the recipient is a member and a user account rather than a bot. Promote them to full administrator first so that both accounts can see the same controls. Perform the transfer from the member list, reading the confirmation. Verify the badge from a second client and check the action log. Decide deliberately whether you remain an administrator, and if you do, reduce your own bundle to the minimum. Review every bot's rights and revoke anything broader than the bot's job requires. Export the history if retention matters. Announce the change to the community, because silence generates more support questions than the change itself. Finally, write down who the owner is now and who the successor is, in a place that is not Telegram.

The whole sequence is perhaps fifteen minutes of work for the technical steps and considerably more for the communication. That ratio is the point. The technical operation is nearly trivial; the reason handovers go wrong is that they are treated as a button press rather than as a change of custody.

Frequently Asked Questions

Can an administrator transfer group ownership without being the owner?

The transfer control is rendered for the account that currently holds the owner slot, so in practice the answer is no. An administrator with the "add new admins" right can build and reshape the administrator team, but that is a different capability from moving the owner role. To confirm on your own installation, open the administrator list and try to demote the account labelled as the owner; if that option is unavailable to you, you are not in a position to transfer the group.

Does the previous owner stay an administrator after transferring the group?

Empirical observation across current clients suggests the departing owner commonly retains administrator status with their existing rights rather than being dropped to a regular member, but this is build-dependent and should not be relied on. Verify directly by opening the administrator list immediately after the transfer and looking at your own entry. If you intend to leave the group, remove yourself deliberately; if you are staying for a transition window, reduce your own permission bundle to the minimum you actually need.

Can ownership be transferred to a bot or to a channel account?

No. Bots can hold administrator rights and can use the bot platform's member-management methods within those rights, but a bot cannot occupy the owner slot, and there is no bot API method for transferring ownership. The recipient must be a regular user account that is already a member of the group. If you see a third-party service advertising automatic ownership handover, it is almost certainly reassigning administrator rights rather than the ownership role itself.

What happens to message history, invite links, and the public username?

They stay with the group. Ownership is a property of the entity, not of your account, so history, existing invite links, pinned messages, settings, and the public username all remain attached to the group after the handover. Your personal account keeps its own chats and contacts. The one thing you should still verify afterwards is that the public username still resolves correctly from an unrelated account, which confirms the entity moved rather than being recreated under a new identity.

Can I get ownership back after transferring it away?

Not unilaterally. There is no control that lets a former owner reclaim the role, because such a control would defeat the purpose of the transfer. The only route back is for the new owner to transfer it to you in return. If you need a reversible arrangement, keep the owner slot where it is and grant broad administrator rights instead, then perform the actual transfer only once the change of custody is genuinely permanent.

What if the current owner's account is already gone?

There is no in-app action that lets an administrator claim the owner role, and administrator rights do not escalate to ownership. People sometimes report receiving help after contacting Telegram's official support channels for a stranded group, but empirical observation suggests this is inconsistent and case-dependent rather than a documented procedure, so it should be treated as a possibility rather than a plan. The dependable fallback is structural: create a replacement group, migrate members through an announcement in the old one, and accept that history does not move with them.

Next Steps

The shortest answer to the original question is that ownership transfer is a two-minute operation performed from the group's member list, available only to the account that currently holds the owner slot, and irreversible from the departing side. Everything else in this guide exists because that simplicity is deceptive: the checks that make it safe happen before the button, and the consequences that surprise people unfold after it.

If nothing else, do two things today. Rehearse the transfer in a disposable group so you know exactly where the control lives on your own devices and what happens to the former owner's rights in your client build. Then write down, outside Telegram, who owns each group and channel you care about, which bots hold which rights, and who the designated successor is. That note is what turns a future emergency into a routine handover.

📺 Related Video Tutorial

How to Manage Groups in Microsoft 365 Admin Center Owners, Members, Settings & More