Guide
Updated 24 September 2026.
Keep each school’s pupils, staff and messages to that school. A parent with children at two of your schools can use one login and switch. Staff in one office should not be able to open another school’s queue.
They will not install a different app for the infant school and the junior school because both sit in the same trust. Share the login. Keep the letters apart. A message from one school should not show up in the other school’s list.
The office works inside its own school. If a trust lead needs to see across schools, that should be a role you give them, not an accident of every login. A contact restriction stays on the child at the school that recorded it.
It is worth agreeing how you label messages, what you do when permission is missing, and how paper packs are produced. Each school can keep its own collector, its own MIS and its own club list. A trust template that skips a local restriction causes more trouble than it saves.
Yes. They switch school in the same login. The booking stays with that school and that adult.
More on this: Pupil Gate for MATs, What to check in a parent app, Parent communication. The full list is on the guides page.
Open the demo as a parent, then as the office, and see the same letter from both ends. It is a fictional trust with the real product behind it.
