Can Two Developers Share One Google Play Account?

Yes, but not by sharing a login.

Google Play is built for this. One person registers and owns the account. Everyone else is invited by email, signs in with their own Google account, and gets only the permissions you grant them [1].

Passing one password around does the opposite. It looks simpler on day one and creates a mess you cannot easily undo later.

Two people, one account, separate logins. Only one of you can be the owner.

Two very different things, and people use the phrase for both.

Sharing a login means both of you type the same email and password. Google has no idea which of you did what.

Sharing an account properly means one owner invites the other as a user. You each sign in as yourself. Every action is logged against a person.

Only the second one is actually supported by Google, and the rest of this post is about doing it that way.

How do you add a second developer?

About a minute, and all you need is their email address.

In Play Console, open Users and permissions.
Enter the email address you want to invite.
Set an access expiry date if you want one. This is optional.
Tick the permissions they need, and leave the rest off.
Click Invite user [1].

Permissions are not all or nothing. You can grant view app information, manage store presence, release to production, reply to reviews, or view financial data, and switch off everything else [1].

Google does not publish a limit on users, so a small team is fine.

What the other person has to do

They get an invitation by email. To accept it, they sign in with a Google account using the same address you invited [1]. If they do not have one on that address, they can create a Google account against an email they already use.

Watch the clock here. The invitation expires after 30 days. If they do not accept and sign in inside that window, it lapses and you have to send it again [1].

How to tell it worked

Two signals. You get a confirmation email, and their entry in the user table switches to Active [1].

If the status still says invited, they have not signed in yet. Nudge them rather than sending a second invite.

Changing your mind later

Click anywhere on their row in the user table to open their details [1]. From there you can add or remove permissions, change the expiry date, or remove them from the account entirely.

That last one is the point of doing it this way. Removing someone is one click, and it takes effect immediately.

Who can do what?

Three levels, and the difference between them is smaller than most people expect [1].

Level	Invite and remove users	What it is
Account owner	Yes	The first registered account. Full access. Only one exists.
Admin	Yes	Access to all apps or specific ones, and can manage permissions.
User	No	Whatever access you grant, and nothing more.

The line that matters is the first one. The account owner is the first registered account, and that position does not move. You can promote someone to admin, which is close to equal in daily use, but ownership stays where it started.

Three reasons, and the third one is the expensive one.

You lose the audit trail. With one login, Play Console cannot show who shipped a release or who edited the listing.

You cannot revoke access cleanly. Removing an invited user is one click. Undoing a shared password means changing it, and hoping nobody saved it.

The account belongs to one identity. It is registered to the owner, and the ID checks belong to that person or that company. If you fall out, the account does not split down the middle. One of you has it.

Should we register as personal or organization?

Decide this before you register. It shapes what comes after.

A personal account is for one person. Google describes the audience as a student, hobbyist, or amateur developer. You can still earn money and still invite other people [2].

An organization account is required if you are engaged in commercial, industrial, professional or governmental activity. It is also required for financial products, health apps, apps using VpnService, and government apps [2].

The catch: an organization account needs a D-U-N-S number [2]. Those take time to get, so start early if you need one.

If two of you are building something commercial together, an organization account is usually the honest answer. It also puts the account in the company name, not in the name of whoever signed up first.

If you are registering a personal account instead, pick the person who will still be around in two years. Moving it later means an app transfer, and that costs you the tester list.

Does a second developer change the 12 testers requirement?

No. Adding people to your Play Console account does nothing to the testing requirement.

Personal accounts created after 13 November 2023 still need 12 testers opted in for 14 continuous days before applying for production access [3]. Two people on the account is still one account, one app, twelve testers.

The other developer can opt in as a tester with their own Google account, and they count as one. But that is one twelfth of the total. A testing record built mostly from the people who wrote the app is a thin one. Our guide on using your own phone as a tester covers why.

What if we split up later?

This is the part worth reading before you need it.

Apps can be transferred between developer accounts. The original owner submits the request, and the target developer reviews and approves it [4]. Both accounts must be registered and active, and you need the target account’s registration transaction ID. Google replies to transfer requests within two business days [4].

Now the part that catches closed testing developers.

Test groups do not transfer. Google states plainly that you must recreate any closed testing groups on the receiving account [4]. Your tester list does not come with the app.

So if you transfer mid-test, you rebuild the list and your testers opt in again on the new account. Earnings and payout reports do not transfer either, and permissions for integrated services are not carried over [4].

If a transfer is on the cards and you are partway through a closed test, finish the test first. Moving the app resets the work, not the policy.

Frequently asked questions

Yes, by inviting the second person as a user in Play Console rather than sharing a password. Each of you signs in with your own Google account and the owner controls what the other can do.

Google does not publish an outright ban on it, but everything about how the account works assumes you will not. It is registered to one identity, and invitations exist so you do not need to share anything. In practice you lose the audit trail and you cannot revoke access cleanly.

Can there be two account owners?

No. The account owner is the first registered account and there is only one. You can make someone an admin, which allows them to invite and remove users, but ownership does not duplicate.

How many people can I add to a developer account?

Google does not publish a maximum. Permissions are set per person, so you can add several people and give each one only what they need.

What if the person I invited never accepts?

The invitation expires after 30 days and you have to send a new one. Until they accept and sign in, their status stays as invited and they have no access at all.

Do we need an organization account if there are two of us?

Not automatically. It depends on whether the work is commercial rather than on how many people are involved. An organization account requires a D-U-N-S number, so allow time for that.

Does adding a second developer reduce the 12 testers I need?

No. The requirement is per app and does not change with the number of people on the account. The other developer can be one of the twelve if they opt in with their own account.

Do closed testing groups transfer with an app?

No. Google states you must recreate closed testing groups on the receiving account after a transfer, so your tester list has to be rebuilt and testers opt in again.

If the testers are the part you are stuck on

Option 1: verified testers assigned to you

Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.

Testers assigned within 6 hours, so your 14 days start today rather than after a week of asking.
They open your app daily and stay active for the full period.
Anyone who goes inactive is replaced.
A feedback report at the end, plus pre-filled answers for the 10 production access questions.
100% production access or your money back.

More than 10,000 apps have reached production this way. Submit your app to start.

Option 2: join a free Pack of 16

If you would rather trade time than money, the Testers Community app puts you in a pack of 16 developers. Everyone tests each other’s apps for 16 days, opening every app daily and leaving feedback. Inactive members get replaced.

Either way, read the full requirements before you start, and our guide to inviting testers properly so nobody falls at the opt-in step. If you are budgeting the launch, the $25 fee covers unlimited apps on a single account.

Can Two Developers Share One Google Play Account?