Accidental removal of owner from account

[ljmccoy]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Actions

Body

I'm hoping someone from GitHub can point us in the right direction.

I'm posting on behalf of the owner of our company. We're currently locked out after an unfortunate mistake.

While cleaning up the organization's member list on May 13, 2026, the owner accidentally removed their own account from the organization. At the time, they were the only remaining owner, so there are now no owners or admins who can restore access.

The owner still has full control of their personal GitHub account and can complete any verification required. We also have documentation proving ownership of the organization and have already opened a support ticket, but we haven't received a response yet.

Unfortunately, the organization contains our private production repositories, so we're currently unable to access our source code and development has come to a standstill.

We're not asking anyone here to resolve the issue directly—we're simply hoping someone can advise whether there's another recovery process or help us get this in front of the appropriate GitHub team.

Has anyone experienced something similar, or is there another avenue we should pursue while waiting for support?

Any guidance would be greatly appreciated. Thank you!

[Dusky-77]

this happens way more than you think. because they were the last owner, the org is now totally orphaned. github safety locks it down so nobody can just break in, which means no quick setting can fix this right now.

your ticket is actually the only way to get back in. github support has to manually verify your business documents and force add their account back as the owner. since your production code is stuck, reply to your own ticket right now and add words like "Production Outage" or "Critical Business Blocker" to help push it past the basic support bots. also, double check if you ever set up an enterprise account above the org, because if you did, an enterprise admin can log into their own panel and fix this instantly.