How Do I Transfer Ownership of My Organization Account in GitHub?

A GitHub organization does not have a single "owner account" the way a personal account does, so you transfer ownership by promoting another member to the Owner role, moving billing management to them, and then optionally stepping down or removing your own account. There must always be at least one owner, which is why you add a new owner before you remove the old one. The whole process happens in the organization's People and Settings tabs and takes only a few minutes once the new owner has a GitHub account.

Below we walk through the exact GitHub menu paths for promoting an owner, transferring billing, and handing over a whole organization or individual repositories — plus the mistakes that trip people up. If you are still getting comfortable with how Git-based platforms like GitHub organize access and history, this primer on version control is a useful companion.

Understanding GitHub Organization Ownership

The first thing to understand is that a GitHub organization is not owned by one account. Unlike a personal account, which belongs to exactly one user, an organization is administered by a role called Owner, and you can assign that role to as many members as you like. Owners have unrestricted access — they can change settings, manage billing, add or remove members and teams, delete repositories, and promote or demote other owners.

Because ownership is a role rather than a single account, "transferring ownership" really means granting the Owner role to someone new and then deciding whether you keep, downgrade, or remove your own account. GitHub enforces one hard rule throughout this process: an organization must always have at least one owner, so you can never remove the last owner. The members you can assign generally fall into three buckets:

• Owner — full administrative control over the entire organization, including settings, billing, and other owners.
• Member — a standard member with access only to the teams and repositories they have been granted.
• Billing manager — a special role that can view and edit billing information but cannot access repositories or org settings.

Step 1 - Add or Promote a New Organization Owner

This is the core of the transfer and the safest way to do it. You promote an existing member (or invite a new one) to the Owner role. Follow these exact menu paths from your organization's main page:

• Sign in as an existing owner and open the organization's page at github.com/<your-org>.
• Click the People tab in the top navigation. If the person is not yet a member, use Invite member first and wait for them to accept.
• Find the member in the list, click the three-dot menu (or the gear/checkbox row) on their row, and choose Change role.
• In the dialog, select Owner, then confirm with Change role.
• Ask the new owner to confirm they can reach Settings for the organization — that proves the role took effect.

The full path in words is Organization → People → member row → Change role → Owner. The promotion is immediate; there is no waiting period or approval step. From this moment the organization has two (or more) owners, which already satisfies most "transfer ownership" needs even if you never remove yourself.

Step 2 - Transfer Billing Management

If your organization is on a paid plan, the new owner should also control billing so invoices, receipts, and payment methods do not stay tied to you. Any owner can manage billing, but you can also assign a dedicated billing manager for someone who handles finances without needing repository access. To update billing:

• Go to Settings for the organization, then open Billing and plans in the left sidebar.
• Update the billing email to the new owner's address so renewal and receipt notifications reach the right person.
• Check the payment method; if it is your personal card, replace it with the new owner's card or the company's payment details.
• To delegate finances without ownership, open People → Add → billing manager (or the Billing managers section in settings) and invite them.

Do not skip the billing email. A common surprise after a transfer is that renewal warnings keep arriving at the old owner's inbox, and a missed payment can downgrade the entire organization's plan.

Step 3 - Step Down or Remove the Previous Owner

Only after the new owner is confirmed and billing is moved should you reduce your own access. You have two options, depending on whether you want to stay involved:

• Downgrade to Member — keep some access but give up administrative control. Path: People → your row → Change role → Member.
• Remove yourself entirely — leave the organization completely. Path: People → your row → Remove from organization, or use Leave organization from your own member view.

GitHub will block this action if you are the last remaining owner, displaying an error that an organization must have at least one owner. That is the safety net working as intended — promote the new owner in Step 1 first, and this step will go through without issue.

Transferring an Entire Organization to Another Account

Sometimes you do not just want a new owner — you want the whole organization to live under a different account or enterprise. The organization name itself does not move to a personal account, but you can effectively hand over the entire org by combining the steps above:

• Hand over administration — promote the receiving party to Owner (Step 1), transfer billing (Step 2), and remove the previous owners (Step 3). The organization keeps its name, repositories, and teams.
• Move into an enterprise account — if your plan supports GitHub Enterprise, an enterprise administrator can add the organization under Enterprise settings → Organizations → Add organization so it is governed centrally.
• Rename if needed — the new owners can change the org name under Settings → General → Rename organization, and GitHub will redirect the old URLs.
• Reassign GitHub Apps and OAuth apps — any GitHub App or OAuth app the organization owns is transferred separately from the org itself, under the app's own settings (Transfer ownership). Do this so integrations and automations keep working after you leave.

