Play Console lets you add closed testers in two ways: an email list you manage inside Play Console, or a Google Group whose members can all join the test. Email lists are simplest for a small, fixed group of people you know. Google Groups are easier when the group changes often, when several apps share the same testers, or when someone else manages the tester roster.
How each option works
Email lists
You type or upload tester email addresses into a list in Play Console, then attach that list to your closed track on its Testers tab. Each address must be a Google account or a Google Workspace account (Set up a test).
Limits Google documents:
- up to 200 email lists per developer account
- up to 2,000 users per list
- up to 50 lists per track
Lists are reusable across apps in the same developer account, so one "friends and family" list can serve several closed tests.
Google Groups
Instead of individual emails, you enter a group address such as [email protected]. Google is explicit about the effect: "Only members of the specified Google Groups can join your test."
Membership is managed in Google Groups, not in Play Console. Add someone to the group and they can join; remove them and they lose access.
Side by side
| Email list | Google Group | |
|---|---|---|
| Where you manage testers | Play Console | Google Groups |
| Adding a tester | Edit the list in Play Console | Add them to the group |
| Good for | Small, stable groups you know | Changing or shared groups |
| Who can manage it | People with access to your Play Console | Group owners and managers |
| Reuse across apps | Yes, within your developer account | Yes, any app that adds the group |
| Testers see each other's emails | No | Depends on the group's settings |
When an email list is the better choice
- You have a fixed set of 12 to 20 people: friends, colleagues, a class.
- You want everything in one place, without creating a group.
- You want to see exactly which addresses are invited, right in Play Console.
The catch is upkeep. Every time someone gives you a new address, you have to edit the list, and changes to the track may need to be sent for review from Publishing overview before they take effect. Typos are common too. An address with one wrong letter is a tester who can never opt in.
When a Google Group is the better choice
- Testers come and go, and you don't want to touch Play Console each time.
- You run several apps and want the same testers on all of them.
- A community or a testing service manages the members for you.
- You want testers to be able to sign up themselves, if you configure the group to allow it.
The catch is configuration. The tester has to actually be a member of the group with the same Google account they use on their phone. Check the group's privacy settings as well, since some settings can show members' addresses to each other. The details are Google Groups settings rather than Play Console rules, so test with one account before inviting everyone.
Can you use both?
Yes. A track can have email lists and Google Groups at the same time. A common setup is a small email list for yourself and your team, plus a Google Group for wider testers. What matters for the requirement is the number of testers who opt in, not how they were added. If you're unsure what counts, read what counts as an opted-in tester.
Setting it up
- Go to Test and release > Testing > Closed testing and click Manage track.
- Open the Testers tab.
- Choose Email lists and create or select a list, or choose Google Groups and enter the group address.
- Save.
- Go to Publishing overview and send the changes for review. Forgetting this is the most common reason invites don't work; this article explains it.
For the full track setup, see how to create a closed testing track.
Mistakes to avoid with either method
- Wrong account. Ask each tester for the Google account that's signed in to the Play Store on their phone, not their work email or an old address.
- Changing the roster mid-test. Removing a tester from a list or group during the 14 days can break their continuous opt-in. Add people freely, but avoid removing them until you've applied.
- Assuming the list equals opt-ins. Adding 15 addresses doesn't mean 15 testers. Each one still has to open the opt-in link and accept.
Key takeaways
- Email lists: simple, managed in Play Console, best for a small fixed group.
- Google Groups: flexible, managed outside Play Console, best for changing or shared groups.
- You can combine both; only opted-in testers count either way.
GoPlayTester uses a Google Group, so you add one address to your track and our testers join from there. The setup guide shows the exact steps, and you can order here if you need 12+ testers for your 14 days.
