Introduction
365Talents is a skills intelligence platform. The native integration between the Docebo platform and 365Talents lets matched users open the 365Talents experiences available to their role and to your organization's purchased package from within the Docebo platform, without a second sign-in. Learners can manage their skills profile and explore relevant training. When a learner opens a recommended Docebo course, the course page replaces the embedded view in the same browser tab. Managers, HR users and administrators can access the 365Talents views available to them.
The two products remain separate systems presented together. The Docebo platform stays the system of record for courses, enrollments and completions. 365Talents becomes the system of record for skills.
It helps to keep two things apart when you plan the integration. The integration itself does four things: it adds entry points to 365Talents inside the Docebo platform, it signs matched users in to 365Talents, it sends a defined set of learning data from the Docebo platform to 365Talents and it embeds the 365Talents views in Docebo pages. What appears inside those views is 365Talents functionality, and it depends on the 365Talents package your organization has purchased, on how 365Talents is configured and on each user's 365Talents rights. Capabilities such as Find an expert, job and gig opportunities and career development can be available in the embedded experience, but they are not separate data flows from the Docebo platform, and not every organization sees them.
To see what learners and managers get in practice, read Using 365Talents in your platform (opens in a new tab).
Please note: Superadmins do not activate the integration. Docebo activates it for your platform as part of your subscription to 365Talents. Once it is active, a Superadmin completes the setup. Learn more about activating and configuring the 365Talents integration.
Before you start
The integration links user records that already exist in both systems. It does not create users in 365Talents, and it does not update user data in 365Talents. Three conditions need to be met before it can work.
First, your organization needs an external system, typically a human resources information system (HRIS) or an identity provider, that provisions users independently into both the Docebo platform and 365Talents. These are two separate provisioning connections reading from the same source system, not one connection feeding the other. If you have no way to provision users into 365Talents, the integration cannot function.
Second, each user's email address must be identical in both systems. The email address is the only identifier used to match a Docebo user to a 365Talents user, and it cannot be changed to a different field. The comparison is not case-sensitive.
Third, if managers are going to use the team skills experience, the manager hierarchy in 365Talents needs to match the manager hierarchy in the Docebo platform. The integration does not synchronize, create or modify manager relationships in either direction.
A matching email address is necessary, but it is not enough on its own. The user must also already exist in 365Talents, because the integration does not create or update users in either platform. A user who exists in only one of the two systems is not matched.
Roles and default language also need to be aligned upstream, because the integration synchronizes neither of them. Docebo has no HR role, so decide with your Docebo representative which Docebo role each 365Talents HR population should hold: a Power User with an appropriate profile, a Superadmin or a learner who reaches the HR pages through a menu assigned to their group. Set the same default language for each user in both systems when they are provisioned.
Please note:
- If your HRIS or identity provider becomes the provisioning source for the Docebo platform as part of this project, it can overwrite manager relationships already recorded in the Docebo platform. Plan for this before you connect it.
- Make sure that each email address belongs to only one active user in the Docebo platform. Several Docebo users sharing the same email address can prevent the integration from matching them correctly.
Best practice: Before activation, organize the courses you want to power skills recommendations into catalogs that represent a meaningful recommendation scope, for example a catalog of leadership courses for managers or a catalog dedicated to one role's development. A single catalog holding hundreds of unrelated courses does not produce useful recommendations, and basic mandatory compliance courses add little value to skills-based recommendations. Give catalogs clear titles, because the catalog title is carried into 365Talents and used as a label there. Write clear course titles and descriptions too: 365Talents assigns skills to each course from its title and description, so a course with a generic or missing description receives weaker skill tags.
Which organizations the standard setup applies to
The standard setup applies to an organization that is new to both products, and to an organization that already uses the Docebo platform and is adding 365Talents. If your organization already has a Docebo platform and a 365Talents tenant that were created as a linked pair, Docebo can activate the integration on them later, without recreating either.
If your organization already uses 365Talents on its own, with its own HRIS, single sign-on or other connections, adding the Docebo platform is not part of the standard setup, because 365Talents keeps a single identifier per user that other connections may already use. If your organization uses an earlier custom integration between the two products, the standard setup does not apply either. In both cases, contact your Docebo representative so that the case can be assessed before any date is set.
How users are matched between the two systems
User matching starts automatically when Docebo activates the integration and continues as users are provisioned in both systems. It links active Docebo users to existing 365Talents users by email address, without regard to upper or lower case. A Superadmin reviews the matched user count in the integration configuration page. For an intended user who remains unmatched, correct the missing record or email address in your organization's provisioning source, then verify that matching recovers.
Only active Docebo users take part in the matching. Deactivated and archived users are excluded.
Users who cannot be matched, because they do not exist in one system or their email address differs, are not matched. An unmatched user is excluded from every data flow until the match is made, and cannot open the embedded 365Talents views.
Not every Docebo user needs to be matched. Compare the matched user count against the population you intend to use 365Talents, not against every user in your platform. For example, external audiences such as customers or partners who exist only in the Docebo platform stay unmatched unless they are also provisioned automatically into 365Talents.
Please note: A user who exists in the Docebo platform but has no matching 365Talents record cannot see any 365Talents content, and cannot resolve this themselves. To fix it, correct the user's record or email address in your provisioning source so that the user exists in 365Talents with the same email address, then check the matched user count on the integration configuration page. Do not resolve mismatches by editing users by hand in either platform.
Once a user is matched, later edits to that user's fields in either system do not break the match.
Signing in
Users never sign in to 365Talents separately, and no separate single sign-on configuration is needed for the embedded pages. When a matched user who is already signed in to the Docebo platform opens an embedded 365Talents view, the platform signs that user in to 365Talents in the background with their Docebo session. There is no second sign-in screen, and users are not asked to accept 365Talents terms and conditions.
What is synchronized
Learning data flows in one direction, from the Docebo platform to 365Talents. Users are not synchronized: they are provisioned independently in each system and then linked by the matching described above. No 365Talents skill, skill tag or skills taxonomy is written into the Docebo platform.
| Data | What happens | When |
|---|---|---|
| Users | Existing users are matched by email address. No user is created and no user field is synchronized | Automatically from activation, and continuously as users are provisioned in both systems |
| Courses | Published courses in the catalogs a Superadmin selects are sent: title, description, type, language, status, a link back to the course and the address of the course thumbnail. A course is sent only if its language is active in your 365Talents tenant | When a Superadmin runs the catalog synchronization, then automatically as courses in those catalogs are created, updated or removed |
| Catalog access | Which selected catalogs each matched user can access, derived from the user, group and branch assignments on each catalog | With the catalog and user synchronizations |
| Course completions | Completions by matched learners of courses that belong to the selected catalogs | Automatically, as they happen, once the first catalog synchronization has completed |
| Historical completions | Optional: either no history, or the completions of the previous 12 months for all matched users | Once only, when a Superadmin runs the import. It does not have to run at setup |
| Certifications | All unexpired certifications awarded in the Docebo platform, regardless of the catalog selection, with their end date. The end date is displayed on the learner profile in 365Talents, and nothing happens automatically when a certification expires | Automatically from activation. There is no setting to switch it on or off |
When 365Talents receives a course, it assigns skills to that course from the 365Talents skills taxonomy, using the course title and description. Those skill tags stay in 365Talents. Skills already tagged on a course in the Docebo platform, including courses from third-party providers such as LinkedIn Learning or Go1 in the content marketplace, are not carried over, and 365Talents tags those courses again.
When a course belongs to more than one selected catalog, it is sent to 365Talents once and is associated with each of those catalogs.
When 365Talents receives a course completion, it creates a suggestion asking the learner to update a related skill on their profile. The learner accepts or dismisses it. A completion never updates a skill automatically. Certifications arrive in 365Talents as independent records in the learner's professional training profile, not attached to a synchronized course.
Which courses a learner is recommended
365Talents recommends integration-synchronized courses only from the selected catalogs that a learner can access in the Docebo platform. Catalog access is derived from the user, group and branch assignments already configured on each catalog. The audience of these courses is defined only in the Docebo platform: the integration creates the corresponding catalog audiences in 365Talents for you.
This means that any attribute you want to use to target recommendations, for example a business line, a country or a job family, must exist in the Docebo platform as a branch, a group or a user field that drives an automatic group, and the catalog must be assigned to it. An attribute that exists only in the data your HRIS sends to 365Talents does not control who is recommended these courses.
Visibility is applied at catalog level, not at course level. If a course inside a catalog is restricted for a particular learner by some other mechanism, that restriction is not reproduced in 365Talents.
Please note: Because visibility is applied per catalog and not per course, a learner may occasionally be recommended a course they cannot enroll in. If they open it, they see the platform's standard access error. Review your catalog assignments before activation so that the audience of each catalog matches the audience you want to receive its recommendations.
Best practice: Assign catalogs to groups and branches that already reflect the populations you want to reach, rather than to long lists of individual users. Many individual catalog assignments are harder to maintain and add load on the 365Talents side.
Impact on the platform's native skill management
When the integration is active, 365Talents becomes the only skills engine for your platform, and the Docebo platform's native skill management features are deactivated. This is similar to integrating skills with any other external talent management platform or HRIS, except that here the connection is native rather than built through the API, and the set of features turned off is wider. The following are turned off.
| Audience | Feature turned off |
|---|---|
| Learners | Guided skill selection |
| Learners | Skills self-evaluation |
| Learners | The My skills section of My profile |
| Learners | The Skills dashboard |
| Learners | AI skill suggestions |
| Learners | Skill targets and self-service target levels |
| Managers | The Skills overview in My team, including the team skills dashboards and the skills overview page of each team member |
| Managers | Suggesting skills, skill levels and skill-related content to team members, and the related learner notifications |
| Superadmins | Resetting user skills |
| Superadmins and integrations | Setting a target expertise level through the API |
Calls to the Docebo API that attempt to set a target expertise level return an error stating that skills are managed by 365Talents. In My team, the native Skills overview is replaced by the embedded 365Talents team experience.
Some features remain available but do not receive 365Talents skills data: AI-based channels, skill tagging on content and skill-based search. They cannot use the 365Talents skills profile, so their results may be incomplete or irrelevant. Any Docebo skill data they use must be managed separately in the Docebo platform.
Best practice: Avoid using AI-based channels, skill tagging on content and skill-based search while the integration is active. Standard, manually curated channels are not affected, and neither is gamification: points and badges do not depend on skills data.
The Docebo platform's own content recommendation engine is not affected and continues to suggest courses using its own logic. This means learners can receive recommendations from two sources, the Docebo platform and 365Talents.
Please note: There is no automatic migration of existing skills data from the Docebo platform's native skill management into 365Talents. If your platform already uses native skill management, agree a transition plan with your Docebo representative before the integration is activated, including whether to rebuild your skills model in 365Talents. Configuration work already done on the Docebo skills catalog does not transfer to 365Talents.
Limitations
The tables below list the limitations of the integration in its current version, so that you can plan around them.
Users and identity
| Limitation | Detail |
|---|---|
| Users are not created by the integration | Both systems are provisioned independently from your own HRIS or identity provider. The integration only matches records that already exist in both. If a user is created by hand in one platform, create the matching record in the other platform too |
| Email is the only matching identifier | Matching uses the email address and cannot be configured to use a different field |
| Deactivated and archived users are excluded | Only active Docebo users take part in matching |
| Unmatched users are blocked | A user with no matching 365Talents record cannot open any embedded 365Talents view, is excluded from all data flows and cannot resolve this themselves |
| No alert for unmatched users | The configuration page shows only the matched user count, not a count of unmatched users. The platform does not warn you separately when the populations of the two systems differ |
| Manager hierarchies are not synchronized | The integration never creates or changes a reporting line in either system. Where the two hierarchies diverge, the embedded views use the 365Talents hierarchy. This affects learners as well as managers, because manager feedback and skill validation follow that hierarchy |
| Roles are not synchronized | There is no automatic mapping between Docebo roles and 365Talents rights profiles, and changes to a user's rights profile are not synchronized. A Power User is not automatically a 365Talents manager |
| Interface language is not synchronized | If a user changes their interface language in one system, the change does not reach the other. Set the same default language for each user in both systems when they are provisioned, and agree a fallback language where 365Talents does not support a Docebo language |
| Page access is not synchronized | Making a 365Talents page visible to someone in the Docebo platform does not grant them rights in 365Talents. Align your menu audiences with the rights configured on the 365Talents side |
Courses, catalogs and recommendations
| Limitation | Detail |
|---|---|
| Only selected catalogs are synchronized | Courses outside the catalogs a Superadmin selects are never sent to 365Talents and are never recommended by 365Talents |
| Unpublished courses are excluded | Draft and unpublished courses inside a selected catalog are not sent |
| Course language must be active in 365Talents | A course is sent only if its language is active in your 365Talents tenant |
| Visibility is applied per catalog, not per course | A learner may be recommended a course they cannot enroll in, and receives the standard access error if they open it |
| Recommendation audiences are defined in Docebo only | Any attribute used to target recommendations must exist in the Docebo platform as a branch, a group or a user field that drives an automatic group |
| Skill tags are not written back | The skills 365Talents assigns to your courses stay in 365Talents. Skills already tagged on courses in the Docebo platform are not sent |
| Catalog titles have limited visibility in 365Talents | Because of how catalogs are represented there, catalog titles do not appear on most 365Talents pages seen by learners |
| Catalog settings are not individually configurable | All synchronized catalogs share the same configuration on the 365Talents side |
| Changing configuration during a synchronization | Changing your catalog selection while a synchronization is running can produce inconsistent results. Run a second synchronization afterwards to correct it |
Completions and certifications
| Limitation | Detail |
|---|---|
| The historical import runs once | The optional import of completions from the previous 12 months can be run later than setup, but only once. It cannot be repeated or extended afterwards |
| Historical scope is fixed | You choose either no history or the previous 12 months. Other periods are not available. The 12 months are counted back from the moment the import runs. |
| Only completions in selected catalogs count | Completions of courses outside the synchronized catalogs are not sent |
| Certifications are standalone | Certifications reach 365Talents as independent records, not linked to a synchronized course, because a certification can be awarded without a course |
| Certification synchronization covers everything | You cannot select which certifications are sent, and there is no setting to switch the synchronization off |
| No record-level certification log | The integration does not log certification synchronization record by record, so individual certifications cannot be traced or reconciled from the Docebo platform |
| Imported items may be missing dates | An imported completion without start and end dates asks the learner to enter those dates before it can be added to their profile |
| Skills are never updated automatically | A completion produces a suggestion that the learner accepts or dismisses |
The embedded experience
| Limitation | Detail |
|---|---|
| Platform branding does not apply | Custom CSS and Branding Studio customizations do not affect the embedded 365Talents content, which keeps the styling provided by 365Talents |
| Dialogs open inside the embedded area | Dialogs from 365Talents open within the embedded area rather than over the whole page. The surrounding Docebo navigation stays visible, and long dialogs may need scrolling inside the embedded area |
| Welcome pages cannot be redesigned | Their layout is fixed. You cannot add content blocks or text, edit or add links inside them, design a layout or create variants for different groups. In the Docebo platform you can change the page name and description. |
| The built-in pages must be placed in menus | The three built-in pages must be added manually to the appropriate existing menus. Menu visibility and 365Talents rights are configured separately |
| Only purchased capabilities appear | The embedded experience reflects the 365Talents capabilities your organization has purchased and enabled, and each user's 365Talents rights. Features outside your package are not shown |
| Mobile app | The Docebo mobile app does not support the embedded 365Talents experience. Use the integration from a browser |
Skills, reporting and other platform features
| Limitation | Detail |
|---|---|
| Native skill management is turned off | See the table earlier in this article for the full list of features affected |
| No 365Talents skills data in the Docebo platform | The 365Talents skills taxonomy is not copied into the Docebo platform, and there is no writeback of skills of any kind |
| Features that depend on skills lose context | AI-based channels, skill tagging on content and skill-based search remain available but do not receive 365Talents skills data, so their results may be incomplete or irrelevant |
| Two sources of recommendations | The Docebo platform's own content recommendation engine continues to operate independently, so learners may see recommendations from both |
| Reporting stays in two places | Learning analytics remain in the Docebo platform and skills and job analytics remain in 365Talents. There is no combined report |
| Skills content is outside Docebo reports | Notes, potential ratings, skill levels, feedback and validations are stored in 365Talents. They do not appear in Docebo reports |
| No migration from native skill management | Existing skills data in the Docebo platform is not migrated into 365Talents |
| Language coverage differs | 365Talents does not support every language available in the Docebo platform. Confirm coverage with your Docebo representative before activation |