LMS Integrations · Article A012

BigBlueButton LTI 1.3 Setup for Canvas: Step-by-Step

Learn how to configure BigBlueButton LTI 1.3 inside Canvas for smooth, secure LMS launches — covering key steps, settings, and common mistakes. A practical guide for IT teams and instructional technologists who need reliable video conferencing and recording inside their LMS.

Deploying BigBlueButton inside Canvas via LTI 1.3 is one of the most requested — and most misunderstood — LMS integration tasks for IT administrators and instructional technologists today. When it works correctly, instructors can launch live sessions directly from course pages, students join with a single click, and recordings sync automatically back into the LMS. When it goes wrong, you get OAuth errors, broken role mapping, missing recordings, and support tickets that pile up fast.

This guide covers every step of the BigBlueButton LTI 1.3 setup for Canvas: from registering the tool in your Canvas admin panel, to configuring the OIDC login URL and redirect URIs on the BigBlueButton side, to verifying that recordings appear and that Canvas grade passback works as expected. We also address recording workflow questions — including how to record BigBlueButton meetings, how to access BigBlueButton recordings, how to share a recording from BigBlueButton back to Canvas, and how students can find conference recordings inside their courses.

For schools and universities, BigBlueButton's WebRTC-based architecture means video, audio, and screen-share all travel through your browser — no plugin needed. But that also means your hosting infrastructure carries the full load. A poorly sized or self-hosted BigBlueButton server will crack under concurrent sessions exactly when you need it most: midterms, live lectures, or all-hands training days. Managed hosting removes that risk.

Whether you are an IT director evaluating options, a Canvas admin doing the first integration, or an instructional designer trying to understand recording sync, this article gives you a complete, honest picture — technical steps, tradeoffs, and best practices included.

Quick Navigation

What Is LTI 1.3 and Why Does It Matter for BigBlueButton Canvas Integration?

LTI stands for Learning Tools Interoperability, an IMS Global standard that allows external tools — like BigBlueButton — to launch securely inside an LMS like Canvas, Moodle, or Blackboard. LTI 1.3 replaces the older 1.1 standard and uses OAuth 2.0 with JSON Web Tokens (JWT) instead of plain shared secrets, making it significantly more secure and flexible.

For a BigBlueButton LTI 1.3 setup in Canvas, the integration means:

• Canvas authenticates users via OIDC (OpenID Connect) before launching the BigBlueButton room — no separate login required for students or instructors.
• Role information (instructor, student, TA) is passed automatically so BigBlueButton can assign the right permissions — including who can start a recording.
• Deep Linking lets instructors embed specific BBB rooms into individual course modules without extra configuration.
• Names and Roles Provisioning Services (NRPS) allows BigBlueButton to pull the course roster for attendance reports and recording-access control.
• Assignment and Grade Services (AGS) enable grade passback — useful when attendance or participation in a BigBlueButton session is graded inside Canvas.
• Recording sync can be tied to the LTI context, meaning recordings appear automatically inside the correct Canvas course after the session ends.

BigBlueButton and Hosting: Why the Server Beneath the LTI Tool Matters

BigBlueButton is an open-source web conferencing platform built specifically for education. It offers breakout rooms, shared whiteboards, polls, chat moderation, and — critically for LMS users — deep recording capabilities. Because it is open-source, any institution can install it. But installation is only the beginning.

Unlike SaaS tools such as Zoom, BigBlueButton requires you to own or rent the server infrastructure that processes every audio stream, video stream, screen share, and recording. When 30 concurrent sessions run simultaneously during a peak exam week, the server must handle all of them without degradation. A server that is correctly sized for 10 concurrent rooms will fall over at 30 — and that failure shows up as frozen video, dropped audio, and recording jobs that never complete.

This is why the hosting decision is inseparable from the LTI 1.3 integration decision. Your Canvas users will judge the quality of BigBlueButton by the performance of your server — not by the quality of the software itself. Institutions that invest in correctly sized, managed BigBlueButton hosting consistently report higher adoption rates, fewer support tickets, and more reliable recording workflows.

