Managed publishing is a switch on the Publishing overview page in Play Console. When it is on, changes that Google approves don't go live automatically; they wait until you click Publish changes. When it is off, approved changes are published as soon as the review finishes.
That's useful when you want to pick your launch moment. During a closed test, though, it is also a common reason why an approved change seems to do nothing. Here's how it works and when to use it.
Where it lives and how to switch it
Everything happens on one page. Google's managed publishing help page describes the steps:
- Open Play Console and select your app.
- Go to Publishing overview.
- Find the Managed publishing status section.
- Click Turn on managed publishing, then Save.
When it's on, the section shows a green check mark and the message "Managed publishing is turned on". Turning it off works the same way from the same section.
Google says you can change the setting "at any time, including while your change is being reviewed."
The flow with managed publishing on
With managed publishing on, a change passes through three stages on the Publishing overview page:
- Changes not yet sent for review. Everything you've saved (a release, new countries, a store listing edit) collects here. Nothing is reviewed yet.
- In review. After you click Send for review, Google checks the changes. Google says this "can take a few hours or up to seven days (or longer in exceptional cases)" and recommends a buffer of at least a week.
- Changes ready to publish. Approved changes wait here. Click Publish changes and, according to Google, "your update will be published on Google Play within a few minutes."
With managed publishing off, step 3 disappears: approval and publication happen together.
The first step applies either way. Saving a change is never the same as sending it. If you forget Send for review, nothing is reviewed and your testers see no change. That mistake is covered in detail in why your tester invite isn't approved.
What managed publishing holds back
According to Google, managed publishing delays:
- full and staged rollouts of your releases
- store listing changes
- app content changes
- changes to your app category
- pre-registration updates
What it doesn't hold back
Some changes are published without waiting, even with managed publishing on. Google lists, among others:
- increasing an existing staged rollout to 100%
- release notes updates
- device exclusion rule changes
- changes to the membership of an email list or Google group
- price changes and in-app product changes
The membership item matters for closed testing. If someone joins the Google Group you've added to your closed track, or you add an address to an email list that's already on the track, managed publishing doesn't delay that. Adding a new list or group to the track is a track change, so treat it as something to send for review.
Internal testing is different
Google says internal test tracks "are not covered by Managed publishing", so internal changes are usually available right away. There are exceptions, such as when your app's very first release is on the internal track or a previous submission was rejected; then a review is needed. Our comparison of internal, closed and open testing explains why the internal track doesn't count toward the 12-tester rule.
Should you use it during a closed test?
For most developers running their first closed test, leaving managed publishing off is simpler. The goal is to get the track live and testers opted in as early as possible, and every extra manual step is one more thing to forget.
Turn it on when timing actually matters, for example:
- You want several changes (a new build, updated listing text, new screenshots) to go live together.
- You need to line up an update with a backend change or an announcement.
- Several people work in the same Play Console and you want one person to decide when things go live.
If you turn it on, make a habit of checking Publishing overview after every submission. "Approved" doesn't mean "live" until you've clicked Publish changes.
The classic symptom: approved, but testers see nothing
A typical scenario: you upload a fix to your closed track, send it for review, and get approval. Your testers still have the old version, or a newly added country still can't see the test.
Check in this order:
- Publishing overview: is anything sitting under Changes ready to publish? If so, managed publishing is on. Click Publish changes.
- Changes not yet sent for review: if the change is still here, it was never sent. Click Send for review.
- Still in review: wait. Reviews can take up to seven days, sometimes longer.
- Published, but testers don't see it: give the Play Store some time to refresh and ask testers to check for updates.
If you're setting up the track for the first time, our step-by-step track setup walks through every step before this one.
Managed publishing and your 14 days
Managed publishing doesn't change how the 14 days are counted. The requirement for personal accounts created after November 13, 2023 is still at least 12 testers who have been opted in continuously for 14 days when you apply for production access. What managed publishing can do is delay the moment your track (or your tester changes) actually goes live. If your closed track is waiting under Changes ready to publish, testers can't opt in yet, and the clock hasn't started for anyone.
So if you turned it on while preparing your test, either publish promptly after each approval or switch it off until testing is underway.
Key takeaways
- Managed publishing is controlled from Publishing overview > Managed publishing status.
- On: approved changes wait under Changes ready to publish until you click Publish changes.
- Off: approved changes go live straight away.
- Changes to the membership of an email list or Google group aren't held back. Internal testing generally isn't covered.
- You still have to click Send for review either way.
If you're using GoPlayTester, our setup guide shows the exact Play Console steps, including sending the change for review. Once your track is live, we can supply 12+ real testers for the 14 days; order here when you're ready.
