A friendlier way to handle account access.

What this is, in plain language

Most help centres are organised around platform features — "here is the YouTube Studio permissions tab" — even though the questions creators actually have are about situations: "the freelancer I worked with last year still has access, what do I do?" or "I added someone but they cannot see the channel."

The hub flips that. Pages are organised by what you’re trying to do. Each page covers the situation end-to-end: the prerequisites, the actual steps, the mistakes that catch people, the common follow-up questions, and where to go next.

How it is organised

Every guide sits in one of five topic areas — what you’re trying to do at the moment:

• Give access — add an editor, agency, or teammate without sharing a password.
• Fix something — diagnose why a permission did not stick, an invite did not arrive, or the screen does not look right.
• Get back in — recover after a lost password, a departing teammate, a hostile change, or a platform action.
• Understand — what each role can actually do, how ownership really works, the difference between account types.
• Stay organised — light frameworks for setting access up well, handing over cleanly, and avoiding the “only one person can recover it” trap.

Inside each topic, anchor pages cover the main situation, and more specific pages branch off them for the operational variations creators actually search for.

How the content is sourced and kept current

Every guide is written against each platform’s own current help centres, settings UIs, and policy pages — today that means YouTube and Google. Where flows or role models change, the affected pages are updated and re-dated. The oldest verification date in the hub right now is 2026-06-16.

We do not invent flows or quote shortcuts that the platform does not actually support. If a recovery path is slow, narrow, or genuinely brittle, the page says so — pretending otherwise just costs people time.

Guides are not legal advice. They describe how the platform works and the operational consequences of common decisions. For contractual, employment, or legal questions, talk to a lawyer.

Why Delvia built this

Delvia is a delegation-governance product for creators and the people who work with them. The Content Hub exists because the same questions kept coming up — about permissions, agencies, and recovery — and there wasn’t a single good resource to point at. So we wrote it.

The hub is independent of the Delvia product. You don’t need a Delvia account to use it.

Where to start

If you have a specific situation in mind, pick the matching topic area:

Or browse every guide.