Skip to main content
Kralis combines role-driven product behavior with permission-aware operations.

​
Main user-facing roles

  • admin
  • dean
  • teacher
  • student

​
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.