Connecting Moodle to Dasmeet, step by step

If Moodle already has the BigBlueButton activity, there is nothing new to install. Changing the server URL and shared secret is enough to bring your branding and recordings along.

Dasmeet Ekibi — Product and content 2 min read TürkçeDeutsch
A ribbon joining two systems; green dots at the junction

Moodle is one of the few LMSs that supports BigBlueButton in core: the BigBlueButtonBN activity module has been built in since 4.0. Because Dasmeet is fully compatible with the BigBlueButton API, connecting Moodle means changing exactly two fields.

First: get your API details

In the Dasmeet panel, open Integrations. You will see two values for your organisation:

  • Server URL — a BigBlueButton endpoint dedicated to your organisation.
  • Shared secret — the secret that signs API calls. Do not share it; if you suspect it has leaked, rotate it from the panel.

Change the setting in Moodle

  1. Sign in to Moodle as an administrator.
  2. Go to Site administration → Plugins → Activity modules → BigBlueButton.
  3. Enter the Dasmeet server URL in BigBlueButton Server URL.
  4. Enter the shared secret in BigBlueButton Shared Secret.
  5. Save. The connection status notice at the top of the page should turn green.

That is all. Every existing BigBlueButton activity runs through Dasmeet from the next launch.

Branding and defaults

Meetings launched from Moodle also receive the logo, colours and default settings you defined in the panel. Nothing extra is needed on the Moodle side; Dasmeet adds these settings while handling the create call.

Recordings

After a session ends, the Recordings table on the Moodle activity page fills in. The MP4 format appears as a column; participants can download it directly. Deleting a recording is also done from Moodle and is reflected on the Dasmeet side.

Two common situations

"Could not connect" notice: usually a leading or trailing space in the secret. Clear the field and paste again.

An old meeting is still on the old server: the setting change only affects newly created sessions. If a session is open, wait for it to end.

Back to the blog