Skip to content
Browse all help topicsSkip to article

Before you start

  • Session codes must be unique
  • Codes are shared with learners, so never put personal data in them

Steps

  1. Open the Sessions page
    Choose Sessions in the Admin app sidebar; the create-session form is at the top
  2. Fill in the fields
    Name, date and status; the session code is suggested from the name and date (example: DEMO-2026-01) and you can edit it
  3. Create
    After submitting, the session appears in the session list
  4. Change status
    Switch between draft, open, closed and archived in the sortable, paged list, which asks for confirmation before sending; you can also open a session’s detail page from its code and change it there

Scope: bound to a course or an event code

A session has one of two scopes. "Bound to one course" (the default and recommendation when you create one): that course's managers can manage the session automatically, and its code cannot be used for another course. "Not bound" (an event code): it works on the code alone, can be used for any course's quizzes and feedback, is managed only by the teachers assigned to it, and never gives a course manager automatic access; good for workshops that span several courses or campus events.

  • When you create a session you choose one of the two; choosing "Bound to one course" requires picking a course
  • The "Course" column shows the bound course or "Not bound (event code)"; tick "Only sessions that are not bound" to find them quickly
  • Use "Edit course" to bind, rebind or unbind; use "Bind unbound sessions" to bind several unbound sessions to one course in a single step
  • Before a change you see its impact: which course managers gain or lose the ability to manage the session, that the session's teachers can claim to become the manager of a course that has none, and how many feedback responses the session already has
  • If a bound session already has course feedback, rebinding or unbinding needs the session code typed to confirm; every change is written to the audit log

Warning

Binding is an authorization change, not just a label: it decides which course managers can manage the session.

Expected result

The session appears in the list with the status you set. Only open sessions accept learner submissions.

Common problems

  1. Duplicate code
    Choose a different session code.
  2. Learners can’t submit
    Check that the session status is open.

Was this article helpful?

Feedback is anonymous: only a daily count per article, language and answer is kept.