Feature Request: YouTube channel content blocking for Workspace customers

Hello,

I would like to make a request or improvement to Workspace customers and interaction with YouTube content channels.

We are a PS - K12 education entity, and our teachers use Youtube, but students can always find inappropriate sites(channels) they should not see using their Workspace accounts (personal account are not our concern and are blocked)

We have the Strict setting (9+) values enabled for students but find that channels that have not been approved for our Workspace domain is still being viewed and the only way to block those sites is to use the User & Browser setting: “URL Blocking” to block the complete youtube channel URL. With the limit of 1000 URL’s this would not be ideal. Also if the channel content creator sets the Age Restrictions to it’s lowest settings the page is viewable.

My improvement would be to block and prevent any and all youtube un-approved channels for Workspace customers in the Admin Portal if the the YouTube permission are set to anything other than Unrestricted and the channel age restrict is not set to an appropriate level. 3rd parting web content filtering services or applications can only block the domain names only. We have used Cisco Umbrella and Websense (before it became Forcepoint)

PS: if i’m not in the correct place for this request, my apologies.

Thank you

1 Like

If you have it set to only approved channels/videos should be viewable, and students are still accessing other content, then that should be reported to support as the system is then is broken.

There is no need (and should never be) to register a feature request for things that are broken.

Thank you, I have worked with support, and they were not able to make any corrections other then use the URL Blocking. Support informed me that I should put in a feature request.

Yes, I expect them to say that you have to do that, but I must say that you have to take a firm stance that the YouTube Strict setting must work. Reporting a broken setting is not a feature request.

1 Like