Google Workspace for Education is a free suite of hosted email and collaboration applications for schools and other educational organisations. The range of services includes:
There is no cost for state and state integrated schools to use Google Workspace.
This overview of the one-off process for setting up Google's Workspace for Education in your school is for teachers or school technicians with a reasonable technical understanding.
The whole process typically takes a few weeks.
Your school will need its own domain, for example, your.school.nz.
Purchase a domain if you don’t have one from a Registrar .
You will need access to manage the domain’s DNS records – this is quite complex so be prepared to get some technical help for part 2.
Start at the Google Workspace for Education "Let's get started" page .
This part is more technical; if your domain is not verified within a week the application will lapse and you will need to start again.
There are some simple things that you should do when setting up Google Workspace to make things easier for users and easier to transition services such as email from other systems.
By default, all information on calendars is visible to all users. We suggest that this is not usually required as it means, for example, that the Principal’s appointments can be seen by students.
We recommend that you consider changing the sharing settings as follows:
Contact sharing has to be enabled in order for users’ names to automatically appear when sharing documents or sending emails.
Consider how you can access training for being an administrator for Google Workspace. This is typically found online or delivered by professional learning or technical providers. If possible, ensure more than one person is trained and is actively being an administrator as this is part of good succession planning.
You should seek the permission of parents or caregivers before setting up their children’s accounts.
Guardian’s Guide to Google Workspace for Education – a PDF for schools to send to parents explaining how their child is using Google Workspace and the tools their child can access and use.
There are a variety of sources of help with administration in a cloud-based system. Reaching out to connect with others is one of the best ways to learn.
By default, at no cost, the Google Admin Console (a website that the school’s administrators can access to manage the Google Workspace domain for the school) enables the management of the user’s experience such as:
In order to manage the devices themselves, your school will need to deploy a Chrome Education Licence for each device. Since November 2018 the Ministry of Education has funded Chrome Education Licenses for school-owned and BYOD Chromebooks.
Among other things, the Chrome Education Licence allows an administrator to:
For student-owned devices it is possible to use the off-hours policy setting to ensure that school-based settings are not applied between, for example, 3.00 pm – 8.00 am on weekdays.
If you are considering purchasing a reasonable number of Chromebooks, we recommend you also deploy the Chrome Education License.
Adding users, like students, teachers, and support staff, to the directory is usually done manually by an administrator or automated by a scripted process. Ideally, your user accounts should be provisioned automatically with your Student Management System (SMS) being the authoritative source of users coming and going. Some SMSs allow for this to happen by feeding data to the school’s network directory which can then synchronise the user accounts with the cloud system’s own directory.
Whether automated or not, having robust procedures for setting up and managing user accounts in a timely fashion is essential for students and teachers to be able to use the cloud services that are available.
There are two key ways that multiple users are identified and managed in bulk:
Organisational Units are distinctly separate in their function from Groups.
Organisational Units separate the allocation of things such as the services, settings, policies, and apps that are allowed or deployed to users.
Usually schools separate staff and student users as a minimum at the top level of OUs. Then, the OU structure could be further granulated, depending on the specific needs around which types of users require different services, settings, policies, and apps. By separating students into OUs using the year in which they leave the school (as opposed to their current year level), students can remain in that OU rather than an administrator having to rename it each year:
Putting users into groups makes it easier to assign access permissions for things like files, folders, calendars, email distribution lists, and so on.
Naming groups with a prefix such as “GRP-” or an underscore “ _ “ makes it easy to see at a glance that it is a group rather than an individual, for example, “_AllTeachers”, or “GRP-Teachers”. Use a naming convention that is easy to follow rather than written in code.
Some typical groups might be:
Groups can be created and managed separately in the admin console or they can be synchronised with the groups that are already in place on the school’s network directory. Whatever system is used, it is essential to have clear systems, roles, and responsibilities around maintaining group memberships. It does not require technical expertise to administer group membership so designating this task to administration staff is recommended. However, it’s important to provide sufficient training, and ensure that the tasks can be done by more than one person as this is good succession planning.
Some SMS providers enable groups to be exported automatically. This can be an effective system to enable the Groups in the cloud system to match the year levels, classes, subjects, and so on that the students and staff belong to.
When an account is deleted, any files, folders, emails, calendars, and so on that person has created are also deleted so it is important to consider what content needs to be retained by the school, what needs to be downloaded or transferred to that person, and what should be archived.
Rather than deleting accounts, they can be suspended which means that the shared content is still accessible to others but the user themselves can not log on to retrieve it. Alternatively, when a person leaves the school, ownership of their files can be transferred to another account such as a generic "past users" account or to a particular person.
Another option to consider is to rename the user who is leaving to "deleted_$Name", change the password, and disable the email for that account.
Set up a good filing system (folder structure) for storing and sharing files. The folder structure you were already using on your server may be suitable, you can duplicate this into your cloud service, or you might decide that it is time for a change.
Setting up a folder structure for shared folders requires some planning. Once the shared folder structure has been created, the groups that are to use the folders can be assigned suitable access permissions. The top two or three levels of the shared folder structure should be owned by a generic service account (for example, email@example.com) and shared so that they are "view only" otherwise people will likely add files and folders that turn the orderly structure into chaos!
We recommend you look at:
Develop clear naming protocols – With any filing system, it is always useful to have clear naming protocols for files and folders that are understood and used by anyone with access to it. If you have named a file/folder carefully in your cloud service, the search function will quickly locate it.
Think about who needs access to which files and folders – Best practice from a security perspective is to limit access to files and folders to only those who really need it.
Once the structures and permissions are in place, people will need to locate the top-level shared folder in their "Shared with me" folder and "Add to my Drive".
Establish clear expectations (possibly through a policy or procedure) around the sharing of resources in your cloud service.
There are admin console settings available for sharing outside of the school domain .
This is a good opportunity to consider or review your school’s policy on who owns the resources a teacher produces, and whether you want a Creative Commons policy in place .
When giving others editing rights to files and folders it is possible for items to be deleted. Options for minimising accidental deletion of files include:
Once a folder structure and groups have been put in place, people can start to benefit from being able to more easily create and share files and folders. Sharing files and folders means that everybody is always accessing the latest version and they can collaborate on one document from different locations at the same time. For this reason, always encourage people to share files rather than send attachments.
As everybody gets more online accounts, be they from school-related activities or personal accounts, it is easy to be confused about which account is being used at any one time and to manage many different usernames and passwords.
It is best if personal and school-related online activities are kept separate.
Your strategy for password security should be centred around both highly secure and highly usable practices. This will increase security with little impact on staff. Consider using:
Setting up shared calendars helps everybody know what is going on at school. People or groups of people can contribute to particular calendars so that the responsibilities for maintaining calendars are more effectively shared which leads to more reliable, up-to-date calendar entries.
Transfer data between Google Workspace accounts outlines options for administrators. Students and teachers can copy content from your school account to another account using the steps outlined.
To copy and transfer data, a student or teacher visits their transfer your content page. Note that only Drive files that the student or teacher is an owner of are transferred, not items that are shared with the account. There are paid services, such as VaultMe , that can transfer data between Google accounts and keep shared document settings in place.
In general, it makes sense to transfer ownership of the blog to the new Google account.
You should also consider how blogs are initially created and managed within your school domain as this will impact transferring data when students or staff leave. Pt England School’s effective blogging site provides many recommendations.
Download your YouTube clips using Video Manager or Takeout.
Use the copy and transfer method.
Use Takeout to download your bookmarks then import them into your new account.
Use Takeout to keep a record of your calendar entries but use fresh, new calendars in your new account. Make a note of any shared calendars that you subscribe to and re-subscribe to them in your new account.
Use Takeout to export contacts as a CSV then import them into your new account.
Use one of the methods to transfer the ownership of your sites to your new account. Unless you want the site to remain under the control of your existing school, it is usually best to transfer ownership and make a copy of it.
Option 1: Use Google Takeout to export and download the Drive files that you are an owner of. This does not export and download files that are shared with you. You need to make a copy of any files that are shared with you in order to download them with Google Takeout. Takeout exports Google Docs, Slides, and Sheets as Microsoft Word, Powerpoint or Excel files. Google Forms are not downloaded at all and revision history and some formatting might be lost in the conversion.
Option 2: Move all your files and folders into a new folder which you then download . Downloading a folder means that files and folders that are shared with you are included in the downloaded ZIP file. Depending on the size of all files this could take some time to download so ensure your internet connection is good and the device being used is not going to go to sleep! You may like to download individual folders rather than everything in one hit. Once downloaded, the zipped folders need to be unzipped then the folder can be uploaded to the new account's Drive.
A step-by-step explanation of how to move documents from one Google drive domain to a separate Google drive domain.
Use the copy and transfer method.