Controlled, role-based onboarding for every member of your school community.
After setting up your workspace, admins invite teachers and parents through Scholary's invitation system. Each person gets a role-specific account — teachers see their classes, parents see their children. Private tutors sign up independently and manage their own workspace.

Only school admins can invite teachers and parents. There is no open self-registration for school-linked roles — the admin decides who gets in.
Invite teachers by email. They create a Clerk-verified account and are immediately scoped to their assigned classes and subjects.
Invite parents and link them to their children at the point of invitation. Parents can only see their own linked children.
Private tutors sign up independently and get a personal tutor workspace — separate from any school — to manage their sessions, students, and earnings.
Roles are embedded in Clerk session claims and verified server-side on every request. Changing your role in the UI does nothing.
A direct comparison against how most Nigerian school software handles the same problems.
Access model
Most school platforms use shared passwords, PIN codes, or open sign-up — any person with the link can register as a teacher or parent.
Invitation-only for school roles. No link-guessing, no code-sharing, no unauthorised access.
Role security
Role checks in many apps are front-end only — hide a button and the API is still open.
Scholary enforces role checks in both middleware and server actions. There is no front-end-only gate.