# Connect the right YouTube channel to a scheduler

**Choose the channel, not just the Google email address.** One Google Account can manage a personal YouTube channel
and Brand Account channels. Confirm the intended channel before authorizing a scheduler, then check the channel it
actually saved. Being invited to YouTube Studio is not the same as being able to authorize a YouTube API integration.

Checked on October 31, 2026 against YouTube Help, Google Account Help and the YouTube Data API documentation.

## Personal channel, Brand Account and Studio access are different

A Google Account is the sign-in. A YouTube channel is the publishing identity. A Brand Account lets multiple people
manage its linked channel using their own Google Accounts, without a shared password. YouTube explains these
[account and channel arrangements](https://support.google.com/youtube/answer/4642409?hl=en) and how to
[check whether your channel uses a Brand Account](https://support.google.com/youtube/answer/7286468?hl=en).

There are two different permission systems:

| Access | What it means for connecting a scheduler |
|---|---|
| Your own personal channel | Sign in with the Google Account that owns that channel, then verify the scheduler saved that channel. |
| Brand Account owner or manager | Use your own Google sign-in with the appropriate Brand Account access and select the intended channel. Brand Account ownership and management are separate from Studio roles. |
| YouTube Studio channel permissions | Invited owners, managers and editors have different native capabilities, but these invitations do not grant access to YouTube APIs. A Studio invitation alone is not enough for an API-based scheduler. |

YouTube's [channel-permissions reference](https://support.google.com/youtube/answer/9481328?hl=en&co=GENIE.Platform%3DDesktop)
says Managers can create, upload, publish and delete content, while Editors can upload and publish but cannot manage
permissions or delete published content. It also explicitly lists **YouTube APIs as unavailable to invited users**.
Even a role named Owner in Studio is not a promise of API access through that invitation.

For a channel already using native Studio permissions, the owner opens **YouTube Studio → Settings → Permissions →
Invite**, enters the person's email, selects the role under **Access**, then clicks **Done**. The recipient accepts
the invitation; YouTube says it expires after 30 days. Brand Accounts still using the older permission system must
first migrate to channel permissions to use this invitation path. That is a separate team-access decision, not a
scheduler fix: do not migrate merely to make a missing API channel appear. Do not share the owner's password or grant
an unnecessarily powerful role. YouTube separately documents
[Brand Account roles and their risks](https://support.google.com/youtube/answer/4628007?hl=en).

## Connect a personal or Brand Account channel

1. **Identify the destination in YouTube first.** On a computer, sign in to YouTube, select your profile picture,
   choose **Switch account**, then select the channel. Confirm its name and handle. YouTube's
   [channel-switching instructions](https://support.google.com/youtube/answer/3046356?hl=en&co=GENIE.Platform%3DDesktop)
   explain that you use one channel at a time; switching there does not switch an already connected scheduler.
2. **Record the channel ID when you can.** The primary owner can open **Settings → Advanced settings** in YouTube to
   see the channel ID, as described in [YouTube's ID guide](https://support.google.com/youtube/answer/3250431?hl=en).
   This distinguishes channels with similar names. A display name or a Google email alone is not enough.
3. **Start an additional YouTube connection in the scheduler.** Use its add-channel workflow when adding a different
   channel. Use reconnect only for the existing channel you intend to repair. If the tool only offers replacement,
   do not overwrite a working personal connection to add a brand channel.
4. **On Google's sign-in and consent pages, use the right Google Account and channel.** Select the intended personal
   or Brand Account channel when the flow offers that choice. If it is missing or the displayed identity is wrong,
   cancel and diagnose the access problem below rather than approving another channel as a substitute.
5. **Read the requested permissions before allowing access.** Google's
   [OAuth documentation](https://developers.google.com/youtube/v3/guides/authentication) explains that scopes determine
   which operations the app may perform. Signing in to the scheduler with Google and granting it YouTube access are
   different authorizations; one does not prove the other.
6. **Check the returned connection before preparing a publishing plan.** Compare the saved channel name, handle and
   channel ID with your intended destination. For each additional channel, repeat the add-channel flow and keep a
   distinct destination. Connection success is not a video upload, a publishing approval or proof that a scheduled
   video is live.

## Does authorization give the scheduler access to all my channels?

**Do not infer that from the Google email or a broad permission label.** There are three separate questions:
which Google Account signed in, which channel the authorization represents, and which actions its scopes permit.
A channel visible in your YouTube account switcher is not automatically a usable destination in a scheduler.

For an ordinary channel integration, the app can identify the authorized channel through
[`channels.list` with `mine=true`](https://developers.google.com/youtube/v3/docs/channels/list). That method's
`managedByMe` and `onBehalfOfContentOwner` options are specifically for YouTube content partners using a linked CMS
account. They are not a shortcut that lets every scheduler enumerate or publish to all channels you manage.

Read the scheduler's connection model and Google's actual consent screen. If you need two channels, verify two
explicit saved destinations rather than assuming that one consent made every channel available. Review the app's
access in [Google Account's linked-app controls](https://support.google.com/accounts/answer/13533235?hl=en).
Removing access can stop features that use that authorization; it is not a harmless first troubleshooting step for
one missing channel when other connections still work.

## Why is my channel missing, or why did the wrong one connect?

Work through these checks without deleting, transferring or replacing another channel:

- **Wrong Google Account:** check the email on Google's account chooser. A Brand Account has no separate password;
  use a Google Account with access to it. In the Google Account's Brand Accounts section, look under **Your Brand
  Accounts** and confirm you are using the intended Google sign-in.
- **Studio invitation only:** if you can work in Studio but cannot select the channel for API access, check which
  permission system granted that access. Invited Studio users cannot use YouTube APIs. For native work, YouTube
  says to try switching at `studio.youtube.com` when a delegated channel is absent from the ordinary switcher.
  For an API connection, the appropriate channel owner must handle authorization through the scheduler's supported
  flow; an extra Studio invitation does not remove this restriction.
- **Brand Account access missing:** YouTube's switching guide says a linked Brand Account channel may be missing
  because the current Google Account is not listed as a manager. Have the existing owner review the Brand Account's
  **Manage permissions** list. Do not change ownership, opt out of Studio permissions or migrate the channel merely
  to experiment with a connector.
- **An email address appears instead of a channel name:** YouTube says this can be a viewer identity without a
  channel. Choose the existing channel's account rather than creating a new empty channel to stand in for it.
- **The tool does not support channel switching:** YouTube's
  [third-party-tool troubleshooting](https://support.google.com/youtube/answer/3046478?hl=en) says some tools use the
  default channel. If that applies, follow the default-channel path below; do not assume every OAuth flow ignores
  its own channel chooser.
- **The tool still returns the wrong identity:** cancel that attempt, preserve the good connection and use the
  tool's documented additional-channel or channel-specific repair path. Changing the selected channel in YouTube
  afterwards does not retarget an existing saved connection or its drafts.

### Set a default channel only when the tool needs it

For tools without channel switching, YouTube documents this
[default-channel setting](https://support.google.com/youtube/answer/6019090?hl=en): on a computer, sign in to YouTube,
switch to the intended channel, open advanced account settings, then under **Default Channel** select **Use this
channel … when I sign in to my … account** and save. This also affects other tools that use the default, so consider
those connections before changing it. Then start a fresh connection attempt and inspect the returned channel.
The setting is not permission to silently replace a different saved destination.

## What you can do in Flaghand today

**YouTube connections are not generally available in Flaghand's public connector setup.** The current rollout is
workspace-specific. If your workspace does not expose YouTube in its supported connection options, use YouTube's
native tools or a scheduler that currently supports your channel. There is no public Flaghand YouTube setup recipe
or availability date promised here.

The live [Flaghand setup documentation](https://app.flaghand.com/docs/setup.md) and
[connection API reference](https://app.flaghand.com/docs/api) describe its existing destination model: list saved connections,
match the intended active account, and use its `con_…` ID as the draft's `connection_id`. A reconnect can carry an
explicit `connection_id` and is for that pinned account, not a way to add a different account. Those generic fields
are not evidence that YouTube is enabled for every workspace.

For an enabled workspace with an existing YouTube connection, this is an **identity check, not a connect or posting
recipe**:

```sh
flaghand connections list --json
```

Inspect only the intended workspace's returned connections. Match `platform`, `status`, `external_id` (the channel
ID), name and handle; do not choose the first account or the most recently connected one. Keep that exact connection
ID for any later draft that the workspace actually supports. An unavailable destination is a problem to resolve,
not a reason to fall back to another personal or brand channel.

For MCP, `listConnections` provides the same saved destinations. An agent may draft, check and request the owner's
approval where supported; **agents never approve, schedule or post**. Only the owner approves the exact plan through
Flaghand's own approval request with a passkey. Connecting Google does not replace that decision. See
[how owner-approved agent publishing works](/docs/guides/let-an-ai-agent-post-safely).

## Sources

- YouTube: [Manage YouTube channels](https://support.google.com/youtube/answer/4642409?hl=en),
  [check for a Brand Account](https://support.google.com/youtube/answer/7286468?hl=en), and
  [Brand Account owners and managers](https://support.google.com/youtube/answer/4628007?hl=en).
- YouTube: [Channel permissions and API exclusions](https://support.google.com/youtube/answer/9481328?hl=en&co=GENIE.Platform%3DDesktop),
  [switch channels](https://support.google.com/youtube/answer/3046356?hl=en&co=GENIE.Platform%3DDesktop), and
  [find the channel ID](https://support.google.com/youtube/answer/3250431?hl=en).
- YouTube: [Third-party tools with Brand Accounts](https://support.google.com/youtube/answer/3046478?hl=en) and
  [set a default channel](https://support.google.com/youtube/answer/6019090?hl=en).
- Google: [YouTube OAuth](https://developers.google.com/youtube/v3/guides/authentication),
  [`channels.list`](https://developers.google.com/youtube/v3/docs/channels/list), and
  [manage linked-app access](https://support.google.com/accounts/answer/13533235?hl=en).

[All guides](/docs/guides.md)