Managing YouTube Access: Options for Districts

Most districts should allow YouTube and control it with Restricted Mode. Restricted Mode filters what a student can watch. Blocking YouTube but allowing embedded videos is supported, but it requires a lot more administrative overhead on the admin’s part.

Choosing an approach

	Option A: Allow YouTube, use Restricted Mode	Option B: Block YouTube, allow embeds
What students can reach	youtube.com, filtered by Google’s Restricted Mode plus any videos your organization approves	Embedded players on sites you list; direct YouTube browsing is blocked
Filtering decision made by	Google, based on the Restricted Mode level Securly signals and the user’s Workspace permission	Securly, based on the HTTP Referer/Origin of the request
Admin overhead	Moderate: set a level per policy, then align Google Workspace permissions	Higher and ongoing: every embedding domain must be added and retested as platforms change
Main weakness	Restricted Mode over-blocks some legitimate educational content, and under-blocks some content teachers object to	Does not reliably confine users to the embedded player; a student can often navigate from a trusted embed into full YouTube
Best for	Districts that want YouTube available with a consistent content standard	Districts with a policy decision to block YouTube outright that still need LMS lessons to play

One caveat that applies to both

Turning Securly’s Restricted Mode off does not mean unrestricted. Google, managed-Chrome policy, and other network controls can each impose restrictions independently.

See also: Blocking YouTube for students for step-by-step setup.