For peak concurrency planning: a rough rule of thumb is that each concurrent BigBlueButton room with 20–30 participants and recording enabled requires approximately 2–4 vCPUs and 4–8 GB of RAM, plus dedicated bandwidth. Multiply by your expected peak room count and add 30–40% headroom for recording post-processing. This math gets complicated fast — which is why many institutions move to managed clusters.

BigBlueButton vs Zoom, Teams, and Google Meet: An IT Impact Comparison

When IT teams evaluate conferencing tools for Canvas integration, they compare BigBlueButton against Zoom, Microsoft Teams, and Google Meet. Each has genuine strengths. The comparison below focuses on what matters most from an IT governance and LMS integration perspective.

BigBlueButton's native LTI 1.3 support and data-ownership model make it the strongest choice for institutions with strict FERPA, data-residency, or audit requirements. The trade-off is infrastructure responsibility — which managed hosting resolves.

Self-Hosted vs Managed BigBlueButton: Which Is Right for Your Canvas Deployment?

Many institutions start with self-hosted BigBlueButton and later migrate to managed hosting after experiencing peak-day failures or mounting sysadmin overhead. The table below summarises the key differences to help you make an informed decision before committing to either path.

Recommendation for most institutions: start with managed hosting. The time savings on setup, LTI 1.3 configuration, and recording management typically justify the cost within the first semester.

Sizing and Requirements: Why Concurrent Users Is the Right Question

When scoping BigBlueButton capacity, the most common mistake is asking "how many total users do we have?" The right question is: "how many simultaneous BigBlueButton rooms will be running at the same moment?" A university with 10,000 enrolled students may only ever run 40 concurrent rooms — or it may run 200 on a Tuesday morning. That peak number drives every infrastructure decision.

Baseline sizing considerations for a BigBlueButton server with recording enabled:

• CPU: Minimum 8 dedicated vCPUs for a small deployment; 16–32 vCPUs for institutions with 20+ concurrent rooms. Recording post-processing is CPU-intensive and competes with live sessions if not isolated.
• RAM: 16 GB minimum; 32–64 GB for medium deployments. Each active room with screen sharing and recording uses 500 MB to 1.5 GB depending on participant count.
• Disk: Recordings accumulate quickly — a 1-hour session generates 200–800 MB depending on quality. Plan for NFS or S3-compatible storage for anything beyond a pilot deployment.
• Network: Symmetrical bandwidth matters. A single 30-person room with webcams can use 30–50 Mbps. Budget accordingly for peak concurrency scenarios.
• TURN server: Required for users behind strict firewalls (common in corporate and K-12 networks). Without TURN, some participants will silently fail to connect audio/video through WebRTC.
• Cluster vs single node: Beyond roughly 150 concurrent users, a single-node deployment becomes a reliability risk. Horizontal scaling via a load-balanced cluster is recommended for production at scale.

WebRTC in BigBlueButton: A Plain-Language Overview for IT Teams

WebRTC (Web Real-Time Communication) is the browser technology that powers BigBlueButton's audio, video, and screen-sharing — no plugin, no installed application required. When a student clicks the LTI link in Canvas and joins a BigBlueButton room, their browser negotiates a direct media connection using WebRTC protocols.

Here is what that means in practice for your infrastructure:

• Media routing: BigBlueButton uses a Selective Forwarding Unit (SFU — Kurento or mediasoup depending on version) to route media between participants. The SFU runs on your server and scales with the number of concurrent streams. This is one reason CPU headroom matters so much.
• Jitter and packet loss: WebRTC is UDP-based. On high-quality corporate or campus networks, this is fine. On congested home or mobile networks, jitter and packet loss cause frozen video and choppy audio. Adaptive bitrate helps, but does not eliminate the problem.
• TURN server: When symmetric NAT or strict firewalls block direct peer connections, a TURN relay is required. BigBlueButton needs a TURN server configured — without it, participants behind certain firewalls (common in schools and corporate environments) cannot connect audio or video.
• CPU headroom: Media processing, SFU routing, and recording post-processing all run on the server's CPU. Allowing less than 20% CPU headroom at peak load is a known cause of session degradation and recording failures.
• Browser compatibility: BigBlueButton via WebRTC works on Chrome, Firefox, and Edge. Safari support has improved but still has edge cases. This matters when advising end users and writing your IT support documentation.

