Send your leavers off with their work.

Why this matters for the school

Every summer the same thing happens. A few weeks after the academic year ends, students realise their OneNote class notebooks have gone, or an alumnus emails asking whether the school still has their coursework, or a parent calls because the previous year's revision is nowhere to be found. You can't restore deleted accounts; the school never had a duty to. But you also know — better than anyone — that this is the student's own work, and it shouldn't just disappear.

mydocs.school is a single answer to that pattern.

What you get

• A self-service download portal at mydocs.school where any student in your tenant can sign in with their school Microsoft account and download a copy of their files in one click.
• A privacy boundary you can stand behind. Class notebook downloads are scoped to each student's own section group — never teacher pages, never other students' work. Enforced by SharePoint ACLs and re-asserted in code.
• An audit trail. Every download is logged with the student's Entra OID, the timestamp, and what they requested. School admins can search the log if a question comes up.
• A school admin dashboard. See recent download activity and manage other school admins.

Cost

Free for every school and student. There's no cost, no per-cohort pricing, and nothing to buy.

How onboarding works

1. Your IT admin opens mydocs.school/onboard, clicks Grant consent for my school, and signs in with a Cloud Application Administrator or Global Administrator account.
2. Microsoft shows the standard consent screen with the scopes we're asking for (OneDrive read, OneNote read, EDU class roster). Your admin clicks Accept.
3. Your tenant is now on the allow-list. Any student or staff member at your school can sign in normally — they will not see a consent screen.
4. We email you to confirm your school is set up. Your students can start downloading straight away.

Total time, end to end: about thirty seconds. There's nothing to install in your tenant, no per-school app registration, and no agent on any device.

Compliance and DPA

• mydocs.school is operated by Muon Works Ltd, a UK-registered company.
• For UK GDPR, the school is the data controller and Muon Works Ltd is the processor. We sign a Data Processing Agreement with any subscribing school on request.
• We don't store, log, or inspect file contents. Files stream from Microsoft Graph to the student's browser — nothing is retained. See the privacy policy for details.
• Production runs on AWS in the London (UK) region. The Postgres database (only school admin metadata, no file content) is in the same region; PII fields are encrypted at rest.
• We don't use analytics that would inspect your students' activity, advertising networks, or AI-training providers.
• Sign-in uses Microsoft Modern Authentication (OAuth / OpenID Connect) — students enter their password on Microsoft's own page, not ours. Your tenant's multi-factor authentication and Conditional Access policies apply to mydocs.school sign-ins exactly as they do for any Microsoft 365 service.

What it's good for (and what it isn't)

Good for: end-of-year leaver workflows, alumni access requests, data subject requests for current students, students changing school mid-year, exam re-mark appeals where original drafts matter.

Not for: backing up the whole school, copying data between teachers, archiving for litigation hold, exporting Outlook email or Teams chats. We're a focused tool — student OneDrive + OneNote, in one zip — not a general-purpose Microsoft 365 backup.

Questions schools usually ask

See the FAQ for student-facing questions; the IT administrators page for the technical details (scopes, data flows, security model).