Exams¶
Exams are the central entity. Each exam belongs to an institute and is linked to an EMS environment and a SEB configuration.
Creating an Exam¶
- Navigate to
/<institute>/admin/exams/exam/→ Add - Fill in:
- Exam Name: Display name
- EMS Environment: Which EMS this exam uses
- Faculty: Optional faculty grouping
- Browser Configuration: SEB settings template
- Required Seats: Number of seats (for remote app pre-warming)
- Configure scheduling:
- Start Date/Time: When the exam window opens
- End Date/Time: When the exam window closes
- Strict Time: If enabled, students can only access during the scheduled window
- Session Cleanup Delay: Minutes after exam end before closing sessions (default: 30)
- Set Owner and optionally Additional Owners
- Click Save
Exam Status¶
| Status | Description |
|---|---|
| Concept | Draft — still being configured |
| Published | Active — SEB config generated, students can access |
| Error | Sync or generation failed |
Publishing¶
When you publish an exam:
- The SEB configuration file (.seb) is auto-generated
- The browserConfigKey and examKeySalt are stored on the exam
- An 8-character access code is auto-generated (e.g., AB12CD34)
- Students use this code to enter the exam
Built-in EMS Publishing¶
For SES (built-in) exams, publishing additionally requires: - At least one AI generation process must be completed - All questions must be frozen (locked from regeneration)
Exam Session Lifecycle¶
| State | Description |
|---|---|
| pending | Student authenticated but hasn't started |
| active | Student is taking the exam |
| submitted | Student submitted answers |
| closed | Session closed by admin or timeout |
Student Entry¶
Students access exams via the exam entry page at /<institute>/exam-entry/ using their 8-character access code. They authenticate via the institute's OIDC IdentityProvider.