Thank you to everyone who attended our DU Live on June 25. If you missed it, you can catch it here on demand.
We received many questions during the live event that we weren’t able to answer, so we’ve placed them below for you to reference.
| Question | Answer |
|---|---|
| Is each instance of a Companion extension tied to a singular Docebo log-in? Or is there a way to have a more generalized user that multiple users could install the extension on their browser? | Currently, Docebo Companion is tied to a singular instance so if you want to switch platforms, you must log out and log back in with a different URL. Typically, switching platforms is not needed at a learer level so it wasn't prioritized at this point. In the long-term, we are investigating into how one can easily switch between platforms. |
| One question we get all the time from our employees is "do you have a course on XYX topic?" Then our team points them to the relevant courses. We have internal employees and external customers using Docebo to train on our software tool. How can we drive customers to install Companion? Their IT teams will probably be very strict about what they can install. | For now, yes, the content is shown regardless of status. We initially considered adding a learner preference setting so users could choose whether completed content should still be displayed, but we decided not to include that in the initial release. We’d be interested in your feedback on this and in understanding how much of a friction point it is for your team. |
| Once the browser extension is set up, how do people install it on their browsers, and how do we ensure that only our team members and selected customers can get it? | There are a few ways to support adoption.
|
| Can you restrict Companion to branches or groups? | Not currently, but in August we’re planning to release the ability to limit spaces to specific branches or user groups. |
| We use SSO through Okta, if someone is not signed on through Okta, would Companion be able to work if they are not connected to Docebo? | No, if a user is not authenticated into Docebo, they would not be able to use Companion. Users must be registered in Docebo and sign in through the authentication flow configured for your platform, whether that is Okta SSO or another supported method. Companion follows your existing platform authentication setup rather than introducing a separate login flow. If helpful, we’d be happy to talk through your specific setup in more detail. |
| Many of our courses, especially compliance related courses are location/role specific. Does it tailor the information fed to the user based on their profile? | For search and Harmony functionality, yes, results can be tailored based on the learner’s profile. For the content shown in spaces, not currently. That said, learner visibility is always respected, so users will only see content they already have access to within the platform. To improve this further, we’re planning an August release that will allow learning spaces to be assigned at the group or branch level. |
| Is there any change in security or information that needs to be shared with IT related to companion for enablement? I'm worried they will not be onboard based on security reasons. | We have a security & IT overview document available on our Trust Center that you can share with your IT team to help facilitate this discussion. |
| Can Docebo Companion display all courses and learning plans currently assigned or enrolled to a user, similar to the My Courses and Learning Plans page? | No, this was a deliberate design decision. We wanted the content surfaced in Companion to remain as relevant as possible to the specific space and workflow the user is in, rather than replicating the full My Courses and Learning Plans experience. That said, we are considering a default or home space that could surface high-priority items such as expiring certifications, upcoming course deadlines, and potentially standard My Courses and Learning Plans content. The goal would be to ensure users still see something useful even when they are not in a space with contextual recommendations. We’d welcome your feedback on whether that would be valuable for your use case. |
| Does this also work in Edge? | Yes it does, you can use the same chrome store link in Edge. |
| Is Companion configurable to be published only to specific users? | Not currently, but we’re planning an August release that will allow spaces to be limited to specific branches or user groups. |
| Does all content need to be on our Docebo platform? HR Handbook, etc? | Currently, yes, content needs to live in Docebo in order to be surfaced through Companion. Our upcoming Enterprise Knowledge functionality is expected to allow Companion to reference connected external sources outside the platform, such as SharePoint or Google Drive. |
| Are the resources secured to just your environment or are they used to gain global research data? | Yes, everything remains fully secured within your own environment. |
| Have you heard of any privacy concerns within a healthcare context? In other words, how is Companion referencing the page if there is PHI? | Currently, Companion reads only the page URL and does not read page-level content, so it does not access PHI or other sensitive information from the page itself. This is by design, with privacy and security in mind. When we introduce optional page-level reading capabilities in the future, any sensitive information would be redacted or removed, and no data would be stored, with zero-day retention. |
| I noticed Companion url is appearing under the User Profile where they add their avatar. Can this be hidden so we don't receive questions on the purpose? | We’ve already developed this, and it is expected to be included in the July release as a Companion configuration setting that allows the learner profile section to be hidden. |
| Does Companion collect any data from the actual page, or just the URL component (our IT will ask from a data security standpoint)? | Currently, Companion reads only the page URL and does not access page-level content. It was designed with security and privacy in mind. We also have Trust Center documentation that explains how Companion works and what data it collects. When we introduce optional page-level reading capabilities in the future, any PII would be redacted or removed, and no data would be stored, with zero-day retention. |
| Any plans to make this available for Safari? | Not currently. At this time, our is on supporting the major Chromium based browsers. |
| is companion now available on Microsoft Edge because i was not able to find it? | Yes, Companion is available on Microsoft Edge. You can access it using the same Chrome Web Store link in Edge. |
