Roles and Permissions - Kralis Docs

Kralis combines role-driven product behavior with permission-aware operations.

Main user-facing roles

admin
dean
teacher
student

Role	Default product focus
Admin	School setup, accounts, policies, billing, and broad operations
Dean	Academic and operational management
Teacher	Assigned teaching, assessment, course, Classroom, and attendance work
Student	Personal learning, tests, Classroom, results, attendance, and fees

Practical meaning

Roles affect:

which sections appear in navigation
which workflows can be initiated
which school data can be viewed or changed

Important rule

Do not infer access only from the presence of a screen in a screenshot or guide. Actual behavior still depends on the signed-in user and the school’s configured permissions.

Classroom roles are event-specific

Classroom adds host, moderator, presenter, participant, and observer roles for one event. These do not replace the user’s global admin, dean, teacher, or student role.

the event creator is its host;
school administrators and deans can manage school events as moderators;
a teacher or other user may be a host, moderator, or presenter through an event grant;
a student may be a participant or observer through audience matching or a grant;
when several access sources apply, Kralis uses the strongest event role.

Permission layer	Example
Global school role	Teacher, student, dean, or admin
Relationship	Assigned subject, LMS enrollment, CBT eligibility, or class membership
Object-specific role	Classroom host, moderator, presenter, participant, or observer
Object state	Draft, published, live, ended, archived, or unavailable

See Classroom Access and Roles.