Tuesday's class finishes, the recording lands on your YouTube channel a few minutes later, and it's marked Private — meaning nobody, not even the cohort who just paid for the session, can watch it yet. That's not a bug and it isn't stuck. It's the one deliberate pause between "recorded" and "published," and clearing it takes about four clicks once you know where to look.
What's actually happening
RecordFlow uploads every recording to your channel as Private, and that default isn't configurable — not a setting you can flip to skip the step. The people on a Zoom call consented to being recorded, not to being published on a channel with an audience, so a course-creator automation shouldn't quietly make that call on their behalf. Publishing is a decision you make per session, with the context only you have (is this cohort paying for replay access, or is this a trailer meant to bring in new students?), so it stays yours to make in YouTube Studio, not baked into the upload.
Once a video is sitting in your channel, YouTube gives you three visibility states to choose from, and the definitions matter more than they look:
Private vs. Unlisted vs. Public
- Private — "can only be seen by you and whomever you choose." Won't show up on your channel page or in search. This is where every RecordFlow upload starts.
- Unlisted — "can be seen and shared by anyone with the link," and the viewer doesn't need a Google account to watch it. It won't appear on your channel's Videos tab or in YouTube search results either — normally the link is the only way in (one exception below).
- Public — visible to anyone on YouTube, discoverable in search and on your channel.
(Source: Change video privacy settings, YouTube Help.)
For a paying cohort, Unlisted is usually the fit: drop the link into your course platform or a weekly email, and a student who's never touched YouTube before can click straight through with no sign-in prompt.
Public makes sense when the recording itself is the marketing — a free workshop replay or a course trailer you want to be found.
Private is where a recording should stay if it's genuinely not meant for anyone but you — which, for a class replay, is rare, but worth remembering when a session veers into something more personal than the rest of the series.
How to change a recording's visibility
- Sign in to YouTube Studio with the Google account connected to the channel RecordFlow uploads to.
- Click Content in the left sidebar — every video on the channel is listed here, RecordFlow's uploads included, each showing its current visibility.
- Find the recording (RecordFlow titles it with the session name and date, so a term's worth of classes sorts the way an actual course list would) and click the down-arrow under Visibility next to it.
- Choose Unlisted or Public, then click Save. It's a metadata change, not a new upload — no reprocessing wait like the original video went through.
Do this once per session as each class wraps, or batch it weekly from the Content list if you'd rather publish a term's worth of replays on a fixed schedule.
What to check before you publish
How RecordFlow fits
RecordFlow's job stops at the upload: connect your Zoom account to your YouTube channel once, and every new class or session recording lands there automatically, titled and dated, Private by default. Everything after that — Unlisted for the cohort, Public for a trailer, or left Private because a session isn't meant for wider viewing — is a decision you make in YouTube Studio, session by session, with full context RecordFlow doesn't have and shouldn't guess at. YouTube only ever receives the video itself; if you also want the audio track, chat log, and transcript preserved, a connected Drive course library keeps the rest of the session archived alongside the channel upload — YouTube is where students watch the replay, not where the full session record lives.
Publish class replays on your terms.
RecordFlow uploads every Zoom class recording to your YouTube channel automatically, Private by default. You decide when and how each one goes live. Free during beta, no credit card.
