Clarifying the District Responsibility for “Other” Google Services in GAE

Earlier this year I posted some thoughts about some concerns that the EFF had raised about Google’s responsibilities with regard to non-Google Apps google services. My take was that the majority of the responsibility is really on the school Google Administrator (and the District). I thought it would be illustrate this perspective by showing the “behind the scenes”  view of what Google Admin has to do to turn on one of Google’s Non-Google Apps services, and point out some extra steps they added in the last few months to make it even more clear.

 

The admin consoled makes a clear distinction between Google apps services (covered by the agreement),  other Google services, Marketplace apps, which are 3rd party tools that can be installed domain wide by the Admin, and SAML apps, 3rd party tools that the Admin can set up to use Google as the authentication provider for services that support the SAML 2.0 federated authentication standard.

SAML blog

The majority of non-core services are OFF for Google Apps for Education (GAFE) customers.

override.png

 

But it is also important for K12 schools to make sure that they set the option for releasing new products  to manual

release.png

 

Clicking thru to the settings for a “non-core” service there are notices that the service is not covered by the Google for Work agreement (of which Google for Education is a part). It also included a notice to make it clear that the admin needs to have the authority in their organization to accept the terms if they do turn it on.

chrome

In the last few months Google added an additional check box and very detailed wording to make it very clear what a school Google Admin’s responsibilities are  when they turn on a service that is not covered by the “core” GAE agreement

terms.png