For most teams, "transferring the organization" is just the three-step owner handover above. The enterprise route only applies when a parent company centralizes many organizations under one billing and policy umbrella, and the GitHub App step matters only if your org publishes or owns its own apps.

Transferring Individual Repositories (Alternative)

If you only need to move specific projects rather than the entire organization, transfer repositories one at a time. This is independent of organization ownership and is handled inside each repo's settings:

• Open the repository and click Settings.
• Scroll to the bottom Danger Zone and click Transfer (Transfer ownership).
• Type the repository name to confirm, then enter the new owner's username or organization name as the destination.
• Click I understand, transfer this repository. The recipient must accept, after which GitHub redirects the old repo URL to the new location.

Repository transfers preserve issues, pull requests, stars, and most settings, and old links keep working through automatic redirects — making this a clean alternative when a full organization handover is more than you need.

Common Mistakes and Troubleshooting

• The last owner cannot be removed — GitHub refuses to downgrade or remove the only owner. Always promote a new owner first, confirm their access, then step down.
• Billing email still points to the old owner — receipts and renewal warnings keep arriving in the wrong inbox. Update the billing email and payment method under Settings → Billing and plans.
• 2FA organization requirement blocks the new owner — if the org enforces two-factor authentication, a new owner without 2FA enabled cannot be added. Have them enable 2FA on their account first.
• Confusing repo transfer with org transfer — moving a single repository through its Danger Zone does not change who administers the organization. They are separate actions.
• Pending invitation, not actual member — promoting only works once the person has accepted the invite. A pending invite cannot be assigned the Owner role yet.

Securing Organization Admin Access

Because the Owner role grants total control, the moment of transfer is a good time to tighten security. The same admin discipline you would apply to a CI pipeline or a release process applies to who can administer your code host. A few practical safeguards:

• Require two-factor authentication for every member under Settings → Authentication security, especially for owners.
• Keep at least two owners so a single lost account never locks the whole organization out.
• Audit the People list regularly and remove stale members or former contractors who no longer need access.
• Review the audit log under Settings → Logs after any ownership change to confirm only the expected actions occurred.

Managing who holds admin rights is part of broader engineering hygiene. If you are reviewing access policies, it pairs well with strong automation testing practices and a healthy code review culture, so changes to your repositories are always reviewed and traceable.

Conclusion

So, how do you transfer ownership of a GitHub organization? Because ownership is a role and not a single account, you add a new owner first (People → Change role → Owner), move billing to them, and then step down or remove yourself — remembering that GitHub always keeps at least one owner. Use repository transfers when you only need to move specific projects, and tighten 2FA and admin policies while you are at it. Follow that order and the handover is quick, safe, and fully reversible up to the final step.

Frequently Asked Questions

Can a GitHub organization have only one owner?

An organization must always have at least one owner, but it can have many. There is no single owner account to hand over, so transferring ownership means promoting another member to the Owner role and, if you wish, removing yourself afterward.

Where do I change a member's role to Owner in GitHub?

Open the organization, go to the People tab, click the three-dot menu next to the member, choose Change role, and select Owner. The member instantly gains full administrative control, including settings, billing, and member management.

Why can't I remove myself as the last owner?

GitHub blocks the removal or downgrade of the final owner so the organization is never left without an administrator. Promote another member to Owner first, confirm they have access, and only then step down or remove your own account.

How do I transfer billing for a GitHub organization?

Go to Settings → Billing and plans and update the billing email or add a billing manager. Any owner can manage billing, but assigning a dedicated billing manager lets a non-owner handle invoices and payment without full admin rights.

Is transferring a repository the same as transferring the organization?

No. Transferring a repository moves a single repo to another user or organization through its Settings → Danger Zone → Transfer ownership. Transferring the organization changes who administers the whole account by promoting a new owner; the two are independent actions.

How do I transfer ownership of a GitHub App owned by my organization?

A GitHub App is transferred separately from the organization. Open the app under Settings → Developer settings → GitHub Apps, select the app, and use its Transfer ownership option to move it to another user or organization. Reassign any OAuth apps the same way so integrations keep working after the handover.

What happens to a GitHub organization if the only owner's account is deleted?

Losing the sole owner can leave the organization without an administrator, which is exactly what GitHub tries to prevent by blocking removal of the last owner. To maintain ownership continuity, GitHub recommends keeping at least two owners so no single deleted or inactive account can lock everyone out of the org.

• What is an admin (administrator)?
• What are DevOps best practices?
• What is code review and its benefits?
• How do I run a system check on my Mac machine?
• Common mistakes hiring managers should avoid