Services

Technical work on Docebo, defined by its scope. Every engagement starts from a written proposal stating what is included, what is out of scope, and the exit criterion of each phase — the proposal template is published.

Docebo Connect & Workato integrations

Recipes that keep running after we leave: designed around the five-step skeleton every Docebo Connect recipe shares, tested with fixtures, and documented for the person who inherits them.

What is in scope

  • Recipe design and build — User Sync, Calendar Sync, Badge Issuance, Content Sync and the custom flows in between
  • Connector and connection inventory: off-the-shelf vs community connectors, OAuth scoping, credential register
  • Data Tables vs Lookup Tables — failed-record queues, deduplication trackers, audit trails
  • Test cases and fixtures for every recipe before it touches production
  • Workato On-Premise Agent for hybrid (on-prem + cloud) integration
  • Event Streams and webhooks where polling is the wrong tool
  • Enablement Labs clone-out discipline and a monthly changelog review cadence

HRIS synchronisation

Employee data flowing from the HR system into Docebo — joiners, movers and leavers — with the field mapping written down and the sync direction chosen on purpose.

What is in scope

  • Workday (RaaS reports), SAP SuccessFactors, ADP Workforce Now, BambooHR, HiBob, Ceridian Dayforce
  • Joiner–mover–leaver provisioning: branches, groups, managers, deactivation
  • Field-mapping specification per system, including custom fields and external IDs
  • Sync direction and cadence: scheduled vs event-driven, and what breaks in each
  • Monthly reconciliation runbook and GDPR-aligned anonymisation of leavers

Identity & SSO

SAML 2.0 that survives the next certificate rotation and the next platform security change.

What is in scope

  • SAML 2.0 with Okta and Microsoft Entra ID (Azure AD); OIDC where it fits
  • Attribute mapping, just-in-time provisioning, single logout
  • External IDs connector: one identity across HRIS, IdP and LMS
  • Migration runbook for the 2026 security-standards cutover, tested in sandbox first
  • Certificate and metadata lifecycle documented so it does not expire on demo day

Migration & deployment

Bulk loads and platform cutovers run through our own Docebo migration engine — 45 operations, each validated locally before a single row is written to the tenant.

What is in scope

  • Users, branches, groups, power users and profiles
  • Courses, catalogs, categories, learning plans, ILT sessions, training materials and SCORM
  • Enrollments (create, update, archive), certifications and completions
  • Two-phase model: check produces an errors file with zero tenant writes; execute pushes only the rows that passed
  • CSV templates and a field-mapping engine so your export becomes the import
  • Cutover plan, rollback points and a post-go-live reconciliation

What you get in every case

How we work

Six phases, each with a written exit criterion. The proposal, project plan, RACI and SLA we use are published as templates, so you can read the deliverables before you ask for a quote.

  1. 1

    Discovery

    Audit of the current platform, the systems it must talk to and the data in them. Stakeholders mapped, KPI baseline agreed.

    Exit: Signed discovery report

  2. 2

    Design

    Integration architecture, field mappings, identity flow and the migration inventory — written down before anything is built.

    Exit: Approved technical design document

  3. 3

    Build

    Recipes, connectors, SSO configuration and migration runs in sandbox, delivered in sprints you can see.

    Exit: Working integration demonstrated on your tenant

  4. 4

    Test

    Test cases per recipe, migration check-phase reports, user acceptance with your admins.

    Exit: UAT signed off, no open P1 issues

  5. 5

    Deploy

    Production cutover with rollback points, admin training, and a runbook your team can operate without us.

    Exit: Live, with your IT team able to run it independently

  6. 6

    Evolve

    Optional ongoing support under an SLA, quarterly reviews, and changes as your HRIS or IdP changes.

    Exit: Quarterly business review

Before kickoff: NDA and data-access agreement · Systems inventory and credentials handover · Named stakeholders on both sides · Kickoff with agreed success metrics.

Tell us what you are integrating or migrating

Send the platform, the systems involved and where you are stuck. You get a written scope back — phases, deliverables and what is out of scope — before anything is billed.

Describe your project What an engagement covers