Duke5A Posted October 6, 2021 Posted October 6, 2021 So we got the notice that Google was clamping down on access to certain services based on age. Wasn't a big deal for staff as they gave us a way to specify an entire organization unit was over 18 and accept the terms of those users behalf. For the students though this is an issue. We've got about 4500 students and one of our departments wants to roll out a suite of plug-ins for Chrome that would only be used by about 500 of those students. What I would do before is just add said apps to the whitelist and for the students that use them they would just just go through Web Store. With no access to said store now I'm looking at having to force install these plug-ins for the entire student body. I'm real apprehensive to do this because we're not a 1:1 school. Chromebooks are communal still and reside in carts. Every time a student signs into a Chromebook now it's going to be installing these plug-ins they most likely won't be using. I'm worried moving forward the login process is going to start to getting bogged down with plug-ins that I have to force install to make available. Anyone else running into this issue?
psydii Posted October 6, 2021 Posted October 6, 2021 Yeah. This is same issue that has nerfed YouTube. It is interesting that the policy has been implemented so quickly, across alphabet they haven’t had time to figure out how to let schools make their own risk assessed decisions. I’d love to know what spooked the entire global googleplex so comprehensively.
Duke5A Posted October 6, 2021 Author Posted October 6, 2021 Yeah. This is same issue that has nerfed YouTube. It is interesting that the policy has been implemented so quickly, across alphabet they haven’t had time to figure out how to let schools make their own risk assessed decisions. I’d love to know what spooked the entire global googleplex so comprehensively. Probably something concerning data collection of minors (under 18). I'm going to have to test the impact of a force install with these plug-ins on a test account. I don't think there is going to be a way around this.
kevin_lane Posted October 7, 2021 Posted October 7, 2021 Probably something concerning data collection of minors (under 18). I'm going to have to test the impact of a force install with these plug-ins on a test account. I don't think there is going to be a way around this. Yea we had this issue for our staff and wanted to use a credit / debit card to verify age, whilst I tried to explain that given that we have explicitly defined the age range within Google We should not be forced to have to provide an extra layer of validity But he was just quoting its nothing to do with us!! I replied Yes it is! And then the call ended I understand why but they have dropped the ball on this one.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now