<!-- generated by php artisan docs:split-brd from brd/BRD-Morvia-Project-Guide-en.md — edit the BRD, not this file -->

#### ADM-049 | Admin users, roles and permissions
**Source:** p.140–142 · **Actor:** system administrator
- **Admin users:** name · email · role · status · last login. **Actions:** add admin user · edit ·
  suspend · assign role.
- **Roles:** internal permissions instead of full control for everyone. Example roles: **system manager** ·
  **courses and content officer** · **finance officer** · **operations and support officer**.
- **Permissions** are controlled per module and action: view · add · edit · approve · reject · cancel ·
  manage settings · view reports.
- **Rule:** an admin user sees and performs only the functions they have permission for.
- **Built as (TD-28, TD-29):** permissions are a modules × actions grid (view, add, edit, delete, approve, reject, cancel, suspend, settings, reports); a role held by admin users cannot be deleted; suspending an admin records the suspension and locks them out, and nobody can suspend themselves.

**Acceptance, rules and screen notes citing ADM-049:**

- BR-ACC-01 — Trainee registration is free; independent trainers self-register and need admin approval; affiliated trainers, centers, hall providers and admin users never self-register. — TRN-002, TRR-002, CTR-005, ADM-010, ADM-015, ADM-049
- BR-ACC-06 — Every admin action is limited by role permissions; sensitive admin actions are written to the activity log with previous state, new state and reason. — ADM-049, ADM-050
