Appoint another owner before the current one leaves, confirm they can open the organization settings, update the billing contact, and only then remove the departing owner. GitHub warns that removing yourself does not update the payment details on file. A lone owner leaving can strand billing and administration.
Why single owners are a risk
Small teams often begin with one founder or engineer who created the organization. That person owns billing, security settings, app installations and member management. If they leave without a handover, nobody can change policies, approve tokens or remove the next leaver.
GitHub's page on transferring organization ownership says that if you are the only person with owner privileges, you should give another member the owner role. It also points to guidance on maintaining ownership continuity. The page does not state a recommended number of owners, so choose a number your team can defend, usually at least two and few enough to keep the list reviewable.
Handover steps
- Choose the successor. Pick someone who will stay and who is accountable for the account.
- Give them the owner role. Do this a while before the departure, not on the last day.
- Ask them to sign in and open the organization settings. GitHub's steps say to confirm the new owner can access settings before you remove yourself.
- Transfer billing responsibility. If the leaver pays by card or other method, the new owner or a billing manager must update the payment information. Only they can remove the old details.
- List what the departing owner administered: apps, webhooks, SSO configuration, secrets, enterprise memberships.
- Move ownership of OAuth and GitHub Apps registered under a personal account to the organization where possible.
- Remove the departing owner from the organization.
- Check the audit log to confirm the change.
The handover record
Write a short page with these headings.
| Item | Detail to capture |
|---|---|
| Owners after handover | Names and the date each was added |
| Billing | Who is the contact, how it is paid |
| Apps and integrations | Owner, purpose, scopes |
| Recovery | How to regain access if an owner is locked out |
| Next review date | A date, not "later" |
Store it where more than one person can read it.
Common mistakes
- Removing the owner first and then discovering nobody can approve the replacement.
- Forgetting that billing sits with the person, so the card on file remains theirs.
- Leaving personal accounts as owners of integrations the company depends on.
- Keeping an owner who no longer needs the power. Owners should be the smallest group that keeps the account recoverable.
Make it routine
Add the owner list to your quarterly access review. If any owner has moved roles, apply the same transfer process described for internal moves, because a change of job should trigger a change of power.
Quick check
How many owners should an organization have?
GitHub does not give a number. Use at least two so one departure does not strand the account, and keep the list small enough to review.
Does removing myself change billing?
No. GitHub says removing yourself does not update the billing information on file.
Safeguard's compliance and evidence automation can help you keep access reviews and handover records in one place for audits. You can run a free scan at gold.safeguard.sh/scan.
Sources
Last reviewed: 19 October 2026.
