Connect a personal channel
Section titled “Connect a personal channel”Open Settings → Integrations → YouTube and connect the intended Personal Channel through the account authorization flow. Return to Stago and check the connected channel name.
If the connection isn’t available, ask the workspace owner or support to check service availability. Users don’t need to configure the application’s server credentials themselves.
Shared organization channel
Section titled “Shared organization channel”Connect a team channel in Settings → Organization. A personal connection isn’t automatically an organization connection. Confirm which channel the project will use before publishing.
Prepare the approved release
Section titled “Prepare the approved release”Approve the intended video draft, add it to the release, and select it as Main Video where required. Project approval and permission to publish are separate; a reviewer can have one without the other.
Open the project’s YouTube publishing controls. Check Title, Description, Tags, category, language, privacy, and thumbnail. Review the offered audience, license, embedding, and statistics options according to the content you intend to publish.
Publish or schedule
Section titled “Publish or schedule”Choose the intended privacy setting. For scheduling, enable Schedule This Publish, choose the date/time, and inspect the final visibility result before submitting. Check the time zone and intended channel, then confirm the action.
Wait for upload and processing to finish. Open the resulting YouTube link to verify the video and privacy state. A queued request isn’t proof that the video is already public.
Changes and failures
Section titled “Changes and failures”Use the available publishing controls to inspect or update an existing publication. Republish only when you intend to create or restore the publication; read the dialog’s Republish behavior explanation.
If publishing fails, check channel authorization, publishing permission, the approved main video, and the visible provider message. Don’t create several publish jobs to troubleshoot a single pending one.