For IT teams managing Canvas LTI 1.3 integrations: WebRTC connectivity issues are often misattributed to the LTI configuration itself. If sessions launch correctly (the LTI handshake works) but audio/video fails, the problem is almost always WebRTC routing, TURN configuration, or network firewall rules — not the LTI setup.

Security, Governance, and Recording Retention for BigBlueButton LTI Deployments

Security considerations for a BigBlueButton LTI 1.3 Canvas deployment fall into three areas: transport security, access control, and data governance.

Transport Security

• TLS 1.2 / 1.3 is mandatory. BigBlueButton requires HTTPS on all endpoints — the LTI 1.3 OIDC flow will fail if your BBB server is not behind a valid, trusted SSL certificate.
• LTI 1.3 uses signed JWTs with a configurable key pair. Rotate public/private keys on a defined schedule per your institution's security policy.
• TURN server traffic should also be TLS-wrapped (port 443/TCP) to traverse restrictive firewalls without inspection issues.

Access Control

• LTI roles (Instructor / Learner) control who can start sessions, who can initiate recording, and who can see recording links. Misconfigured role mapping is the most common cause of students accidentally gaining moderator access.
• Recording access can be restricted to enrolled students only via NRPS-based access lists — recommended for any session containing sensitive educational content.
• SAML and OIDC SSO can be layered on top of LTI for institutions requiring federated identity management across multiple LMS instances.

Data Governance and Recording Retention

• Define a recording retention policy before go-live. Recordings stored indefinitely create FERPA and GDPR exposure. Most institutions set a rolling 12–24 month retention window.
• Audit logs for session start/end, recording initiation, and recording access should be enabled and shipped to your SIEM or log management system.
• For data-residency requirements, ensure your BigBlueButton server and recording storage are in the correct geographic region.

See our full terms and data policies at: biggerbluebutton.com/terms-and-conditions

How to Record in BigBlueButton: Step-by-Step Guide and Best Practices

Recording is one of the most valuable features of BigBlueButton for Canvas-integrated courses. Students who miss a live session can review the recording; instructors can build asynchronous libraries of lectures. Here is exactly how recording on BigBlueButton works in a Canvas LTI 1.3 environment.

How to Start a Recording in BigBlueButton

1. Launch the session via Canvas: Open your Canvas course, navigate to the BigBlueButton activity or module link, and click Join. You will be taken directly to the BigBlueButton room (this is the LTI 1.3 launch in action).
2. Verify your moderator role: Only moderators (instructors in Canvas → Instructor role in BBB via LTI) can initiate recording. If you have student role by mistake, recording controls will not appear — check your LTI role mapping.
3. Click the red Record button: In the top toolbar of the BigBlueButton interface, you will see a circular Record button (often labelled "Start Recording"). Click it once to begin. A red dot and the word "Recording" will appear in the header bar to confirm that recording is active.
4. Add a recording to a BigBlueButton conference after it has started: If you forgot to start recording at the beginning, you can enable recording after the conference started — simply click the same Record button at any point during the session. Only the period after you click Record will be captured; earlier content in that session will not be retroactively recorded.
5. Stop or end the recording: Click the Record button again to pause or stop the BigBlueButton recording, or simply end the meeting. When you end the session, BigBlueButton will automatically stop recording and begin post-processing. Note: stopping the recording mid-session and restarting creates separate recording segments.
6. Wait for recording post-processing: BigBlueButton recordings are not instantly available. Post-processing converts raw media into a web-playable format (Podcast, Presentation, Video, or Screenshare format depending on your server configuration). This typically takes 30 minutes to 2 hours for a 1-hour session, depending on server load.
7. Access BigBlueButton recordings: Once processing is complete, the recording will appear in the Recordings tab of the BigBlueButton room in Canvas. Students and instructors can find conference recordings on BigBlueButton by returning to the Canvas course, opening the BigBlueButton activity, and clicking the Recordings tab. Recordings are listed with date, duration, and format.
8. Download recordings from BigBlueButton: Depending on server configuration, a Download option may appear next to each recording. If enabled, this generates a downloadable video file. For compliance reasons, some institutions disable download and only allow streaming playback — confirm your policy before enabling downloads.

