Use Cases · Article A061

BigBlueButton for Universities: Lectures, Labs, and Office Hours

Discover how universities use BigBlueButton to deliver live lectures, virtual labs, and student office hours — with reliable recordings, native LMS integration, and the hosting infrastructure needed to support hundreds of concurrent sessions without degradation.

Universities are running more of their teaching online than ever — not as a temporary measure, but as a permanent expansion of how higher education is delivered. Hybrid lectures, asynchronous lab sessions, virtual office hours, dissertation supervisions, faculty seminars, and student study groups all now expect a conferencing platform that is purpose-built for the academic environment: one that integrates directly with the LMS, records reliably, gives instructors pedagogical tools beyond a basic video call, and keeps student data under institutional control.

BigBlueButton for universities addresses all of these needs in a single, open-source platform. Unlike general-purpose tools such as Zoom or Microsoft Teams, BigBlueButton was designed from the ground up for online education — with multi-user shared whiteboards, breakout rooms for tutorial groups, polling for formative assessment, shared notes, and a recording system that ties directly to Canvas, Moodle, or Blackboard via LTI 1.3. Instructors get the tools they actually need for teaching. IT teams get a platform they can govern, audit, and scale on their own terms.

This guide covers the three core university use cases in depth — large-group lectures, small-group virtual labs, and one-to-one office hours — explaining exactly how BigBlueButton handles each scenario, how recording works in each context, how to record BigBlueButton meetings and make them accessible to students in Canvas, and what the hosting infrastructure needs to look like to support a full university deployment without peak-day failures.

We also address the hosting and infrastructure layer honestly — because a BigBlueButton deployment that is correctly sized and managed is a completely different experience from one running on an undersized server. For universities, the difference between self-hosted BigBlueButton on a single VM and managed BigBlueButton on an elastic cluster is the difference between a tool that fails on exam review day and one that simply works.

Quick Navigation

What BigBlueButton for Universities Actually Means — and What It Requires

BigBlueButton is an open-source web conferencing system built specifically for education. For universities, it functions as a complete virtual classroom platform — not merely a video call tool. It supports the full spectrum of higher education teaching formats: large-group lectures with 100+ students, small breakout tutorial groups, virtual laboratory sessions with screen sharing and shared annotation, one-to-one faculty office hours, and department-wide seminars or town halls.

What makes BigBlueButton distinct from general-purpose conferencing tools in a university context:

• Purpose-built pedagogy tools: Multi-user shared whiteboards with multi-shape annotation; breakout rooms that the instructor can visit and monitor; polling with real-time results; shared notes synced across all participants; and hand-raise queues that keep large lectures manageable.
• Native LTI 1.3 integration: Launches directly from Canvas, Moodle, or Blackboard courses. Students join with one click. Instructor and student roles are mapped automatically. No separate logins, no room codes to distribute.
• Institutional recording ownership: All recordings stay on your infrastructure — not in a vendor's cloud. Lecture recordings, lab session recordings, and office hour recordings are governed by your retention policy, not a third-party vendor's storage limits.
• Open-source transparency: Universities with IT security offices can audit the codebase, review data flows, and satisfy procurement requirements that proprietary SaaS tools cannot meet.
• Scalable hosting model: From a single department pilot to an institution-wide deployment with hundreds of concurrent sessions, BigBlueButton scales on dedicated infrastructure — self-hosted or managed.

The Three Core University Use Cases: Lectures, Virtual Labs, and Office Hours

Each university use case has distinct requirements for room configuration, participant count, recording behaviour, and infrastructure load. Understanding these differences is essential for sizing your deployment correctly and configuring BigBlueButton appropriately for each scenario.

Use Case 1: Large-Group Lectures (50–300+ Students)

BigBlueButton handles large-group online teaching through a combination of presentation mode, webcam management, and audience engagement tools. For lectures with 50–300 students:

• The instructor shares their presentation (PDF or PowerPoint) directly in BigBlueButton — no screen share required, reducing bandwidth load and ensuring all students see a clean slide view.
• Student webcams can be selectively enabled or disabled — for very large sessions, disabling student webcams significantly reduces server bandwidth and CPU load.
• Polling tools allow the instructor to run formative assessment checks mid-lecture — results display in real time and are included in the recording.
• Hand-raise and reaction features allow students to signal questions or confusion without disrupting the session flow.
• Recording on BigBlueButton for lectures: the instructor clicks Record at the start of the session. The Presentation format captures slides, audio, and the shared whiteboard — producing a compact, searchable recording that is far more appropriate for lecture archives than a full video recording.

Use Case 2: Virtual Laboratory Sessions (10–30 Students)

Virtual labs require more interactive configurations than lectures. BigBlueButton supports lab-format teaching through:

