Setting up your school

Roles, and what each one can see

Who gets which role, and why a teacher cannot see the whole school.

A role is not a label — it decides what a person can reach. This is enforced on the server on every request, so nobody reaches a screen they should not by guessing a web address.

Admin — sets the school up: classes, people, roles, cards, settings. Uses the web console, not the app.
Headteacher — sees the whole school: the day, attendance, approvals, incidents, reports, emergencies.
Teacher — their own class or their own subject registers. Not the rest of the school.
Gatekeeper — the scanner, and a way to find a person with no card. Nothing else at all.
Front office — visitors, deliveries and visit requests.
Boarding staff — sign-outs, night roll-call, and which boarders are away.
Nurse — the sick bay: who was admitted, who was sent home.
Bursar — fees. Uses the web console, not the app.

Where to find itRoles → see and change what each role can reachOpen it →

One person can hold several roles. A headteacher who also teaches S.3 Maths gets both, and sees both.

Set up your school for the first time

The four steps, in order, and roughly how long each one takes.

Import your students from a spreadsheet

What the columns mean, and what to do when rows are rejected.

Print the ID cards

What GatePass generates, what you print on, and what to do about lost cards.

Did this not answer it? Tell us what happened — we would rather fix the guide than answer the same question twice.