-
Notifications
You must be signed in to change notification settings - Fork 924
Description
To Reproduce / Steps to observe the problematic state
- Be an administrator in a group where the original creator is no longer a member.
- Go to the group's info page -> "Manage Group" -> "Administrators".
- Observe the list of administrators. Note that no user is marked with the "Owner" or "Creator" title, nor do they have the crown (👑) icon.
- (Optional) Use a management bot (e.g., @Rosebot) and issue the /adminlist command. The bot's output will also confirm that there is no user with the "Creator" role.
- As a current administrator, attempt to find an option to claim or transfer ownership. The "Transfer Group Ownership" option is completely absent, as expected, since we are not the owner.
Expected behavior
There should be a clear and reliable mechanism for group ownership to be maintained.
- Scenario A: If an owner leaves a group, Telegram should enforce the transfer of ownership to another member, and this new owner should be clearly visible to all other administrators.
- Scenario B: If an owner's account is deleted by Telegram, there should be a documented procedure for the remaining administrators to elect or claim ownership. A group should not be allowed to enter a permanent state without an owner.
Actual behavior
The group is effectively ownerless.
- No administrator holds the "Creator" role.
- Key administrative functions that require owner-level permissions are permanently locked.
- There is no visible path for any of the existing, active administrators to be promoted to owner.
Operating system
- macOS Sequoia 15.5
Version of Telegram Desktop
- 11.15.274613 Stable
Installation source
- Static binary from official website
Additional context
This is a long-standing group with a significant number of members: [over 1,000 members]. The inability to manage ownership is not just an inconvenience but a serious risk to the community's future. If the current admins need to step down or leave, the group could become completely unmanageable.
We are seeking guidance on whether this is an intended design limitation or a bug.
- Is there any hidden or established procedure for promoting an existing admin to owner in such a case?
- If not, we would like to propose this as a critical feature request for a mechanism to recover orphaned groups.
Thank you for your time and consideration. We look forward to any assistance you can provide.