- admin
- dean
- teacher
- student
Capabilities
Role-aware access in Kralis supports:- different navigation by user role
- different workflow access by user role
- school-setup dependence for daily operations
- student-facing self-service where enabled
Why role documentation matters
Many support and onboarding issues are not product failures at all. They are the result of:- expecting a workflow that belongs to another role
- missing school setup
- missing class, section, or subject assignment
- missing permissions or incorrect current school context
Role summary
- admins usually manage school settings, structure, access PINs, users, and the broadest operational workflows
- deans usually share many academic and school-operations workflows with admins
- teachers typically work in teaching-facing modules such as results, tests, LMS, and attendance
- students mainly consume their own results, tests, courses, attendance context, and fee information