Blog · 16 May 2026

Personal OneNote vs Class Notebook vs Staff Notebook — explained

Microsoft 365 schools have three kinds of OneNote notebook, each with different ownership, sharing model, and export path. Here's how to tell them apart and what to do about each.

OneNote in a school M365 tenant looks deceptively uniform from the outside — it's all "OneNote" in the app picker. Underneath, there are three distinct notebook types, each with its own ownership model, its own export path, and its own gotchas.

1. Personal notebooks

The simplest case. You created the notebook. It lives in your OneDrive (in the /Notebooks folder). You own it.

Ownership: yours. Where it lives: your OneDrive. Who can see it: you, plus anyone you've shared with. Export path: OneNote → File → Export Notebook works. Save as .onepkg (whole notebook) or per-section .one files. What happens when you leave: dies with your account, like the rest of your OneDrive.

This is the easiest export. The OneNote desktop app on Windows or Mac handles it directly because you own the notebook and Microsoft trusts your authority to take it with you.

2. Class notebooks

Created by a teacher using the Class Notebook tool. Lives on the class's SharePoint site, not in anyone's OneDrive.

Ownership: the class team owns it (technically: the SharePoint site collection backing the team). Where it lives: the class team's SharePoint document library. Who can see what:

  • Teachers see everything in the notebook.
  • Students see the Content Library (read-only), the Collaboration Space (read-write), and their own section group (read-write).
  • Students do NOT see other students' section groups, teacher pages, or the staff-only content. Export path: OneNote → File → Export Notebook is greyed out / refused, because you don't own the notebook. Microsoft enforces this on both Windows and Mac. What happens when you leave: the notebook stays with the class. Your access disappears with your account. Your section group content is no longer reachable by you.

This is the hard case. The student's own work inside a class notebook is meaningful (often the most meaningful workload, see class notebooks: the part you'll miss most) but the export tools refuse to help.

The two reliable ways out:

  1. Microsoft Graph extraction — pull the raw .one files for your section group via Graph. mydocs.school does this; you can do it yourself with PowerShell + Microsoft Graph PowerShell SDK if you're technical.
  2. SharePoint direct download — if your school's SharePoint policy allows it, navigate to the class's site, find the notebook in the document library, download the .one files directly. Many schools restrict this; some don't.

The unreliable workarounds:

  • Send as PDF (flattens, lossy).
  • Copy pages one by one to a personal notebook (tedious at scale).
  • Screenshots (not searchable, not editable).

3. Staff notebooks

A teacher-only variant of class notebooks, used for departmental collaboration. Senior staff can create them via the Staff Notebook tool.

Ownership: the staff team that created it. Where it lives: that staff team's SharePoint site. Who can see what: staff members in the team see everything; the layout mirrors a class notebook (a leader area, a collaboration space, individual member sections). Export path: same constraint as class notebooks — Microsoft's tools refuse to export a notebook you don't own. What happens when you leave: the notebook stays with the staff team; your access ends with your account.

Relevant primarily to teachers and staff leaving the school. The same export options apply: Microsoft Graph extraction or SharePoint direct download. mydocs.school handles staff notebooks the same way it handles class notebooks — scoped to the signed-in user's own section.

Telling them apart in OneNote

The OneNote left-hand list doesn't visually distinguish these. Practical heuristics:

  • Personal notebook: name starts with anything you chose. Often visible under "More Notebooks" if you have many.
  • Class notebook: name typically follows a pattern like "Y11 Physics Notebook" or "Class Notebook: Year 13 History". Has a Content Library and a Collaboration Space.
  • Staff notebook: similar layout to class, but populated with staff names rather than student names.

If you're not sure: right-click the notebook → Properties → Display Name and Path. The path tells you which SharePoint site it's hosted on (class / staff site) or whether it's in your personal OneDrive (personal notebook).

What to download, in what order

If you have all three types and limited time:

  1. Class notebooks first — hardest to export, most valuable, fewest fallbacks.
  2. Personal notebooks second — easier to export, valuable, more fallbacks available.
  3. Staff notebooks (for teachers) — hardest to export, valuable to specific staff, sometimes covered by departmental hand-over.

For all three, mydocs.school provides the section-by-section .one files scoped to your own contributions, which is the closest thing to a faithful archive that exists.

A note on the Class Notebook add-in

Schools sometimes use the OneNote Class Notebook add-in, which gives teachers extra workflow tools (distribute pages to students, collect homework, etc.). The add-in changes the teacher's experience; it doesn't change the underlying file format. The same export constraints apply — class notebooks created via the add-in are still owned by the class team, and the same Graph / SharePoint extraction paths work.

Long-term archive recommendation

Whichever type, the same archive approach:

  1. Export to the original .one / .onepkg format. This is the canonical preservation format.
  2. Import into OneNote on a personal Microsoft account to confirm it opens.
  3. Optionally, export each notebook to PDF as a secondary, format-stable archive.
  4. Save in two locations: personal laptop + a personal Google Drive or external drive.

If you do all four, your school OneNote work is safe for the long term. The .one files survive future OneNote versions; the PDFs survive future format changes; the two locations survive a single backup failure.