Generally speaking, the administrative procedures are more streamlined for G suite than for Zimbra so we can expect less admin busy work but more direct support for TCEO staff.
- Account provisioning is now automated through the TCEO staging database. Although we no longer need to provision accounts directly like in Zimbra, there will be occasional coordination with TCEO staff required to provision a new account such as letting them know when a new account is ready or creating a generic account.
- Password resets, another common support activity for Zimbra, can now be self-supported by TCEO staff. Therefore there will be less doing it for them, but more showing them how. In rare cases we will have to reset passwords if a user forgets their security questions.
- Google Groups creation is to be managed Getbusi in order to keep the usage and naming consistent. However the members of the groups can be managed directly by the school, so less day-to-day work will be required to maintain them.
- G Suite app settings and permissions G Suite offers many apps and services, and as the TCEO's usage of them evolves we made need to tighten up various aspects of how they can be used by staff members.
- Help Desk. The on-site migration sessions Getbusi did at the systemic schools introduced us as a direct contact point for many staff members. We now expect to provide more assistance directly to staff as opposed to queries which have filtered up through the ICT team. This will include answering phone calls and emails during our business hours.
- Help website. As part of the migration project we established getbusi.com/tceo to provide help guides for common staff G Suite activities. We'll continue to use this site to publish guides for activities we find ourselves having to explain frequently.