User management & access control
Every screen checks
who’s asking.
Admin-managed accounts, role assignment, Face ID sign-in and parent–student linking — a full role-based permission system enforced on every screen and every action.
← All featuresUsers
ADMIN VIEW
S. Whitford
M. Harris
J. Okafor
R. & K. Chen
👁 Face ID enabled for quick sign-in
What it does
Access is granted, never assumed
Nobody self-selects a role. The administrator creates accounts, assigns roles and approves access.
- Admin-managed user accounts — created and approved by the administrator, with role assignment at creation.
- Five roles, five experiences — Admin, Driver, Relief Driver, Teacher and Parent each see a different app.
- Parent accounts linked to specific students — a parent’s entire view is scoped to their own children.
- Biometric quick sign-in — Face ID / Touch ID for returning users, handled by Apple’s frameworks on-device.
In practice
How it works on the day
1
Admin creates the account
With the right role, linked to the right students if it’s a parent.
2
The role shapes the app
Screens, actions and data all filter through the role from first sign-in.
3
Every action re-checks
It’s not just hidden menus — each screen and action validates the role before displaying or allowing anything.
Going deeper
What enforcement actually looks like
Role-aware isn’t a marketing word here — it’s the architecture.
- No accidental edit access — read-only means the edit controls don’t exist on that role’s screens.
- No irrelevant screens — parents never see fleet or maintenance; teachers never see admin tools.
- Sensitive data filtered at the source — medical alerts and other families’ students never reach a parent’s device view.
- See the full matrix — the complete who-can-do-what table is on the Who it’s for page.
Ready to put your operation on the bus?
Download on theApp Store
Android — coming soon