Docebo Connect 11 changelog: SAML cutover and review cadence

For a Spanish SME running Docebo as the LMS — typically with 50-200 learners, an HRIS pushing employee records nightly, and a small L&D team that does not have engineering bandwidth to investigate breaking changes the morning they surface — the Docebo Connect changelog is one of the artifacts the integration owner should put on a calendar. Not because the changelog is interesting reading. Because the changelog is the document that turns “our SSO broke this morning and we don’t know why” into “we knew about this in May, scheduled the migration for August, and tested it in sandbox in July.” The April 2026 changelog edition is a useful working example because it carries one item — the new Docebo for SAML rollout — that every Docebo customer using SAML-based SSO needs to act on before October 28, 2026.

What the changelog tracks — and why the discipline matters

The Docebo Connect changelog is the integration team’s record of what has changed in the connectors, the recipes, and the platform-level integration capabilities since the last review. The entries fall into three categories the SME’s integration owner should learn to read at a glance. Breaking changes are the items that require action — a connector deprecation, an authentication-method change, a webhook payload alteration — because the integration will stop working on a known date if the SME does nothing. Migration paths are the documentation Docebo publishes for breaking changes, describing the steps to move from the old behaviour to the new one and the window in which both work. Connector and recipe improvements are the non-breaking enhancements — new fields, new triggers, new error-handling — that the SME can opt into without operational pressure.

The discipline that converts the changelog from a static document into an operational artifact is a five-step review the integration owner runs on a known cadence, typically monthly. Search for the SME’s integrations — the changelog covers the full Docebo Connect catalogue but most SMEs use 3-6 connectors (HRIS, calendar, identity provider, content authoring, credentialing, communications). Filter to those. Review dates since the last review — the changelog is chronological, so the integration owner can scan from the previous review date forward. Identify impact — does the change require action in the SME’s environment, and by when. Plan updates — schedule the work into a maintenance window rather than reacting to a production failure. Test in sandbox — every Docebo tenant has a sandbox environment, and every changelog-driven change should pass through it before production.

For a Spanish SME under INCIBE supply-chain expectations on documented integration governance, the monthly changelog review is the documentation surface that proves the SME knows what is changing in its third-party software boundary. The cost of the discipline is one hour per month. The cost of skipping it is one production incident per year and a finding in the next quarterly review.

The April 2026 SAML rollout — anatomy of a staged migration

The April 2026 changelog’s headline item is the new Docebo for SAML rollout, which replaces the legacy SAML implementation across the platform. The staged plan is the example every SME’s integration owner should study, because it is the shape Docebo uses for any high-impact platform-level change.

The shape that matters is the cancelled-then-replaced middle row. Docebo originally planned three forced-wave migrations across April, May, and June, with each customer assigned to a wave based on their identity provider (Okta, Microsoft Entra ID, custom). Forced waves are the migration approach where the vendor picks the date and the customer adapts. The cancellation and replacement with Launch Pad opt-in from July 22 is the more customer-friendly approach: each SME activates the new SAML on its own schedule between July 22 and October 28, runs the new and legacy SAML in parallel during the activation window, and confirms the new flow works before the hard cutoff.

For the SME’s integration owner, the operational implications are concrete. Between April and July, no action is required — the changelog entry is informational. From July 22, the integration owner should activate the new SAML in the sandbox tenant, run the SSO flow with the SME’s identity provider, and confirm it works. From August (sandbox confirmed) through September, the integration owner activates the new SAML in production during a maintenance window, runs both flows in parallel for 1-2 weeks, and confirms no SSO failures in the production logs. By early October, the legacy flow is disabled in the SME’s identity provider. October 28 arrives as a non-event because the migration is already complete. The Spanish SME under EU AI Act Article 13 transparency expectations on AI-augmented workflows touching authentication can document each of those steps as evidence of controlled change.

Building the changelog review into the SME’s monthly rhythm

The integration owner’s review cadence should be small, regular, and documented. The pattern that works for an SME with a single integration owner and 3-6 active connectors is a 60-minute monthly review on a fixed calendar slot — typically the first Tuesday of the month, before the daily grind crowds the calendar. The review’s output is a one-page note in the SME’s documentation system covering: which integrations were checked, which changelog entries are relevant, which require action, the planned action date for each, and any items that have moved from “planned” to “completed” since the last review.

For a Spanish SME accessing Kit Digital IA/BI vouchers — Segment III (10-50 employees) up to €12,000, Segment II (3-9 employees) up to €6,000 — the documented monthly review is the deliverable that converts “we deployed integrations” into “we maintain them with documented change governance.” The Agente Digitalizador can install the integrations, ship the review template, and hand the L&D lead a process the team can run without external help past month three. The official changelog itself lives at help.docebo.com, and the broader product context at docebo.com.

Ready to get started?

Working on this yourself? J4SGON S.L. delivers Docebo Connect, HRIS, SSO and migration work for European organisations — see what a scoped engagement covers or describe your project and we will reply with a written scope.