• Screen sharing from the instructor's machine for software demonstrations, lab equipment simulations, or data analysis walkthroughs.
• Multi-user whiteboard annotation — students can annotate over the instructor's shared presentation or diagram simultaneously, enabling collaborative problem-solving that mirrors in-person lab work.
• Breakout rooms for small-group lab exercises — the instructor sets up groups of 3–5 students in separate breakout rooms, then rotates between them to provide guidance. Breakout rooms in BigBlueButton include their own whiteboard and shared notes.
• Recording virtual lab sessions: lab sessions are best recorded in Video format (which captures webcams and screen share) rather than Presentation format. Advise students at session start that recording is active — especially important for lab sessions that may include student work products or discussions.

Use Case 3: Faculty Office Hours (1–5 Students)

Office hours in BigBlueButton are typically configured as persistent rooms that students access via a Canvas course link or a shared URL. For virtual office hours:

• The instructor sets up a dedicated BigBlueButton room for office hours — accessible from their Canvas profile page or a course module. Students join when they need support, without needing to email for a Zoom link.
• The waiting lobby feature allows the instructor to manage a queue — one student in the active session while others wait in a lobby, preserving privacy and meeting the same expectation as a physical office door queue.
• Shared notes allow the instructor and student to co-author feedback or study notes during the session — these notes can be downloaded at the end of the meeting.
• Recording office hours: most institutions advise against recording one-to-one office hours by default due to FERPA and privacy considerations. If recording is needed (for example, for a supervised dissertation session), both parties should explicitly consent and the recording should have restricted access in the LMS.

Infrastructure implication: Office hours sessions are CPU-light individually but add up across a faculty. A university with 200 faculty running simultaneous office hours creates 200 concurrent BigBlueButton sessions — more than many self-hosted single-node installations can handle. Peak concurrency planning must account for office hours load, not just lecture load.

BigBlueButton vs Zoom, Teams, and Meet for University Teaching: An IT Perspective

University IT departments evaluating conferencing platforms need a comparison that goes beyond feature lists. The table below focuses on what matters for a higher education deployment: pedagogy tools, LMS integration, data governance, and operational overhead.

For university IT teams: BigBlueButton's combination of purpose-built pedagogy tools, native LTI 1.3 recording sync to Canvas, and full data sovereignty makes it the strongest platform for institutions where the LMS is the centre of the student experience. The infrastructure responsibility is the genuine trade-off — which managed hosting addresses directly.

Self-Hosted vs Managed BigBlueButton for Universities: The Honest Comparison

Universities choosing BigBlueButton face a foundational decision before any teaching begins: self-host on university-managed infrastructure, or use a managed BigBlueButton hosting provider. This choice determines the reliability, scalability, and operational burden of everything that follows.

For most universities without a dedicated Linux infrastructure team, managed BigBlueButton hosting delivers significantly better lecture-day reliability than self-hosted deployments — at a total cost that is often lower than the IT staff time a self-hosted deployment consumes.

Sizing for Universities: Why Concurrent Sessions — Not Student Count — Is the Right Metric

University IT teams consistently size BigBlueButton incorrectly by planning around total student enrolment. The correct planning variable is peak concurrent sessions — the maximum number of simultaneous BigBlueButton rooms running at your busiest moment across lectures, labs, and office hours combined.

University-specific sizing considerations:

• Large lectures (100+ students, recording enabled): 4–6 vCPUs per room; higher if screen sharing and multiple webcams are active. Recording post-processing adds 2–3× the live-session CPU after the session ends.
• Virtual labs (15–30 students, screen sharing + webcams): 2–4 vCPUs per room. Labs typically use more bandwidth per participant than lectures due to active screen sharing and multiple webcam streams.
• Office hours (1–5 participants): CPU-light individually — approximately 0.5–1 vCPU per session. But 200 simultaneous faculty office hours sessions creates significant aggregate load.
• Peak exam week scenario: Assume your highest teaching-week concurrent count and multiply by 1.3–1.5× to account for recording post-processing running simultaneously with live sessions. Size for this number, not for your average.
• Storage for lecture recordings: A 1-hour lecture in Presentation format generates approximately 200–400 MB. A full semester of 50 lectures across 100 courses = 10–20 TB. Plan storage capacity at the beginning of the academic year, not mid-semester.
• TURN server: Essential for students connecting from home broadband, mobile data, or through strict campus firewall policies. Without TURN, a meaningful percentage of your student population will silently fail to connect audio or video — a support ticket disaster during the first week of term.

WebRTC in BigBlueButton: What University IT Teams Need to Understand

Every BigBlueButton audio, video, and screen-share stream that flows during a university lecture, lab, or office hour session travels through WebRTC — the browser-native real-time communication protocol. Understanding how WebRTC works in BigBlueButton is essential for diagnosing connectivity issues, sizing infrastructure correctly, and supporting faculty and students effectively.