Best Practices for BigBlueButton Recording

• Always notify participants that recording is in progress — it is displayed on screen, but verbal confirmation is a best practice and may be legally required in your jurisdiction.
• Keep recording chat logs in mind: BigBlueButton recording can include the public chat by default. Make sure students know that public chat during a recorded session is captured in the recording.
• Use the Presentation format for lecture recordings (slides + audio) to reduce file size and processing time. Use Video format only when webcam video is essential for the recording's pedagogical value.
• Set a disk-space alert on your server — recording files accumulate fast. For managed hosting, confirm your storage allocation and retention policy upfront.

For a full list of recording and conferencing features, see: biggerbluebutton.com/features

Canvas BigBlueButton Recording: How to Share and Sync Recordings in Canvas

When people search for "Canvas BigBlueButton recording," they are typically asking one of three questions: how do students access BigBlueButton recordings inside Canvas; how do instructors share a recording from BigBlueButton to their Canvas course; and how do institutions manage a governed media library of all BigBlueButton recordings. Here are the three main methods.

Method 1: Built-in LTI Recording Tab (Recommended)

When BigBlueButton is integrated via LTI 1.3, recordings are automatically associated with the Canvas course context. After post-processing completes, the recording appears in the Recordings tab of the BigBlueButton activity inside Canvas. Students enrolled in the course can view recordings here — access is controlled by Canvas enrollment, not a public link.

1. In Canvas, open the course and navigate to the BigBlueButton LTI activity.
2. Click the Recordings tab — completed recordings appear here automatically once processing is done.
3. Students can click the recording name to view it in their browser — no download, no separate login.
4. To send a BigBlueButton video recording to Canvas for a different course or student, use the recording link (URL) and paste it into a Canvas Page, Announcement, or Module item as a URL resource.

Method 2: Sharing a Recording Link Manually

If you need to share a recording from BigBlueButton with students who are not in the originating Canvas course, or with external stakeholders:

1. In the BigBlueButton Recordings tab, click the recording you want to share. A unique URL for that recording will be displayed.
2. Copy the URL and post it as a Canvas Announcement, Module external URL, or in a course Page.
3. Note that this URL may be accessible to anyone who has it if your server's recording visibility is set to "public." For restricted access, set recording visibility to "unlisted" or "protected" and use the LTI tab method instead.

Method 3: Governed Media Library via API or External Integration

For institutions with a large volume of recordings, or with strict governance requirements, a governed media library approach is best:

1. Use the BigBlueButton API or a webhook integration to push recording metadata and file locations to a media management system (Kaltura, Panopto, or a custom S3-backed solution).
2. From the media library, generate Canvas-compatible embed codes or LTI deep links for each recording and place them in the appropriate Canvas course.
3. This approach gives you a single inventory of all BigBlueButton recordings across all courses, with centralised retention management, access auditing, and recording sync logging.

Recommended Resources and Internal Links

The following resources from BiggerBlueButton will help you complete your LTI 1.3 Canvas setup, understand your hosting options, and get support from our team:

• Compare managed BigBlueButton hosting plans — find the right capacity for your institution's concurrent session needs, including recording storage.
• Explore BigBlueButton features for LMS integration — recording formats, LTI support, breakout rooms, whiteboard, and more.
• BiggerBluButton documentation and technical guides — LTI 1.3 configuration references, API documentation, and troubleshooting guides for Canvas and Moodle integrations.
• Contact our LMS integration specialists — get help scoping your Canvas LTI 1.3 deployment, recording configuration, or managed hosting migration.
• Review our terms, data policy, and security commitments — relevant for procurement, legal review, and FERPA / GDPR compliance documentation.
• Read more BigBlueButton guides and best practices on our blog — covering recording workflows, Canvas LTI setup, Moodle BigBlueButton integration, SSO, and more.

Frequently Asked Questions: BigBlueButton LTI 1.3 Setup, Recording, and Canvas Integration

Ready to Set Up BigBlueButton LTI 1.3 for Canvas?

Get a managed BigBlueButton environment that is pre-configured for Canvas LTI 1.3, with reliable recording workflows, elastic scaling, and dedicated support — so your IT team focuses on education, not server maintenance.