Building a personalized dashboard page with Docebo Connect/API data

You are SOL. Such a thing does not currently exist. You would need to host somewhere else and use an oauth token to let that server know what data to present back to the learner and iframe it in.

Sorry to deliver the harder news.

There is a KPI widget…but it hasn’t received any love. That would have been the most natural place to extend that learner dashboard.

Good luck with your continued discovery.

In general I agree with ​@dklinger’s verdict, ​@kprim, but depending on what exactly you’re trying to achieve, some of this may be possible in a roundabout way. I wouldn’t call it Docebo-native per se, but it can work in Docebo.

On a high level, the approach would be to make use of existing dynamic widgets (such as “My Courses and Learning Plans”) and then use 

to determine whether to display e.g. certain classes in your custom HTML.

I’ve seen this work in limited contexts and I imagine it can work in others besides, but the execution is not easy, and I’m not sure how strong your HTML and CSS skills are.

* * * * *

Looking at this from a slightly different angle, if you are (or someone reading this is) making use of generative AI to code your custom dashboard, then I’d at least reconsider whether you really need to avoid an external page/application (and why). In my current job, Cybersecurity / IT policies prevent me from spinning up my own web apps, and we don’t have e.g. Lovable for Enterprise, but in my previous job at a smaller company, that probably wouldn’t have been the case.

As ​@dklinger rightly pointed out, you’re hitting the classic Docebo HTML widget wall. Docebo aggressively sanitizes JavaScript in native HTML widgets for security reasons (XSS prevention). And while ​@Ian 's clever CSS :has() trick is a great workaround for manipulating native widgets visually, it won't help you execute the JS needed to fetch and render your Docebo Connect API endpoint.

The official recommendation is indeed what dklinger mentioned: an externally hosted page within an iframe.

However, if your learners are internal employees on managed devices, there is a workaround that completely avoids external hosting.

In organizations I've worked with, when we absolutely needed to avoid external servers but required dynamic API calls, we utilized a SCORM.

The whole application ships as a standard SCORM package, uploaded to Docebo like any other course. There is no external hosting, no server to maintain, and nothing for IT to deploy — Docebo serves it to the learner's browser from within its own player.

Once it loads, it does three things:

1. Identity from the live session. The package reads the logged-in user straight from the SCORM runtime that Docebo exposes (cmi.core.student_id). No login, no user mapping, no second set of credentials — whoever opened the course is who the app renders for. One note from the field: Docebo returns the username there, not the numeric ID, so the middleware resolves it to the internal id_user via the Docebo API before touching any data.
2. Custom UI instead of the HTML-widget sandbox. Because the package owns its own window, we render full HTML/CSS/JS — cards, matrices, tabs, progress bars, approval queues — with none of the restrictions of a Docebo HTML widget.
3. A secure call to our own API. The JavaScript calls an authenticated Workato API endpoint (token in the request header) that reads and writes the skills data tables and talks back to Docebo. All traffic is the learner's browser → our endpoint; nothing is proxied through a third-party host.

Hope this is usefull.

That’s a very nice trick ​@Moshe.Machlav! :D

​@Moshe.Machlav that is probably one of the coolest approaches I have seen in a bit.

Very cool approach indeed.

​@Moshe.Machlav great idea. Were you able to come up with a way to present this info to the user without it feeling like they were accessing a course? I’m imagining it being confusing for the user why they’re seeing their dashboard statistics by taking a course 

Hey ​@ntosto  great question.

Since it's a SCORM, it will always open inside the Docebo player environment. To make it feel less like a traditional course, we usually hide the player navigation (Full Screen mode) and design the internal SCORM UI to look exactly like a modern web dashboard.

It’s definitely a workaround and requires some UI compromises, but it solves the security and external-hosting barriers. If you end up trying it and find ways to optimize the player experience further, definitely share it back here with the community!