• No plugin required: Students and faculty join BigBlueButton lectures directly from Chrome, Firefox, or Edge — no installed application needed. This is critical for university environments where students use a wide range of personal devices.
• SFU media routing: BigBlueButton uses a Selective Forwarding Unit (mediasoup in BBB 2.6+) to route video and screen-share streams between participants. All SFU processing runs on your server — this is why CPU headroom is non-negotiable for large-lecture deployments.
• TURN server requirement: Students connecting from home broadband with symmetric NAT, from mobile networks, or from devices behind strict university firewall policies (common for distance learners) require a TURN relay. Without TURN, these students see their audio and video fail silently — which presents as a platform failure to the instructor even though the BBB software is functioning correctly.
• Jitter and packet loss on student networks: Distance learners and international students often connect on variable-quality broadband or mobile data. BigBlueButton's adaptive bitrate reduces stream quality gracefully under congestion, but very poor connections will still result in degraded audio/video. Advise faculty to set realistic expectations for distance learner video quality.
• FreeSWITCH audio layer: BigBlueButton uses FreeSWITCH for its audio conferencing component. For large lectures, FreeSWITCH handles the audio mixing for all participants — this is separate from the WebRTC video SFU and has its own CPU cost. For 200-student lectures, audio processing alone can consume 2–4 vCPUs.
• Diagnostic tip for IT teams: When faculty report "it works for me but not for some students," the cause is almost always TURN configuration, UDP port blocking, or browser version incompatibility — not BigBlueButton application errors. Check TURN connectivity first, then WebRTC diagnostics, before escalating to application-level debugging.

Security, FERPA, and Student Data Governance for University BigBlueButton Deployments

Universities operating under FERPA, GDPR, or equivalent national student data protection regulations have governance requirements that generic SaaS conferencing tools struggle to satisfy definitively. BigBlueButton's open-source, self-owned infrastructure model addresses these requirements structurally — not contractually.

Data Sovereignty for Lecture and Lab Recordings

• All BigBlueButton session data — participant names, chat logs, poll responses, whiteboard content, and recordings — is stored on your server. No data is sent to BigBlueButton's development team or any third party.
• Lecture recordings containing identifiable student information (questions, quiz responses, webcam video) are FERPA-protected educational records. Storing them on your own governed infrastructure is definitively compliant. Storing them on a vendor's cloud requires a FERPA agreement and trust in vendor compliance.
• Define and implement a recording retention policy before deploying BigBlueButton at scale. A common university policy is 12–24 months rolling retention. Automate deletion and document the policy for compliance audits.

Access Control via LTI Role Mapping

• LTI 1.3 role mapping ensures that Canvas Instructors automatically receive the BigBlueButton Moderator role — with recording controls, session management, and the ability to end the session. Canvas Students receive the Viewer role — no recording controls, no session management.
• Recording access is scoped to enrolled course participants via Canvas enrollment — students from other courses cannot access lecture recordings even with a direct link.
• TLS encryption is mandatory on all BigBlueButton endpoints — HTTPS for the web interface, WSS for WebSocket signalling. All media streams are encrypted in transit via DTLS-SRTP (WebRTC standard).

Audit and Compliance

• BigBlueButton application logs capture session start/end times, participant joins and leaves, recording start/stop events, and recording access. Ship these logs to your university SIEM for audit trail purposes.
• For universities with accessibility requirements (ADA, WCAG), BigBlueButton's Presentation-format recordings include keyboard-accessible playback and can be captioned via third-party captioning services integrated at the post-publish stage.

Review BiggerBluButton's data governance and security commitments: biggerbluebutton.com/terms-and-conditions

How to Record Lectures, Labs, and Office Hours in BigBlueButton: A University Guide

Recording on BigBlueButton is a core feature for universities — lecture recordings allow students who missed a session or need to review content to access the material on their own schedule. Here is the complete guide to recording BigBlueButton meetings in each university context.

Step-by-Step: How to Record a BigBlueButton Lecture

