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

# Classroom Events and Scheduling

> Create, publish, start, end, archive, share, and understand Classroom events.

A Classroom event holds a live room's schedule, audience, settings, access, attendance, recordings, and history. Create and share the Kralis event so every participant enters through their existing account.

## Classroom home page

Open [Kralis Classroom](https://kralis.app/classroom) to see **Your classrooms**. The header also links to Whiteboards and Groups, while eligible non-student users receive **New classroom**.

Two filter rows control the event list:

| Filter | Choices | Purpose |
| - | - | - |
| Record state | Active or Archived | Switches between current records and retained archived history |
| Event status | All, Live, Scheduled, Drafts, Completed, or Cancelled | Narrows the selected record state by lifecycle status |

Students receive Active and Archived filters and all relevant status filters except Drafts. They do not receive **New classroom** or event-management actions.

Search matches visible classrooms using the submitted text. Filters and search work together. The result count reflects the current selection, and **Load more** appends the next set without removing events already displayed.

Events are ordered for practical use:

1. live events;
2. scheduled events from nearest to latest;
3. drafts;
4. completed and cancelled events from most recent to oldest.

## Who can create an event

The Kralis web app allows active non-student school users to create Classroom events. The creator receives the event’s protected **host** role.

Students see only events available to them and do not see the draft filter or the new-event action.

## Instant and scheduled events

### Instant

Use an instant event when the room should start on demand. It has no planned start or end timestamps. Start it explicitly when the host is ready.

### Scheduled

Use a scheduled event when participants need a known start and end. The end must be later than the start. The form shows both the event duration and how far the start is from the current time; selecting a start also proposes an end one hour later until the operator chooses another duration.

Scheduled events support:

* an early lobby window
* automatic activation at the scheduled start
* a live start countdown in the lobby
* live-room elapsed and remaining-time counters
* five-minute and two-minute end reminders
* automatic completion after the scheduled end
* Add to calendar, copy-link, and share actions

Calendar export and sharing are client-side conveniences. Access is still checked by Kralis when the recipient opens the event.

## Audience and context

Audience controls who can discover and enter the event. Context describes what the event is about.

### Audience scopes

* **Invite only**: only the creator, administrators, and users or collaboration groups granted access.
* **Class**: active students in the selected class. An optional section narrows that class audience.
* **School**: active users in the same school can receive participant access.

A section is never an independent audience. Select a class first; Kralis only accepts a general section or a section tied to that class.

### Academic context

* **Class and section** identify the intended student cohort.
* **Subject** labels the teaching context but does not grant access by itself.
* **Year and term** are captured automatically from the school’s current year and term when the event is created. They are shown on the details page and are not selected manually in the event form.

An event may remain generic with no class, section, or subject.

## Event settings

The event form also controls:

* participant microphone, camera, and screen-sharing defaults
* chat and raise hand
* waiting room
* recording policy: disabled, manual, or automatic
* maximum participants
* minutes before start when the lobby opens
* minutes after start that count as late
* minimum attendance percentage

The minimum attendance percentage is the percentage of the planned event window a user must attend before duration is sufficient for **present** or **late**. A lower percentage becomes **partial**.

## Lifecycle and available actions

| State | Meaning | Typical actions |
| - | - | - |
| Draft | Not visible to ordinary audience members | Edit, grant access, publish, start an instant event, cancel, archive |
| Scheduled | Published and waiting for its start | Edit, manage access, enter early lobby, start when allowed, cancel |
| Live | A current media session exists | Join, manage participants, present, record, end |
| Ended | The event and active sessions are closed | Review attendance, sessions, chat, and recordings; archive |
| Cancelled | The event will not run | Review details; archive |

Draft scheduled events must be published before ordinary audience members can discover them. Instant events are started directly rather than published.

The main timeline places live events first, then scheduled events from nearest to latest, then drafts, then completed or cancelled history from most recent. Users can search, filter by status, switch between active and archived records, and load additional cursor-paginated results. Students receive the same relevant history but not draft controls.

## Event details page

The event details page is the central record before, during, and after a classroom.

| Area | Available information or action |
| - | - |
| Main actions | Enter, edit, publish, start, end, cancel, share, copy link, add to calendar, archive, or restore when permitted |
| Classroom setup | Audience, role and live-setting summary |
| Whiteboards | View attached boards, create and attach a new board, attach an existing board, or detach one |
| Session history | Every live run with start, end, duration, participation, presentation, and associated recordings |
| Recordings | Processing state, preview, publish, unpublish, playback, and delete controls |
| My attendance | The current user's read-only status, first join, duration, and percentage |
| Academic context | Class, section, subject, year, and term |
| Activity | Joined and expected counts plus a manager link to the complete attendance page |
| Access | Direct user and collaboration-group roles for an open event |
| Audit history | Important management actions visible to authorized managers |

Closed events keep their history stable. They do not accept new access grants or new whiteboard attachments.

## Automatic scheduling

Classroom opens the lobby at the configured early-entry time, starts an automatically scheduled event at its planned start, and ends it after its planned end. While waiting, the lobby shows a live countdown and moves an admitted user into the room when the event begins.

A brief update delay can occur around the scheduled start or end. Participants should remain on the lobby or live-room page while Classroom refreshes the event state.

## Archive is not delete

Archiving removes an eligible event from the active listing without destroying attendance, sessions, chat, recordings, or audit history. Draft, ended, and cancelled events may be archived and later restored. Live and scheduled events must first reach an eligible state.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.