What the connector does
Once connected, Dendreo and DGTLMS work together with no double entry:
- From Dendreo to DGTLMS — every session created in Dendreo becomes a DGTLMS session linked to the chosen course; every participant gets an account; every enrolment enrols them in their session. Changes and cancellations follow.
- From DGTLMS to Dendreo — each participant's progress (completion, score, time spent, dates) is sent back to Dendreo as it happens.
- One-click sign-in — from the Dendreo extranet, the participant opens their course in DGTLMS without typing a password.
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
Open the dashboard
Administration → Integrations & connectors, Dendreo card.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).
Advanced options
optional: only fill them in for the cases described below.
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.
Pause if needed
the switch on the card suspends exchanges without erasing the configuration.
Fields to fill in
- Tenant ID (mandatory) — the identifier of your Dendreo space.
- JWT Secret (mandatory) — the shared secret that signs one-click sign-in.
- Webhook Secret (mandatory) — the secret that signs exchanges in both directions.
- Webhook URL — the Dendreo address that receives progress. Leave it empty for Dendreo's standard address.
- Return URL — the address back to Dendreo after one-click sign-in.
- Site ID — fill it in if your platform has several sites and Dendreo should only see the courses of one of them.
- Allowed Hosts — only fill it in if Dendreo gives you a receiving address other than
hooks.dendreo.com(a test environment, for example).
What to send to Dendreo
Send Dendreo the following (or enter it in Dendreo's LMS connector settings):
- The DGTLMS API address:
https://<your-platform>/api/dendreo— for examplehttps://training.my-organisation.com/api/dendreo. - The one-click sign-in address:
https://<your-platform>/api/dendreo/auth/jwt. - The DGTLMS API key and your Tenant ID: Dendreo uses them to read your course list.
- Both secrets (JWT and webhooks): they are the same values on both sides. If one changes at Dendreo, update it in DGTLMS straight away, and vice versa.
Check the connection
The API responds
open
https://<your-platform>/api/dendreo/healthin a browser: you should read"status": "ok"and"database": "connected".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.
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.
One-click sign-in
from the Dendreo extranet, open the course as the test participant: they should land directly in DGTLMS.
Progress
complete an activity as this participant: their progress should appear in Dendreo.
How data is matched
- Courses — Dendreo shows your DGTLMS catalogue in two groups: « [Parcours] », your courses, and « [Session] », your existing DGTLMS sessions. Choose a course so that DGTLMS creates a session from each Dendreo session, or an existing session to enrol participants in it directly.
- Participants — a participant whose e-mail (or login) matches a DGTLMS learner account is linked to that account; otherwise a learner account is created. An instructor or administrator account is never linked: the person gets a separate learner account.
- Sessions and enrolments — found by their Dendreo identifier: a change or a cancellation in Dendreo updates the same item, with no duplicate.
- Progress — sent at every step forward. If Dendreo does not respond, DGTLMS retries automatically, at increasingly spaced intervals, until Dendreo confirms receipt.
- 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.