1. Launch from Canvas as instructor: Open the Canvas course, click the BigBlueButton LTI activity, and join as the moderator. Your Canvas Instructor role maps automatically to the BigBlueButton Moderator role — recording controls are visible only to you.
2. Upload your presentation: Use the Upload Presentation button to add your PDF or PowerPoint slides directly to the BigBlueButton session. This is preferable to screen sharing for lectures — it reduces bandwidth consumption and produces cleaner Presentation-format recordings.
3. Start recording: Click the red Record button in the top header bar before students begin joining — or at any point after the session has started. To add a recording to a BigBlueButton conference after it has already started, simply click Record at any point — only content from that click forward is captured in the recording.
4. Announce recording to students: BigBlueButton displays the recording indicator to all participants, but a verbal announcement is best practice — and a legal requirement in many jurisdictions. Recording chat is also captured in Presentation-format recordings, so remind students that public chat is part of the recording.
5. Stop or end the BigBlueButton recording: Click the Record button again to pause mid-session (for example, during a Q&A you do not want recorded), or end the meeting to stop recording entirely and begin post-processing. Pausing and resuming creates separate recording segments.
6. Post-processing: After the session ends, BigBlueButton automatically processes the raw recording into a web-playable Presentation format (or Video/Podcast format depending on your server configuration). This takes 30 minutes to 2 hours for a 90-minute lecture. Do not be alarmed if the recording does not appear immediately — check back after the post-processing window.
7. Access BigBlueButton recordings: Once processing is complete, the recording appears in the Recordings tab of the BigBlueButton LTI activity inside your Canvas course. Students can view and listen to the BigBlueButton recording directly in their browser — no download required, no additional login.
8. Downloading recordings from BigBlueButton: If your server administrator has enabled downloads, a download link appears next to each recording. Students or instructors can download a local copy. For lecture recordings with student content, consider whether your institutional policy permits student download of recordings before enabling this feature.

Recording Format Recommendations by Use Case

For a complete list of BigBlueButton recording formats and features: biggerbluebutton.com/features

Canvas BigBlueButton Recording: How University Students Access Lecture Recordings

The Canvas BigBlueButton recording workflow is one of the most practically important topics for university IT teams and faculty — because this is what students actually experience when they try to access a missed lecture or review a lab session. Here are the three methods, from simplest to most governed.

Method 1: LTI-Native Recording Tab (Standard University Setup)

When BigBlueButton is integrated into Canvas via LTI 1.3, lecture recordings from that course's sessions appear automatically in the Recordings tab of the BigBlueButton activity — no manual action required from the instructor after the session ends.

1. Students open their Canvas course and click the BigBlueButton LTI activity link.
2. They select the Recordings tab — all processed recordings for that course appear here, listed by date, title, and duration.
3. Students click the recording name to view or listen to the BigBlueButton recording in their browser. Access is automatically limited to enrolled students — unenrolled users cannot reach the recording even with a direct link.
4. If a student asks "where do I find conference recordings on BigBlueButton?" — the answer for LTI-integrated Canvas courses is: inside the Canvas course, in the BigBlueButton activity, under Recordings.

Method 2: Sharing a Recording Link to Canvas Manually

1. After a recording is processed, the instructor or administrator copies the recording's playback URL from the BigBlueButton Recordings interface.
2. The URL is pasted into a Canvas Announcement, Page, or Module as an External URL item. Students click the link to open the BigBlueButton recording in their browser.
3. To send a BigBlueButton video recording to a Canvas assignment submission or feedback page, embed the URL in the assignment description. Ensure recording visibility is set to "published" on the server before sharing.

Method 3: Centralised Media Library for Large-Scale University Recording Archives

1. Use BigBlueButton's post-publish API hooks to automatically push completed recordings to a university media library (Kaltura, Panopto, or a custom S3-backed solution).
2. From the media library, generate LTI deep links or embed codes for each recording and place them in the corresponding Canvas course module — giving students seamless browser-based playback with centralised access control and FERPA-compliant retention management.
3. This approach is recommended for universities with 500+ courses per semester, where manual recording management creates unacceptable administrative overhead and audit trail gaps.

Recommended Resources for University BigBlueButton Deployments

The following BiggerBluButton resources are specifically useful for university IT directors, instructional technology teams, and procurement leads evaluating or deploying BigBlueButton for lectures, labs, and office hours.

• Compare managed BigBlueButton plans sized for university concurrent load — find a hosting tier that covers your peak lecture-week concurrent session count with recording storage included.
• Explore BigBlueButton features for university teaching — whiteboard, breakout rooms, polling, recording — full feature reference for instructional technology teams and faculty champions.
• Read BiggerBluButton's technical documentation for Canvas LTI 1.3 setup, recording configuration, and Scalelite clustering — essential reference for IT teams implementing a university-scale deployment.
• Contact our university deployment specialists for scoping, proof-of-concept support, and migration guidance — including peak concurrency modelling and Canvas LTI configuration support.
• Review our data governance, FERPA compliance, and security policy documentation — required reading for university procurement, legal, and compliance offices.
• Read more BigBlueButton university use case guides and best practices on our blog — covering recording workflows, hybrid teaching, Canvas integration, and infrastructure planning for higher education.

Frequently Asked Questions: BigBlueButton for University Lectures, Labs, and Office Hours

Ready to Deploy BigBlueButton Across Your University?

Get a fully managed BigBlueButton environment sized for university peak concurrency — with elastic cluster scaling, Canvas LTI 1.3 integration, governed lecture recording storage, and dedicated support from a team that understands higher education deployments.