1. with Gaggle!!!!

2. WRPS had been using Gaggle.net for student email. We were pleased with the filtering and notification- Google did not provide this level of management o How to provide a safe and controlled student email system WRPS was planning to transition staff to Google Apps for Education and did not want students and staff to "live" in seperate domains. o Needed to work with a partner that understood the impacts of the designs we were considering- domains, sub domains, delivery mode options, etc Accommodating for mail archiving Automating account creation when working "in the cloud" Eliminating the need for an additional set of log in credentials

3. Automatic filtering of text and images offers CIPA and COPPA compliance All inappropriate behavior is blocked AND administrators are notified Continually updated blocked word list (including slang and text speak) Administrative access to student accounts and all mail Students cannot delete mail Messages are retained for 1 year

4. Begin using Google Apps for Education with students but provide filtering and notification through the use of Gaggle.net's Passthrough Technology How it works o All inbound and outbound mail passes through Gaggle before reaching its' final destination. The mail is sorted, filtered and stored on the Gaggle system just like one of our regular subscription email accounts. o Two changes by the Google Apps Administrator. The changes are seamless and will not interrupt the email service of your Google Apps users

5. Add an Administrator account in Google for Gaggle Enable the provisioning API in Google Contact Domain Registry to update your MX record for mail routing Configure Gaggle as the outbound gateway in Google Notify current users of change- provided access to Gaggle system for two weeks (old mail was accessible but all new mail was routed Configure the Gaggle Site Administrators for block mail review

6. We have an automated script that looks for changes in our SIS system and populates an account in Active Directory We also have implemented Google Apps Directory Sync to automate account creation If the account exists in Active Directory, the account exists in Google Gaggle accounts are synchronized with Google o If the account exists in Google, it exists in Gaggle A Single-Sign On service is used to consolidate user credentials (we are using SSO Easy)

7. Provide students the Google experience but with "best in class" filtering solution Gaggle is Erate eligible (mail hosting only- not archive service) Student email is retained for one year Mail notification gets sent directly to appropriate Google account and can be "released" from the Google interface

8. The students already existed on the wrps.net Google Apps for Education Domain- Thus we wanted to have our staff "live" in the same domain as the students. The focus for staff was not on filtering and monitoring- it was developing an archiving strategy Gaggle was used to archive all staff mail. Thus it was important to have sub domains so that the archival pass through solution could differentiate user types

9. Benefits of the archiving solution It was hosted Highly accessible with robust search features Reduced our costs compared to our on premise mail archival appliance model we were using Data can be extracted from system if need be Ability to provide access to others in the discovery process or litigation hold scenario Offers archiving for both mail and also docs, calendars, and chat Excellent support- willing to work through a solution

10. Determine how you want your domain and sub domains structured o Consider if there would be reason be granular? I.E. would you turn certain services on/off for certain groups? Determine who should be getting block messages, prepare these staff with the overview of how the filtering works and what conditions block a message o Also, consider approval process to occur as close to the students as possible, for example building level What is your e-discovery process o When a request comes in, how and who should have access to the discovery o Work through scenarios o How long will data be archived

11. Questions?