YouTube scheduling tool cannot connect?
Your YouTube scheduling tool can't connect to the channel — here's why that happens and how to fix it without guessing.
When a scheduling tool loses its connection to YouTube, the cause is almost always one of three things: the Google Account that authorised the connection no longer has the right role on the channel, the OAuth permission was revoked or expired, or the tool was authorised under a different Google Account than the one that actually manages the channel.
If your situation is actually …
- Your tool connected before but stopped working after a team change → Third-party tool cannot connect →
- You're not sure whether the problem is the role or the connection itself → Why YouTube APIs require Owner access →
How scheduling tools connect to YouTube
Scheduling tools connect to YouTube through Google's OAuth system. When you authorise a tool, you're granting it permission to act on behalf of a specific Google Account — not a channel directly. That Google Account then needs the right role on the channel for the tool to do anything useful.
This means the connection has two parts that can break independently: the OAuth authorisation (whether the tool can talk to Google at all) and the channel role (whether the Google Account the tool is acting as has permission to do what the tool needs). A scheduling tool that only needs to upload videos needs an account with at least Editor access. Some advanced features — like changing channel settings — require Manager or Owner.
Brand Account channels add a layer: the Google Account you use to authorise the tool must be a member of the Brand Account with an appropriate role. Authorising via a personal Google Account that was never added to the Brand Account will fail, even if that account owns another channel.
What you see and why
Match your error or symptom to find the likely cause before changing anything.
| What you’re seeing | Likely cause | What it usually means |
|---|---|---|
| Tool says "not connected" or asks you to reconnect | OAuth token expired or revoked | The authorisation grant between the tool and Google has lapsed. Re-authorising through the tool should fix it — but re-authorise from the right Google Account. |
| Tool connects but shows no channels or the wrong channel | Authorised under the wrong Google Account | The Google Account used to connect is not a member of the Brand Account that owns the channel you need. |
| Tool connects, shows the channel, but fails when scheduling | The connected account's role is too low | The Google Account the tool acts as has Viewer or no role on the channel. Uploading and scheduling requires Editor access or above. |
| Connection worked until recently, then stopped | Role was changed or removed, or OAuth was revoked from Google Account settings | A team change may have removed the account's role, or someone revoked connected app access at myaccount.google.com/permissions. |
| You can connect personally but your team's tool cannot | Team tool was authorised under a different account | Whoever set up the tool on your team's side used a Google Account that doesn't have access to your channel. |
If you're not sure which Google Account was used to authorise the tool, check inside the tool's settings — most scheduling platforms show the connected account email.
Check these before reconnecting
- Open the scheduling tool's settings and note the exact Google Account email used to connect it.
- Sign into YouTube Studio with that same Google Account and confirm the channel appears in the channel switcher.
- In Studio → Settings → Permissions, check what role that Google Account has. Editor access or above is needed to upload and schedule.
- Go to myaccount.google.com/permissions and check whether the scheduling tool still appears in the connected apps list.
- If the channel is on a Brand Account, confirm that the authorised Google Account is a member of that Brand Account.
- Check whether anyone recently changed roles or removed a team member — that could have removed the connected account's access.
How to reconnect correctly
Follow these in order. Reconnecting without checking the account and role first usually leads to the same failure.
Identify the right Google Account to use
The account you use to authorise the tool must be a member of the Brand Account (if the channel has one) with at least Editor role. If you're not sure, sign into YouTube Studio with candidate accounts and see which one shows the channel.
Where: studio.youtube.com — check the channel switcher at top right
Verify the role is sufficient
In YouTube Studio, go to Settings → Permissions and confirm the account has Editor, Manager, or Owner role. Viewer-level access is not enough for scheduling tools that upload or modify content.
Where: YouTube Studio → Settings → Permissions
Confirm: You should see the account listed with a role of Editor or above.
If this fails: How to give editor access on YouTube
Revoke the old connection and reconnect
In the scheduling tool, disconnect the existing YouTube account. Then reconnect — making sure to sign in with the correct Google Account when Google's authorisation prompt appears. Don't just confirm the existing session; click "Use another account" if a different account is pre-selected.
Test with a draft or private video
Schedule a private or unlisted video as a test before relying on the connection for live publishing. This confirms the tool has working write access without affecting your public channel.
The most common mistake
Most reconnection failures happen because someone re-authorises the tool using the Google Account that's currently signed into their browser — which is often a personal account, not the one that has access to the channel. Google's authorisation prompt doesn't always make it obvious which account is pre-selected.
If the scheduling tool keeps losing the channel after reconnecting, the fix is almost always to check which Google Account was used and whether that account still has the right role — not to re-authorise again.
Delvia
Access issues are easier to prevent when roles, owners, and responsibilities are recorded clearly
Most access problems trace back to the same gap — no clear record of who has access, what role they hold, and what should happen when that changes. Delvia helps you keep that record so problems are visible before they become incidents.