Integrations

Moodle (mod_llp)

The open-source plugin mod_llp embeds lern.link content as an activity in Moodle. The Moodle admin installs it once (Site administration → Plugins → Install plugins → upload ZIP) and enters your organisation's API URL and API key. After that, trainers create activities and upload PPTX directly. Platform improvements reach you without a plugin update; the plugin is compatible with Moodle 4.5, 5.2 and 5.3 (playback → "Player & LMS").

WordPress (wp_llp)

The wp_llp plugin embeds content via the shortcode [llp …] or as a Gutenberg block. By default it shows the simple player variant; via an attribute you switch to the standard player (→ "Player & LMS").

API keys

Plugins and your own applications access the portal API via API keys (format llp-...). You create and revoke keys in Administration; treat them like passwords (→ "Administration").

Translation engine

Per organisation you define which translation engine is used. The default is the portal's EU-hosted AI translation; optionally you connect DeepL with your own API key (own contract, own brand or compliance requirement). Both engines translate the content into additional language versions (→ "Editing & AI").

AI providers (your own credentials)

The AI services in use (language models, speech output) are configured as providers and are interchangeable. If needed, you store your own credentials for a provider ("bring your own"). All providers have their legal domicile in the EU — details on the "Privacy & AI" page.

Payment providers

For purchasing credits you connect a payment provider (e.g. Mollie) to your organisation. The provider handles payment processing only (→ "Credits & billing").

E-mail delivery (SMTP)

In the mail area you store the credentials of your mail server (SMTP) so the portal can send notifications. Verify delivery with a test message.

Further connections such as LTI 1.3 (Canvas, Blackboard and others) and a content marketplace are planned.