1. Managed publishing is Play Console's hold-until-you-go-live control for an app that is already on Google Play. Under standard publishing, approved changes go live as soon as Google finishes review. With managed publishing on, Play Console Help holds those same changes until you actively publish them from Publishing overview. Use it when a go-live time matters — an ad campaign, a launch event, or a version that must land together with store-listing or distribution edits. Play also recommends it for apps that see extended review, including apps from new developer accounts. Primary sources: Play Console Help, "Control when app changes are reviewed and published" (https://support.google.com/googleplay/android-developer/answer/9859654) and "Publish your app" (https://support.google.com/googleplay/android-developer/answer/9859751).
2. Turn it on in Play Console: select the app → left menu Publishing overview → Managed publishing status → Turn on managed publishing → Save. You should see a green check and the message "Managed publishing is turned on" until you turn it off. You can toggle it while a change is still in review. You need one of these permissions: Release to production, exclude devices, and use Play App Signing; Release apps to testing tracks; Manage testing tracks and edit tester lists; Manage store presence; or Admin (all permissions). Play Console Help states the app must already be available — you cannot use managed publishing when publishing an app for the first time.
3. After it is on, prepare and submit releases as usual (Play Console Help, "Prepare and roll out a release", https://support.google.com/googleplay/android-developer/answer/9859348). Submitted items appear under Changes in review, then move to Changes ready to publish once approved. They stay held until Publishing overview shows Changes in review empty, every item is listed under Changes ready to publish, and you click Publish changes (the confirm step may read Review and publish). After you confirm, Help says the update is published on Google Play within a few minutes and becomes visible to users. One Publish changes click releases every ready item together — you cannot publish a subset of the queue.
4. Staged rollouts still apply, but they are not a substitute for that Publish click. Play Console Help lists "full and staged roll-outs of your releases" among the changes managed publishing holds, with one explicit exception: increasing an existing staged roll-out to 100% is not held and can go out without that extra Publish step. Internal test tracks are also outside managed publishing: in most cases an App Bundle uploaded there is available immediately (Help documents two caveats — a first-ever internal rollout, and a follow-up after a rejection, both still need review). Country targeting changes that affect production or testing tracks are listed on Publishing overview and are held; do not confuse that with a staged rollout's optional country filter under Production → Releases (Play Console Help, "Release app updates with staged rollouts", https://support.google.com/googleplay/android-developer/answer/6346149).
5. Do not confuse managed publishing with a draft release or with Changes not yet sent for review. A draft on Production or a testing track has not been sent for review. Changes not yet sent for review lets you choose when to click Send for review. Managed publishing starts after approval: it chooses when already-approved changes go live. Play Console Help treats those as two complementary controls. If a previous update was rejected, later edits are not auto-sent — you must return to Publishing overview and click Send for review.
6. Common mistakes: (a) review is approved but production users and the store listing never show the new build — the change is sitting in Changes ready to publish because nobody pressed Publish changes; (b) treating a saved draft as "held by managed publishing" — drafts were never submitted; (c) assuming a later staged-percentage bump or country-availability tweak always waits for Publish — raising an existing staged rollout to 100% is a documented exception and is not held; (d) submitting extra changes while review is open, which Help says restarts the review SLA from the latest submission and disables Review and publish until that review finishes; (e) expecting internal-test uploads to wait in the same Ready to publish queue — they generally do not.
7. Plan only from documented review windows: processing can take a few hours or up to seven days (longer in exceptional cases). Play Console Help's own tip is a buffer of at least a week between submit and the moment you intend to press Publish. Help does not publish a deadline for how long an item may sit in Changes ready to publish; the hold lasts until you publish, or until you move the change back to Changes not yet sent for review (which can trigger another review). The same workflow is covered in Play Academy, "Choose when your app updates are published with Managed publishing."