New software requests should initially be submitted to the Digital Leads via form https://forms.office.com/e/j9PSQ0pbRy - users can complete this form to confirm the likelihood of quick approval (where there are no cost or GDPR considerations).
- MHS (Richard Dweck)
- Belmont (Peter Fannon)
- MHI (Stephen Trask)
- Cobham Hall (Richard Kipling)
Note that web applications are much preferred to standalone applications (which may take some time to install on machines, and may require constant security updates).
Single Sign-on (SSO) via Microsoft is much preferred, this eases password management and generally prevents ex-users from logging-on. Google SSO is a backup mechanism that may work. Staff should not allow pupils to sign-in to applications with their personal email addresses, pupils (and staff) should only use their school email addresses.
Where software requires pupil accounts to be set-up, iSAMS (or other) integration would be expected as manual processes are too inefficient for adding/removing large numbers of accounts. IT will only support onboarding/offboarding/creation of classes if integration is available.
Where software requires personal data to be loaded/entered to operate (this could be: DoB, Address, Full Name with email, Year Group, Photo, Videos, Medical Data or any other personal identifiable data), compliance may also need to involved in the approval process.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article