In our Coffee & Cake sessions at the end of 2023 and surveys we gathered many questions from staff. Below are answers to the questions we received and we'll add to this over time.
Email - We will be working with the university to transfer e-mail from @leeds.ac.uk to @luu.ac.uk, setup redirects for at least 6 months to ensure you can still be contacted via known email addresses.
Files / documents - Littlefish will support us to automatically transfer files from our Google workspace to new Teams and SharePoint repositories that we will set up. However, there will be some manual work that we will need to do with everyone since we will also be transferring away from the networked O:\ drives which which contain a lot of very outdated files.
Forms / Jamboards - We will not be able to automatically transfer forms so we will support teams with the setup of any data capture or transfer of other Google specific files such as the discontinued Jamboard.
Sharing links - Unfortunately, we don't foresee it will be possible to preserve file sharing links within LUU, with the university and with external organisations. However, this provides an opportunity to assess what documents need to be shared more widely in LUU and potentially locate in an area that everyone can access. In addition, this provides an opportunity for reassessment - the majority of reported potential data breaches at LUU have been in connection with a lack of control of document sharing so this gives us an opportunity to address how we secure our data and information.
Supporting clubs and societies - Following a pilot with LSR and LSTV LUU rolled out (luu.group) e-mail addresses and Google accounts to all clubs and societies during the pandemic to support their interactions with students. This Google workspace will be left as it is and the limited support that is provided by LUU Digital Services - mainly around account set up - will be continued.
Other emails addresses - Apart from (@leeds.ac.uk) and (@luu.org.uk) which will be discontinued for staff for the new (@luu.ac.uk) accounts, and the (@luu.group) Google accounts which will be continued for student groups we are not aware of any other e-mail addresses used in an official capacity. However, if you are let us know on the staff feedback page
File sharing - The approach is no different then working with external organisations in Google you can share files with colleagues at the university and also partners. As discussed on Why, this project is focused on creating an IT setup that is right for LUU and there are some positive changes we can make about file sharing - for example, the university does not allow files to be shared with external visitors within a team chat; this type of policy makes perfect sense when you're managing cybersecurity for 50,000 users using a policy-based approach but at our smaller scale, where it is possible to review IT usage manually, we may opt for a more open setup for the productivity benefits it brings.
Will we have access to the university address book? - As we will be in a separate Microsoft workspace, we will no longer be able to access the university address book. However, teams that need to look up student e-mail addresses can be given access to engage our membership platform which contains contact details for students (LUU membership is 80-85% of the student population). We don't envisage that it will be possible to have guest access to the address book.
Migration of email from @leeds.ac.uk >>> @luu.ac.uk - Part of the technical project delivery is moving your email from your current @leeds.ac.uk account to the new LUU.ac.uk account. Once that is come
Redirection of email from @leeds.ac.uk >>> @luu.ac.uk - We will have a gradual, staged approach to email migration to allow users to check that all files have been successfully copied across and that they have everything they need.
Three months full @leeds.ac.uk account access after migration
Data retrieval for 3 following months (no login, email forwarding)
Total email forwarding for 6 months
Telephony switchover - We are aiming to provide an integrated approach to telephony where you can receive calls in Teams Voice set up on your laptop or on a mobile phone, and staff who have an external telephone extension/number, we will transfer this across.
What about switchboards? - Whilst many LUU staff no longer use the telephone handsets as we work in a hybrid way, we know that there are some teams, for example Help and Support, that still need a physical telephone and the ability to receive and transfer calls - we will ensure that this is preserved for the teams that need it.
We are keen to make the most of our switch to Microsoft and will explore using their applications more - For example, many teams successfully use Asana to manage their work, but we will explore a switch to Microsoft Planner and Loop to see if we can create a simplified and more integrated experience. In addition, some staff have been experimenting with third party tools such as Otter.AI to improve on the standard teams transcription but Microsoft's artificial intelligence (AI) helper 'coPilot' does this and provides a more secure and integrated experience for staff. We will explore this in the optimise and complete stage of the project - See Calendar.
How do I logon to X (which I currently use Google Single Sign-on SSO for) - During the transition, we will make sure that platforms that require Google single sign on are switched over to Microsoft.
Can I still use Google Chrome? - Google Chrome is the browser used when your main workspace is Google. With the switch to Microsoft, the supported browser will be Microsoft Edge. However, you will still be able to use Google as your search engine if you prefer.