The sequence
1
Your school is set up with a signup code
A code is issued against your school’s name. It is what turns a new account
into a working one — see Access approval.
2
Teachers are invited, or given the code
You can email invitations directly from MESO, or simply share the signup
code with staff. Both routes end in the same place. See
Inviting members.
3
Each teacher completes their own setup
Seven short steps — name, role, school, and the subjects and year groups
they teach. Those choices decide what they can plan.
4
Planning begins
From that point a teacher works independently: units, lessons, assessments
and resources are theirs.
What a school administrator can see
Two views, both under Settings → Workspace, and both visible only to administrators:- Members — send invitations and manage your school’s signup codes.
- Cohort — how many of your teachers have activated and completed setup.
What MESO does not do yet
MESO has no organisation tenancy. Accounts are individual. A school is a
name attached to a signup code, not a container that owns teachers or their
work.In practice this means an administrator can see whether teachers have
activated, but not what they have planned. There is no shared school library, no
central unit repository, and no way to reassign one teacher’s work to another.