← All Research
YouTube Account Architecture
Brad Stevens · Outsource Access · Google · VidIQ · API
Living map
Research for Brad · July 23, 2026

Your YouTube architecture, without the account confusion

You do not have “one YouTube login.” You have several layers that can each be signed in, signed out, or pointed at a different identity: macOS, Chrome, Google, YouTube, Brand Accounts, VidIQ, and API tokens. This page separates those layers and maps what is confirmed today.

✓ 2 channels confirmed✓ VidIQ sees both! Ownership mapping pending🔒 No permissions changed

The seven layers

Each layer can be in a different signed-in or selected state.
1
Mac userThe local macOS session
→
2
Chrome profileBookmarks, extensions, Sync
→
3
Google AccountThe human login identity
→
4
Brand AccountOptional shared business identity
→
5
YouTube channelThe public content container
→
6
VidIQ channelSelected optimization target
→
7
API grantChannel-bound automation token
Key rule: seeing your face in Chrome does not prove that YouTube, VidIQ, or the active channel is correct. Before every public edit, verify the Chrome profile, Google account, YouTube channel, VidIQ channel, and expected channel ID.

Brad’s current account map

Confirmed facts are green. Relationships requiring owner-screen verification are orange.
⇄
Confirmed channelBrad StevensUC0Hm6gNgLPSNrCDQDiec22w
135 videos observed through VidIQ. Whether this is a personal-account channel or a Brand Account channel remains unverified.
Confirmed channelOutsource AccessUCtuOEc77xh8HISeBIy2-Jiw
428 videos observed through VidIQ. Likely corporate/Brand architecture, but Brand Account name, primary owner, and permission model must be read from Google.
What is already proven: one VidIQ connection recognizes both channel IDs. Research and analytics work can target both. Public editing still requires an authenticated VidIQ web session or a separately verified YouTube OAuth grant.
563

Combined videos observed through VidIQ

2

Distinct public channel identities

0

Ownership or permission changes made during this audit

Why the faces and sign-in messages look contradictory

The icons belong to different identity layers.
💻

macOS user

You are logged into the Mac. This says nothing about Chrome or Google.

👤

Chrome toolbar face

Identifies the Chrome profile. Bookmarks and extensions belong here. A missing bookmark bar may only be hidden, or this may be another profile.

G

Google webpage avatar

Shows which Google account is signed into that website. It can differ from the Chrome profile.

▶

YouTube avatar

Shows the active YouTube channel—not necessarily the Google login or Chrome profile name.

V

VidIQ selector

Shows which connected channel VidIQ will analyze or publish to.

“I see my face, but it says Sign in”

You may be signed into a Chrome profile while the webpage itself is signed out. Chrome and websites keep separate sessions.

“I see my face, but no bookmarks”

The bookmarks bar may be hidden, or Chrome may have opened a different profile. This does not by itself prove that Google or YouTube is signed out.

Personal channel, Brand Account, and Studio permissions

Three different ownership/delegation models that are often conflated.
ModelWhat it isWho controls itAPI implication
Personal YouTube channelChannel directly associated with one Google Account identity.The controlling Google Account.Owner must complete OAuth while acting as that channel.
Brand Account channelBusiness identity that multiple Google Accounts can own/manage without sharing passwords.Primary owner, owners, and managers.Authorize while the real owner is acting as the Brand channel; bind the token to the returned channel ID.
YouTube Studio permissionsNewer delegation roles inside Studio: Owner, Manager, Editor, Viewer, etc.Managed in Studio → Settings → Permissions.Delegates cannot authorize/use YouTube APIs as the channel. Manual access only.
Do not migrate permission systems just to make VidIQ work. VidIQ documents a manager path that can require legacy Brand Account permissions, but changing from Studio permissions could disrupt team access. Prefer authenticating VidIQ and the API with the actual owner first.

How VidIQ fits

Three VidIQ surfaces with different abilities.

VidIQ MCP CONNECTED

Research, transcripts, analytics, title and thumbnail generation/scoring. It sees both channels.

  • No metadata publishing
  • No uploads
  • No YouTube save action

VidIQ web Optimize LOGIN NEEDED

Can edit and publish title, description, tags, and long-form thumbnail for existing connected videos.

  • Persistent interactive browser
  • May require MFA/reauthorization
  • Confirm selected channel before Publish

VidIQ Chrome extension INSTALL/VERIFY

Adds optimization tools inside YouTube Studio and can populate title, description, tags, and thumbnail workflow.

  • Same paid VidIQ account
  • Same persistent Chrome profile
  • Final save remains in Studio
Recommended VidIQ setup: one paid account entitled for at least two channels, both channels listed under the lower-left avatar, and one dedicated headed Chrome profile. Headless Chrome is not VidIQ’s documented production workflow.

Recommended direct YouTube API architecture

Use VidIQ to decide what should change; use guarded channel-bound OAuth to apply approved bulk changes.
A
OA-owned Cloud projectYouTube Data + Analytics APIs
→
B
Two OAuth grantsOne authorization per channel
→
C
Channel-ID bindingValidate channels.list(mine=true)
→
D
Guarded publisherApproval + before/after proof

Token: Brad Stevens

expected_channel_id = UC0Hm6gNgLPSNrCDQDiec22w

Authorize while Brad is acting as the actual controlling personal/Brand channel owner.

Token: Outsource Access

expected_channel_id = UCtuOEc77xh8HISeBIy2-Jiw

Authorize while the actual corporate/Brand Account owner is acting as this channel.

No ordinary service-account shortcut exists. Normal YouTube channels require human OAuth. Once refresh tokens are securely stored, approved API work can run without a browser; initial authorization and future consent/MFA challenges remain interactive.

Publication guardrails

  • Read and back up every current field
  • Lock every job to an expected channel ID
  • Generate an exact before/after payload
  • Require explicit approval before public changes
  • No deletion methods in the application allowlist
  • No privacy/scheduling changes by inference
  • Verify API response and public YouTube page
  • Keep rollback metadata and idempotency lock

What we will verify together later

A read-only session first. No ownership or permission changes.

Identify the Chrome profile

Click the Chrome toolbar avatar and record the profile name, sync email, and whether bookmarks are merely hidden or belong to another profile.

Confirm the personal channel relationship

Open YouTube’s channel switcher and Studio advanced settings. Match the Brad Stevens title to channel ID UC0Hm6gNgLPSNrCDQDiec22w.

Confirm the corporate channel relationship

Match Outsource Access to channel ID UCtuOEc77xh8HISeBIy2-Jiw and identify the Google login acting as owner.

Inspect Brand Accounts

At myaccount.google.com/brandaccounts, record Brand Account name, primary owner, other owners, and managers—without changing them.

Inspect Studio permissions

For each channel, open Studio → Settings → Permissions and record the active delegation model.

Restore VidIQ web access

Sign into the existing paid VidIQ account, complete MFA, confirm both connected channels, and open Optimize without publishing.

Authorize the API twice

Create separate offline OAuth grants, verify each returned channel ID, and store each refresh token securely under that ID.

Run one controlled test

Complete read-only inventory first. After Brad approves an exact change, publish one low-risk video update and verify it publicly before scaling.

Authoritative references

Official Google, YouTube, and VidIQ documentation.
Prepared by Sterling · Confirmed facts, guarded recommendations, and verification gaps are intentionally separated.