Skip to content
Beta

Scholardemia is in beta.

Sessions, rooms & speakers

3 min readUpdated 10 July 2026Events & conferences

Sessions are the building blocks of an event programme. Each one says what is happening, when, where, and who is presenting, and can carry its own materials, seat limits, and live join details.

What a session holds

  • Basics: title, description, and start and end times in the event timezone.
  • Type: presentation, keynote, panel, workshop, break, lunch, opening, closing, networking, or a general session, so the schedule reads clearly at a glance.
  • Capacity: optionally limit seats for a session; attendees then reserve a place from the programme page and can see how many spots remain.
  • Live details: online and hybrid sessions can carry a join link shown to attendees.

Rooms & tracks

Rooms and tracks are labels you define in the programme parameters, such as a main room, a workshop room, or an online track. Assigning a session to a room places it in that column of the schedule, and the programme workspace warns when two sessions overlap in the same room. Attendees can filter the public programme by track. The event’s overall venue name and address come from the event location settings.

Speakers

Speakers are Scholardemia accounts linked to a session. The public programme shows each speaker’s profile card with their name, title, institution, photo, bio, and scholarly links such as ORCID and Google Scholar, drawn from their Scholardemia profile, so speaker pages stay current without re-entering anything. When accepted submissions are published into the programme, the authors are attached as the session’s speakers automatically.

Materials & feedback

  • Session materials: speakers and organisers can upload files to a session, choosing whether each file is visible publicly, to attendees, or to speakers only. Uploaders can remove their own files; organisers can manage all of them.
  • Session voting: signed-in attendees can give a session a thumbs up or down from the programme, giving organisers a quick read on what resonated.
Scheduling happens in the programme workspace. For day layouts, auto-generating a draft from accepted submissions, and publishing, see Build the programme.

Still stuck? Talk to a person.

Our support team reads every message. Include what you were doing, any error message, and a screenshot if you have one; it usually saves a round-trip.

Email support