Webinar and Workshop Series

A recurring session series: registration, a stage for the talk, breakout rooms for exercises and a recordings archive.

  • 5 categories
  • 20 channels
  • 8 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

UPCOMING

  • welcome

    What this series is and how to attend.

  • how-sessions-run

    The shape of a session: talk, questions, breakout, notes.

  • next-session

    Date, topic, presenter. One card, kept current.

  • session-schedule

    The term ahead.

  • register

    Confirm you are coming and pick up session pings.

LIVE

  • Main Stage
  • live-questions60s slowmode

    One question per post during the session. The moderator reads from here.

  • live-chat

    Reactions and side conversation while the talk runs.

BREAKOUTS

  • Breakout One
  • Breakout Two
  • Breakout Three
  • breakout-notes

    One post per group: what you worked on and what you concluded.

AFTER

  • recordings

    One post per session: recording, slides, unanswered questions.

  • session-followup

    The week after. Ask what you did not get to ask.

  • topic-requests

    What you want a session on. Votes decide.

  • presenter-signups

    Offer to present. Say the topic and roughly when.

ORGANISERS

  • run-of-show

    Timing and who does what.

  • presenter-prep

    Shared with the presenter for the session they are running.

  • vetox-logs

    Vetox Logs output.

  • Green Room

Roles

  • OrganiserAdministrator
  • ModeratorModerator
  • PresenterModerator
  • FacilitatorModerator
  • Attendee
  • Session Pings
  • Muted

Overview

Built for a series that runs the same shape every few weeks: someone presents, attendees do an exercise, and the recording goes up. Upcoming holds #next-session, a read-only card with the date, topic and presenter, plus #session-schedule for the term ahead and #register where attendees confirm. During the session the Stage is the room: the presenter and panellists speak, everyone else listens, and #live-questions runs alongside with a slowmode so the moderator can read it rather than fight it. Breakouts are three voice rooms used for the exercise half, capped small enough that everyone in them speaks; #breakout-notes is where each group posts what they came up with, which is the part most webinar servers lose entirely. After the session, #recordings is a read-only archive with one post per session — link, slides, and the questions that were not reached — and #session-followup is the open channel where the conversation continues for the week afterwards. Between sessions, #topic-requests collects what attendees want covered and #presenter-signups is how the series finds its next speaker, both of which decide whether a series survives past session six. Presenter is a per-session role granted and removed; Facilitator runs breakouts; Attendee is everyone else. Nothing here assumes a permanent community, because most series are a room that fills and empties.

When to use it

A webinar series usually lives on a calendar invite and a folder of recordings, which means attendees have nowhere to ask a follow-up and the exercise half produces nothing anyone keeps. This layout gives the series a room: registration and schedule in one place, a stage for the talk with a moderated question channel beside it, breakout rooms whose output is written down, and an archive that includes the questions there was no time for.

What makes it different

  • One read-only card answers what the next session is, so nobody asks in chat.
  • Live questions run in a slowmoded channel the moderator can actually read.
  • Breakout groups post their output, so the exercise half leaves something behind.
  • The archive includes unanswered questions, which is where the next topic comes from.

Recommended Vetox setup

  • Reminders

    Set Reminders in #next-session so registered attendees get a notice a day and an hour before the stage opens.

  • Self-Roles

    Post a Self-Roles panel in #register so attendees opt into session pings and the Attendee role is self-served.

  • Suggestions

    Run Suggestions on #topic-requests so the series can see which topics attendees actually voted for.

  • Temp Voice

    Enable Temp Voice beside the breakout rooms so a large session can split into more groups and tidy up afterwards.

Questions

Why a stage channel instead of a normal voice channel?

A stage separates speakers from listeners at the permission level, so a hundred attendees cannot unmute by accident and the presenter does not spend the first five minutes asking people to mute. It also gives the moderator a clean way to bring an attendee up to ask a question live and then move them back down.

Do we need #presenter-signups if the same person always presents?

A series with one presenter is one burnout away from ending. The channel costs nothing while it is unused and is the difference between a series that survives its founder and one that does not. If you are certain, delete it and keep #topic-requests, which matters more.

How long should recordings stay up?

The layout assumes indefinitely, with one post per session in a read-only channel. If your material dates quickly, add the recording date to each post and prune on a schedule you state in #session-schedule. What matters is that the rule is written down, because an archive with silently missing sessions is worse than a short one.

Common mistakes

  • Letting live questions run in an unmoderated channel, where the moderator loses them in the scroll.
  • Running breakouts with no written output, so an hour of group work produces nothing anyone can revisit.
  • Publishing recordings without the unanswered questions, which is the cheapest source of future topics.

Consider instead

  • Conference Server This is a multi-track event over one or two days rather than a repeating single session.
  • Online Tutoring Center Teaching is one to one or in small fixed groups rather than a presentation to an audience.

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages