> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kralis.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Subjects and Users

> How to define subjects, operational roles, and basic permission expectations in Kralis.

After the academic structure exists, define what is taught and who is allowed to
operate each part of the school.

## Capabilities

This area supports:

* subject catalog setup
* role-aware user preparation
* permission groundwork
* creator accountability for student records where available

## Subjects

Subjects should be created clearly and consistently so score entry, reports, and
CBT setup remain understandable.

Keep names stable. Changing a subject naming style repeatedly creates operator
confusion even when the system still accepts the data.

## Users

The main operational roles are:

* admin
* dean
* teacher

These are all school-scoped in normal use. Operators should only see and manage
their own school's records through the application.

## Permission guidance

* give the smallest permission set that still lets the person do the work
* use admin accounts carefully
* keep role boundaries clear where the school wants accountability

## Student records and creators

Student creation can capture which signed-in user created the student record.
This helps answer who added a student when the system has that request context.

## Feature links

* [Subjects page](https://kralis.app/subject)
* [Teachers page](https://kralis.app/teacher)
* [Board Members page](https://kralis.app/dean)
* [Users page](https://kralis.app/user)