Larnup
Getting Started / Roles & Permissions

Roles & Permissions

3 min readGetting Started
On this page

Purpose

Everything you can see and do in Larnup is determined by your role. Rather than every user having the same app with settings to unlock or hide features, each role gets a purpose-built experience: an Admin's dashboard looks nothing like a Parent's home screen, and that's intentional. This page explains the roles that exist and, roughly, what each one is for.

When to Use

  • You're trying to understand why your app doesn't show a feature someone else mentioned.
  • You're a School Admin deciding what role to invite someone as.
  • You're new to Larnup and want a map of who does what.
  • You're troubleshooting access — someone can't see something they think they should.

How It Works

  1. School Admin — manages the school as a whole: classes, staff, fee structures, transport setup, announcements, and school-wide reports. Usually the person who registered the school or was appointed to run it.

  2. Teacher — manages their own classes: marking attendance, assigning and grading homework, and communicating with the parents of their students. A Teacher doesn't see other teachers' classes or school-wide settings.

  3. Parent — follows their own child (or children): attendance, homework, fees, announcements, and live bus tracking. A Parent only ever sees their own family's data.

  4. Driver — runs their assigned route: starting and ending trips, tracking location, and marking students on and off the bus. A Driver sees their route and vehicle, not the rest of the school.

  5. Sales Partner (also referred to internally as an Agent) — helps onboard new schools and manage their initial setup and pricing, largely operating outside any one school's day-to-day data.

  6. Super Admin — oversees the Larnup platform itself across all schools, from a separate console used by Larnup's own team rather than by school staff.

    Screenshot placeholder

    A side-by-side comparison of the Admin, Teacher, Parent, and Driver dashboards, showing how each role's home screen differs.

  7. Roles are assigned at invitation, not chosen by the user. When a School Admin invites someone, they choose that person's role — the invited person doesn't get to pick a different one after logging in.

  8. Permissions follow the role, not the person. Larnup's access model is role-based rather than user-by-user — two Teachers at the same school have identical access to their own respective classes, not customized individual permissions.

TipIf you need broader access than your current role allows — for example, a Teacher who also needs to see school-wide reports — that's a conversation with your School Admin about your role, not a setting you can change yourself.
TipThe "student" role exists conceptually in Larnup but doesn't have its own app yet — a child's academic and attendance information is accessed through their Parent's account.
Common MistakeDon't share your login with someone who should have their own account under a different role — it breaks the role-based view the app relies on, and that person won't see the experience built for their actual role.
Common MistakeIf you're a School Admin inviting staff, double-check the role you assign before sending the invite — changing a role after the fact means re-inviting the person, so it's worth getting right the first time.