DGTLMS & LMSDISPATCHER Guide

Administration

Set up the Dendreo connector

Connect DGTLMS to your Dendreo management software — sessions, participants and enrolments arrive on their own, progress goes back to Dendreo, and participants open their courses in one click from the extranet.

Administrator · Integrator~10 minutesAdvanced

What the connector does

Once connected, Dendreo and DGTLMS work together with no double entry:

Dendreo is the one that calls DGTLMS: there is no synchronisation to start and no mapping to maintain in DGTLMS.

  • A DGTLMS account with the right to configure connectors.
  • On the Dendreo side: your Tenant ID, the JWT secret (one-click sign-in) and the webhook secret. Dendreo provides them, or generates them with you when the LMS connector is activated.
  • On the DGTLMS side: your platform's API key. It is set by your hosting provider in the server configuration; ask DGT Concept for it.
  • The courses used in Dendreo must be published (Active status): a session created on a draft course, or one awaiting re-approval, is refused.

Steps in DGTLMS

  1. Open the dashboard

    Administration → Integrations & connectors, Dendreo card.

  2. Enter the connection details

    « Renseigner les informations de connexion à Dendreo » button (enter the Dendreo connection details): fill in the three mandatory fields (see Fields to fill in below).

  3. Advanced options

    optional: only fill them in for the cases described below.

  4. Save and activate

    « Enregistrer et activer ». The configuration is saved on the server and the connector becomes active. Secrets are never displayed again: leave a secret field empty to keep its current value.

  5. Pause if needed

    the switch on the card suspends exchanges without erasing the configuration.

Fields to fill in

What to send to Dendreo

Send Dendreo the following (or enter it in Dendreo's LMS connector settings):

Check the connection

  1. The API responds

    open https://<your-platform>/api/dendreo/health in a browser: you should read "status": "ok" and "database": "connected".

  2. Dendreo sees your catalogue

    in Dendreo, the list of DGTLMS courses should appear. If it is empty, check the API key, the Tenant ID and, if you filled it in, the Site ID.

  3. A test session

    in Dendreo, create a session on a published course, with a test participant. In DGTLMS, the session appears and the Dendreo card counts one more user and one more enrolment.

  4. One-click sign-in

    from the Dendreo extranet, open the course as the test participant: they should land directly in DGTLMS.

  5. Progress

    complete an activity as this participant: their progress should appear in Dendreo.

How data is matched

  • Unpublished course — it appears in Dendreo's list, but creating the session is refused: publish the course, then resend or recreate the session from Dendreo.
  • Secret changed on one side only — exchanges are refused (authentication error) until both values match.
  • One-click sign-in is for learners only — it never opens an instructor or administrator account. An instructor enrolled as a participant in Dendreo gets a separate learner account, with the login dendreo_<Dendreo identifier> if their e-mail is already used as a login.
  • The connector handles enrolments and progress, not attendance: attendance is handled by other tools (e.g. Edusign).
  • A resend carries the current state of the enrolment's progress: it is not added to the previous one.
  • The Dendreo card on the dashboard shows the number of users and enrolments received from Dendreo: it is the simplest way to see that exchanges are going through.

See also