You went looking for your closed testing track in Play Console and it is not there. Before you panic, know that this is usually a navigation or setup issue, not a bug. This guide shows you exactly where the track lives and how to fix a missing or hidden track.
Quick answer
Featured answer: The closed testing track is under Testing → Closed testing in Play Console. If it is not showing, you may be looking under the wrong app, lack the right permissions, have not created a closed track yet, or your browser cache is stale. Create the track or check access.
Where the track lives
In the left menu of your app, go to Test and release → Testing → Closed testing. From there you can create a track (Google may show a default "Closed testing – Alpha") and manage releases and testers. Full setup: how to create a closed testing track.
Why it may not show
- Wrong app selected: You are viewing a different app in the account.
- No track created yet: You need to create the closed track.
- Permission limits: Your Play Console user role lacks release access — see console permissions.
- Stale cache: The Console UI needs a refresh.
- App setup incomplete: Required steps are not finished.
How to fix it
- Confirm the correct app is selected at the top of the Console.
- Navigate to Testing → Closed testing and Create track if none exists.
- Check your role/permissions if the menu items are missing.
- Hard-refresh the browser or try another browser.
- Complete outstanding setup tasks flagged in the dashboard.
Tip: Once your track is visible and a release is rolled out, share the opt-in link — see opt-in link setup — and add 12+ testers.
Roles and permissions explained
If entire menus are missing rather than just a single track, the cause is almost always your Play Console user role. Google Play uses role-based access, so a user with limited permissions may not see release or testing sections at all. Common situations include:
- You were invited as a limited user without release management access.
- You are an admin on one app but not on the app you are viewing.
- The account owner restricted testing permissions for your role.
The fix is for the account owner to grant your user the appropriate release permissions in Users and permissions. For a deeper look at how permissions interact with testing, see console permissions and closed testing.
Interface changes and defaults
Google periodically updates the Play Console layout and wording. The closed track has appeared as "Closed testing" and sometimes with a default "Alpha" name. If a guide's screenshots look different from your screen, rely on the menu path — Test and release → Testing — rather than exact labels. And if you genuinely have no closed track yet, simply create one; a fresh app will not always have every track pre-created.
Where the closed testing track lives
Before assuming something is broken, it is worth confirming exactly where the closed testing track should appear, because a great many "it's not showing" reports are simply developers looking in the wrong place. In the current Play Console, closed testing lives under the testing area of your app's release section — typically found by opening your app and navigating to Test and release, then Testing, then Closed testing. The interface groups the release ladder together: internal testing, closed testing, and open testing all sit near one another, which is convenient but also a source of confusion if you land on the wrong one.
If you have navigated to the right place and still do not see what you expect, the issue is usually one of a small set of causes: you are looking at the wrong app, a required setup step is incomplete, the interface has been updated and moved things slightly, or a permissions limitation on your account is hiding the section. Each of these is quick to check, and knowing them prevents a frustrating hunt through the console.
Common reasons the track seems missing
The most frequent explanation is simply navigation — the section exists but you have not found it, often because the console layout differs from an older tutorial you are following. Google updates the console periodically, so screenshots and menu names in guides can lag behind reality. Trust the current structure: look under the testing group of the release area rather than a specific labeled button from an old walkthrough.
Other reasons include being in the wrong app entirely when you manage several, an incomplete app setup where prerequisite steps gate access to certain sections, and account permission limits if you are a member of someone else's developer account without full access. If the track genuinely will not appear, systematically rule these out: confirm the app, complete outstanding setup tasks shown on your dashboard, and verify your account has the necessary permissions.
Creating the track if it does not exist yet
Sometimes the track is not showing because you have not actually created a closed testing release yet — the section is there, but it is empty until you set one up. To create it, navigate to Closed testing, create a new track or use the default one, and prepare a release by uploading your signed app bundle. Once you have a release and a tester list configured, the track becomes an active, populated part of your console. For the complete walkthrough, see how to create a closed testing track.
Do not confuse an empty track with a missing one. Many developers expect a fully configured track to appear automatically, when in fact they need to create the release themselves. If the section is present but shows nothing to test, that is your cue to set up a release, not a sign that anything is broken.
Avoiding the wrong-track trap
The most costly version of this confusion is not that the track is missing, but that a developer uses the wrong one — setting up internal testing while believing it is closed testing. Because the tracks sit together and look similar, this mistake is easy to make and devastating to your timeline, since only closed testing counts toward the production requirement. Always confirm you are on the closed track specifically before recruiting testers and starting your 14-day window. A ten-second check of the section heading can save you two wasted weeks. See internal vs closed testing to be sure you are in the right place.
Account permissions and access levels
If the closed testing track genuinely will not appear even though you are in the right app, one under-appreciated cause is your account's permission level. Play Console supports multiple users on a single developer account, each with different access levels, and a user without sufficient permissions may not see certain sections — including testing tracks. If you are working within someone else's developer account, or if your organization has granted you limited access, this can be the invisible reason a section seems missing.
The fix is to check your access level and, if necessary, ask the account owner to grant the permissions you need. This is worth ruling out early when the usual navigation checks come up empty, because no amount of clicking will reveal a section your account is not permitted to see. For solo developers who own their own account, this is rarely the issue, but for team members and agencies it is a common and easily overlooked explanation. Confirming you have the right access turns a baffling "missing" section into a simple permissions adjustment.
Browser, cache, and interface glitches
Occasionally the closed testing track is missing not because of your configuration or permissions, but because of a transient interface glitch. The Play Console is a complex web application, and like any such tool it can occasionally render incompletely, cache an outdated view, or behave oddly in certain browsers. Before assuming a deeper problem, try the simple remedies: refresh the page, clear your browser cache or try an incognito window, switch to a well-supported browser like Chrome, and ensure you do not have an extension interfering with the page. These quick steps resolve a surprising number of "it's not there" reports that turn out to be display issues rather than real configuration problems. If the section reappears after a refresh or a browser switch, you have found your answer — and saved yourself a needless troubleshooting session.
Incomplete setup that hides the track
Sometimes the closed testing track appears absent because a prerequisite step in your app's setup is incomplete, and Google gates certain sections until you have provided the basics. A brand-new app with only minimal information filled in may not present every release option in the way a fully set-up app does. If you have just created your app and immediately gone looking for closed testing, it is worth confirming that you have completed the initial setup steps the console prompts you through — app details, and the basic declarations that establish your app in the system.
Working through your app's setup checklist often reveals that the track was never truly missing; it simply becomes fully accessible once the prerequisites are met. The Play Console tends to guide you through required steps in sequence, and skipping ahead to look for a specific track can create the impression that something is absent when it is really just waiting on an earlier step. Completing the outstanding items on your dashboard is therefore a good early move whenever a section seems to be missing.
This ties back to a theme that runs through the whole Play Console experience: the console rewards completing things in order. Front-loading your setup — app details, forms, and declarations — not only unlocks the sections you need but also prevents last-minute blockers when you apply for production. If your closed testing track seems to be hiding, treat it as a prompt to finish your setup rather than a bug, and the track will typically appear as the prerequisites fall into place.
Key takeaways
- Closed testing lives under Test and release → Testing → Closed testing.
- Most "missing" reports are navigation — trust the current layout, not old tutorials.
- Check the right app, complete setup tasks, and verify permissions if it truly will not show.
- An empty track is not a missing track — you may need to create a release.
- Confirm you are on the closed track, not internal, before starting your window.
Frequently asked questions
Where is closed testing in Play Console?
Under Test and release → Testing → Closed testing.
Why might the track not appear at all?
Common causes are looking at the wrong app, incomplete setup steps, insufficient account permissions, or a browser glitch. Rule these out before assuming a deeper problem.
Is an empty track the same as a missing one?
No. The section may be present but empty because you have not created a release yet. Set up a closed testing release and it becomes active.
Do I have to create the track myself?
Often a default closed track exists, but you can create one if needed.
Why are testing menus missing entirely?
Your user role may lack release permissions. Ask the account owner to adjust it.
Could it be a browser issue?
Yes — refresh or switch browsers to rule out cache problems.
What next after the track shows?
Upload a release, add testers, share the opt-in link, and start your 14 days.
Why do I see a track called "Alpha"?
Google sometimes labels the default closed track as "Closed testing – Alpha." It is still the closed track that counts toward production access.
Do I need to publish the app first?
You do not publish to production first — but you must create the app, upload a release to the closed track, and roll it out before testers can opt in.
Conclusion
A missing closed testing track is nearly always the wrong app, a track you have not created, permissions, or cache. Navigate to Testing → Closed testing, create the track, and confirm your access. Ready to fill it with real testers? Submit your app today.