· Everpop
To manage Shorts for many client channels, give each person a YouTube channel role instead of a password, connect tools through the client's own OAuth consent, keep one folder per client, decide in writing who may publish, send every clip through review, and give each client proof they can open themselves.
A couple of clients fit in a spreadsheet and a shared login. Once you have a roster, you have a system whether anyone designed it or not, and the shared login is usually the first thing to break. This post covers the plumbing: access, files, publishing rights and proof. Getting individual clips signed off is a separate job, covered in our guide to the client approval handoff.
How do you get into a client's channel without their password?
Ask the client to invite you. YouTube's channel permissions let a channel owner add people by email and pick a role for each one. YouTube calls this "safer than sharing your password or other sensitive sign in details."
Two details catch agencies out during onboarding. First, "Once an invite is sent, it expires after 30 days," so an invite sent during a busy kickoff can lapse without anyone noticing. Second, "If you have a Brand Account, you must first migrate to channel permissions." If the client's channel still runs on a Brand Account, that migration has to happen before anyone gets invited.
For example, a new client signs on a Monday and invites your account lead and your editor by email that day. Your onboarding list then has a line to confirm both invites were accepted before the week is out.
Which YouTube role should each person on your team get?
Give each person the smallest role that lets them do their job, and leave ownership with the client. In YouTube's words the Owner role "Can do everything on all platforms", including deleting the channel. That role belongs to the person whose business it is.
| Role | What YouTube's page says | Fit at an agency |
|---|---|---|
| Manager | "Can manage permissions (in YouTube Studio)"; "Can create, upload, publish, and delete content" | The account lead who adds and removes people |
| Editor | "Can upload and publish content"; "Can't manage permissions"; "Can't delete channel or published content" | The person who ships Shorts |
| Editor (limited) | Editor, but "Can't access revenue data (includes chat revenue and viewer activity tab)" | A freelancer with no need to see earnings |
| Viewer | "Can view revenue data (including chat revenue and viewer activity tab)" | Whoever writes the client's reports |
| Viewer (limited) | Viewer, without the revenue data | Someone who checks the channel but not the money |
The same page adds a useful detail: names and emails of people with access are visible to managers and the owner. Your account lead, as a Manager, can check the access list. Your editor can't.
How do your tools connect if roles don't cover them?
Through the client's own OAuth consent. The same YouTube page lists "YouTube APIs" among the things channel permissions don't support yet. So a clipping or scheduling tool that posts through the API isn't added as a Manager. It's linked to the client's Google Account instead.
That makes offboarding easier. Google's page on linked apps says "You can remove access to your Google Account at any time," and after that "they can't access your data anymore." When a contract ends, the client removes your team's roles and revokes the tool's grant, and nobody has to change a password. Our guide to disconnecting a tool from a YouTube channel walks through it.
How should you organise files per client?
Give each client one folder and never mix their sources. If one client's footage sits next to another's, posting the wrong clip to the wrong channel takes a single careless drag.
Name files so a newcomer could route them: client, series, episode, date. Keep the original files. They belong to the client, and they're your evidence if a claim ever lands.
Everpop supports this in two ways. In a Team workspace, you create a folder for each client and assign its connected YouTube channels to it. On a paid plan, an Everpop account can also link one Google Drive Finals folder, which Everpop picks up through Google's official Drive API. That's one folder per account, not one per client, and a file added from Drive on its own isn't filed into a client folder yet. New files in that folder are picked up at least daily, and the folder can be unshared anytime. So when an editor drops a finished episode into that Finals folder, it gets picked up without anyone emailing a download link.
Who should be allowed to publish?
Decide it in writing, per client, before the first clip goes out. The usual setup: anyone can cut and queue, one named person approves, and the client can see what went out.
Everpop's Team workspace is review-first by default, with invited managers, and nothing posts until it's approved unless the owner switches on auto-post. The owner can turn on "Members may publish directly" for a team that has earned that trust, and an audit log names the member behind each action. Approved YouTube Shorts can be scheduled up to 7 days ahead, so each client's week can be reviewed in one sitting.
For example, a junior editor queues a clip for a cooking channel and the account lead approves it. If the client later asks who posted it, the audit log shows the member's name.
What proof should each client get?
Give clients proof they can open without logging into anything of yours. For each eligible Short, Everpop creates a token-protected receipt link that the client can open without an account. It shows what the Short did at 48 hours and at 7 days, flops included. It records what the Short did; it is not a forecast. For campaigns, Campaign Mode reports export to CSV on Pro and Scale.
So at the monthly check-in, instead of a slide full of screenshots, the client opens the links for that month's Shorts and sees the same numbers you do.
The client onboarding checklist
- Client keeps the Owner role
- Brand Account migrated to channel permissions, if the channel still uses one
- Each team member invited with the smallest role that fits
- Invites confirmed as accepted before they expire
- Tools connected through the client's OAuth consent, never a shared password
- One folder per client, with a file-naming rule
- Publishing rule written down: who queues, who approves
- Proof format agreed: which links, at which check-in
- Offboarding plan: remove roles, revoke tool grants
Where Everpop fits
Scale is built for teams and agencies. It starts from $149/mo, is shaped on a call, and covers 10 client YouTube channels, up to 75 videos a month and up to 15 clips per video, with receipts for every channel, plus Campaign reports you group per client. The workflow is laid out on the agencies page, and every plan is on the pricing page.
Claims table
| Claim | Source |
|---|---|
| Channel permissions invite by email with a role; "safer than sharing your password" | support.google.com/youtube/answer/9481328 (desktop, quoted) |
| Invite expires after 30 days; Brand Accounts must migrate first | same page (quoted) |
| Owner "Can do everything on all platforms" incl. deleting the channel | support.google.com/youtube/answer/9481328 (quoted) |
| Manager/Editor/Viewer/limited-role wording in table | support.google.com/youtube/answer/9481328 (desktop, quoted bullets) |
| Access names/emails visible to managers and owner | same page |
| Channel permissions don't support YouTube APIs yet | same page (quoted) |
| Remove linked-app access anytime; afterwards no data access | support.google.com/accounts/answer/3466521 (quoted) |
| Team workspace, folder per client, review-first, owner toggle, audit log names member | everpop.app/ai-clipping-for-agencies |
| One Drive Finals folder per Everpop account on a paid plan, via official Drive API, unshare anytime, new files picked up at least daily | Send finished videos from Google Drive; everpop.app/pricing |
| YouTube Shorts scheduler up to 7 days ahead | everpop.app/help/posting-to-youtube |
| Token-protected receipt link, no account, 48h/7d, flops included, not a forecast | everpop.app/ai-clipping-for-agencies; everpop.app/help/posting-to-youtube |
| Campaign Mode reports with CSV on Pro and Scale | everpop.app/ai-clipping-for-agencies |
| Scale from $149/mo, shaped on a call, 10 channels, up to 75 videos/mo, up to 15 clips/video | everpop.app/pricing |
Frequently asked questions
- Do I need my client's YouTube password to manage their channel?
No. The client can invite you by email through channel permissions, which YouTube describes as safer than sharing a password.
- Which role should an editor who posts Shorts get?
Editor, or Editor (limited) if they don't need revenue data. YouTube says Editors can upload and publish but can't manage permissions or delete published content.
- How long does a channel permissions invite last?
YouTube says an invite expires after 30 days, so confirm it was accepted during onboarding.
- Can team members publish without approval in Everpop?
Team workspaces are review-first by default. The owner can turn on "Members may publish directly", and an audit log names the member behind each action.
- How many client channels does Everpop's Scale plan cover?
Scale covers 10 client YouTube channels. It starts from $149/mo and is shaped on a call.