YouTube Roles Explained (Owner, Manager, Editor, Viewer)
Owner, Manager, Editor, Viewer and the limited variants on YouTube — what each role can and cannot do, and how to pick the narrowest one that still gets the work done.
YouTube delegates channel access through roles in YouTube Studio → Settings → Permissions. That Permissions screen exists on every channel — a personal-account channel and a Brand Account channel both invite people by their own Google Account email, with no password sharing. The roles form a ladder from Owner (full control, including ownership) down to Viewer (read-only). The single most common mistake is granting Manager when Editor would do.
Roles control access — not ownership
Everything below the Owner line is a delegated permission: you can add it, change it, or revoke it in seconds, and it never lets the person take the channel away from you. Managers, Editors, and Viewers are all in this layer.
Ownership is different. On a personal-account channel there is exactly one owner — the Google Account holder — and ownership cannot be shared or transferred. Only a Brand Account can have multiple owners, a backup owner, and a primary owner who can transfer the channel. So when you hand out a role, you are sharing work, not handing over the channel.
Every YouTube channel role
The full role ladder, with what each can and cannot do. Pick the lowest row that still covers the work.
| Role | Where it lives | Can do | Cannot do |
|---|---|---|---|
Owner Can delegate to others | Google Account / Brand Account owners listEntire channel and its Google account |
| — ⚠ Only assign to long-term, trusted principals. Removing an owner requires Brand Account governance. |
Manager Can delegate to others | YouTube Studio → Settings → PermissionsChannel-wide |
| — ⚠ Managers can invite new users — equivalent to delegating delegation. |
Editor | YouTube Studio → Settings → PermissionsChannel content |
|
|
Editor (Limited) | YouTube Studio → Settings → PermissionsChannel content excluding revenue |
|
|
Viewer | YouTube Studio → Settings → PermissionsRead-only |
|
|
Viewer (Limited) | YouTube Studio → Settings → PermissionsRead-only, no revenue |
|
|
Subtitle Editor | YouTube Studio → Settings → PermissionsSubtitles and captions only |
|
|
Which role does this person actually need?
- Q1
What is this person here to do?
Edit and publish videos (in-house)Editor — full content control, including revenue data, without the ability to add or remove people. How to give Editor access →Edit videos but should not see earnings (freelancer)Editor (Limited) — the same content workflow with revenue hidden. The right default for most outside editors.Run the channel and manage who else has accessManager — everything an Editor can do, plus inviting and removing people and editing channel settings. Reserve it for people you trust with access itself. How to give Manager access →Only review analytics or reportingViewer, or Viewer (Limited) if they should not see revenue. Read-only, nothing to break. How to give Viewer access →Add captions and nothing elseSubtitle Editor — the narrowest role, limited to subtitles and captions.
Where role choices go wrong
Granting Manager by default
Manager can invite and remove other people, including other Managers. Most collaborators only need Editor; Manager hands over control of access itself.
Why it happens: Manager is the most visible role, so it gets picked without checking whether Editor would do.
Already happened: When to give Manager vs Editor
Sharing the password instead of adding a role
Roles exist precisely so you never have to share a login. A shared password gives someone everything and leaves no audit trail.
Why it happens: People assume access means handing over the account.
Already happened: Why password sharing is dangerous
Giving full Editor to a freelancer
A full Editor can see revenue. For most outside editors, Editor (Limited) is the better fit — same content workflow, earnings hidden.
Why it happens: The two Editor variants look alike in the invite menu.
Frequently asked questions
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.