Account Admin and Owner: Responsibilities and Rights
The account owner role isn’t just an extra set of permissions — it’s legal and practical responsibility for the entire developer account. Here’s how it differs from the admin role on both platforms, and the risk that comes with having only one owner.
Apple: Account Holder vs Admin
| Account Holder | Admin | |
|---|---|---|
| Number per account | Exactly one | Can be multiple |
| Signs legal agreements | Yes, only the Account Holder | No |
| Manages membership (renewal, cancellation) | Yes | Limited |
| Changing the Account Holder | Initiates the transfer | Cannot appoint a new owner |
| Access to certificates, apps | Full | Full |
The Account Holder in Apple Developer Program isn’t just a technical role — it’s the person who legally signs the Developer Program License Agreement. For organizations, that’s typically a director or an authorized representative, not a rank-and-file developer.
Google Play: Account Owner vs Admin
| Account Owner | Admin | |
|---|---|---|
| Number per account | Exactly one | Can be multiple |
| Can remove/replace the Owner | Initiates the transfer | No |
| Manages other users’ permissions | Yes | Yes |
| Access to all apps and data | Full | Full unless explicitly restricted |
The structure mirrors Apple’s: a single Account Owner carries formal responsibility, while Admins have near-equal operational authority but no right to transfer account ownership.
The main risk: a single point of failure
If the Account Holder / Account Owner loses access to their own account (personal issues, leaving the company without a handover, unavailable 2FA), the entire developer account can become unmanageable — even while its published apps stay live and working for end users.
Practical recommendation: for organizations, designate at least one Admin who’s fully independent of the Account Holder (a different device for 2FA, a different email), so an emergency scenario where the owner is unreachable doesn’t paralyze account management.
How ownership transfer works
Apple
Transferring the Account Holder role is a formal process through the Account section in Apple Developer, requiring confirmation from both the current and the new role holder. It can only be initiated by the current Account Holder, or in some cases through a support request with documented proof of authority (e.g., when the prior responsible person has left and can’t be reached).
Google Play
Transferring Account Owner happens through “Transfer ownership” in account settings, also requiring confirmation from both parties. For organization accounts, the process is usually simpler than for personal accounts, since authority to represent the organization can be documented rather than relying solely on confirmation from one specific individual.
FAQ
Can an Admin do everything an owner can in day-to-day work?
Practically, yes — most operational tasks (app management, team management, publishing) are equally available to Admins. The difference shows up in rare but critical situations: signing agreements, ownership transfer, final membership decisions.
What happens if the sole Account Holder leaves the company without a handover?
You’ll need a formal request to Apple or Google support with proof of authority to represent the organization — the process can take significant time and may require legal documentation.
Should the Account Holder/Owner role be tied to a dedicated, non-personal email address?
Yes — for organizations, it’s often sensible to tie the owner role to a shared organizational account (controlled by multiple trusted people) rather than a specific employee’s personal email, since that employee might leave the company.
This article is independent and not affiliated with Apple Inc. or Google LLC. For official information, see developer.apple.com/support/roles and support.google.com/googleplay/android-developer.
Related: Adding Team Members in Apple Developer & App Store Connect · Google Play Console Roles and Permissions · Apple Developer Account Locked: How to Recover Access