Thrive Discovery

Allow adaptive learning to be driven by AI / automation

We want the ability for automated / AI-driven adaptive learning so that the manual effort associated with a rules based setup is lessened, or ideally removed. Additionally, adaptive learning that has AI at the core will be able to factor in many more variables and data points to help curate a hyper-personalised experience for learners.

Make it possible to create rules-based adaptive learning

We want the ability to create rules based adaptive learning so that a single pathway or group of learning content can be tailored to the individual based on their role, skill level, location, mastery of the topic, and so on. This would significantly reduce the amount of duplicative work required to construct the appropriate experience for the learner, and allow them to efficiently and effectively progress through only the content that’s relevant for them.

Kiki / AI

Make Kiki / AI data available within Thrive Analyse

We’d like Kiki / AI usage data within Insights to be able to report on how many have used the capability, what they are searching for, what they get answered & what they don't get answers for (gap analysis) how many then go on to complete learning from search results etc.

[Kiki] Support contextualisation and learning strategy suggestions

We’d like Kiki to provide richer contextualisation of content (e.g. applying learning to specific industries or contexts) and suggest learning strategies to accompany content.

[Kiki] Increased personalisation in Kiki responses

Kiki currently doesn't tailor responses based on the user's job data e.g. job title, department, location etc. Although content-surfacing can be managed through audience visibility settings, we’d like Kiki's responses to take into account job title/department etc. Our specific use case is for technical skills/competency-related questions, like "what should I do to progress my career?" With Kiki's answer/recommendations taking into account the user's job title/department/skill level etc so that Kiki usage can be linked through to organisational skills frameworks.

Skills, Goals, and CPD

[Skills] Global Switch to Disable Skills

Implement a switch that allows customer Administrators to completely disable and hide the Skills functionality from all users and related administrative views.

[CPD] Feedback and Comments on Goals

To implement a dedicated, persistent comments and feedback section directly tied to Goals, thereby centralising performance documentation and actively supporting structured manager-employee 1:1 conversations.

[Goals] Bulk Goal Assignment for Admins

Enable Learning Administrators and Super Administrators to bulk assign a single goal (or a set of pre-defined goals) to multiple users simultaneously.

[Goals] Include Goal Deadlines in Manager Digest Notifications

Enhance the Manager Digest Notification to include the deadline or due date for any goals referenced in the notification content.

[Skills] Admin Control to Disable or Restrict User Skill Creation

Provide client administrators with the ability to restrict or completely disable the user-facing functionality for creating new skills.

[Skills] Enhancements to User API Endpoint for Skills Data

To update the User API endpoint response to include crucial skill level detail and flag deleted skills, enabling client automation.

[Skills] Role/Audience-Based Goal and Skill Assignment

To introduce an administrative function that allows Skills and Goals to be assigned at Audience level.

[Goals] Goal Template Management and Assignment

Implement a Goal Template Library that allows administrators and managers to create, save, and reuse standardised goals, eliminating the need to build common goals from scratch for every user assignment.

[CPD] Include Time Spent/CPD Hours on Completion Certificates

Enhance the certificate generation feature to automatically include the total time spent (expressed as verifiable CPD hours or minutes/hours) on the associated learning content.

[Skills] API endpoint to allow skills to be added

We’d like the ability to add new skills to the Thrive platform (that are not already created in Thrive) via an API call. Currently /rest/v1/users/{userID}/tags only accepts requests to add skills that already exist, it does not allow for creation of new skills.

Mentoring

Ability for mentors to become verified or endorsed

The ability to become a verified or endorsed mentor gives great value to us as mentees will have great confidence that their mentor is able to expertly assist them with the progression they’re seeking to make. We would like a way for mentors wishing to become verified/endorsed for a particular item/topic, or as a mentor in general, to be ‘tested’ or have to prove their capability prior to receiving the verification.

Schedule mentoring sessions via Teams, Google Meet, etc from within Thrive

We’d like to be able to schedule mentor/mentee sessions on Microsoft Teams, Google Meet etc directly within Thrive. As part of this we want to be able to see the calendar/diary of both the mentor and mentee so it’s possible to select an suitable time for both people. Lastly, we want to be able to join the meeting via a link in Thrive’s mentoring interface.

Extend mentoring to coaching

Mentoring and coaching are different concepts and we’d like the platform to provide an experience for coaching that is well suited to that. Currently the mentoring setup doesn’t support this in the best way.

Integrations and Connectors

Provide an Events API Endpoint

Build an Events API endpoint that allows users to retrieve information such as the below about Events on the Thrive platform: Dates - creation date, start and end dates (latter if applicable) Duration/length of event Author/host (name, employee ID, etc), title, summary/description Sign-ups, cancellations, and attendees

Show “last modified by” for user data changes (admin visibility)

It’s currently not possible to see who made specific changes to user data, particularly for actions taken by super admins or via integrations. While all data is stored (e.g. status changes, logins), the source of a change is not visible. This can make it difficult to trace updates, validate actions, and maintain accountability - especially in environments with multiple admins or external systems making changes. We’re exploring adding visibility into the most recent change made to a user record — for example, showing a “last modified by” field and timestamp in API responses and surfaces like Insights. This would provide a lightweight way to improve auditability and traceability.

Ability to select specific content items from external providers

We’d like the ability to cherry pick learning content, pathways/courses, etc that are mastered on external content providers such as Go1, LinkedIn Learning, Udemy, and so on. Currently we don’t have this level of fidelity when ingesting this content into Thrive.

API access to learning asset content

Today, the API provides access to content metadata, but not the underlying learning assets themselves. This suggestion is for the API to support retrieving the content of learning assets (for example, lesson text, assessments, and other learning materials) so they can be analysed programmatically. This would enable organisations to automate content reviews, identify outdated or duplicate content, assess accessibility and content quality, review assessments, and improve content governance at scale.

Audience API - ability to move Audiences between Structures

Currently it is possible to move an Audience to another Structure via the UI, but it is not possible to do this via the Audience API. We’d like this as it’ll allow us to manage this kind of update programatically instead of manually via the UI.

Display learning progression in Thrive for externally hosted content

Currently we only see whether a piece of external learning has not been started or has been completed but we know that progression data is available from the APIs offered by content providers such as LinkedIn Learning and Go1. We’d like this information to be made available in Thrive so both learners, managers and admins can see this data alongside that which is available for native Thrive content.

Brilliant Basics

Under consideration

Schedule publish date and time for content

Currently, content is published immediately when made live, with no option to schedule it for a future date and time. This makes it harder to plan and coordinate content releases in advance — particularly for time-sensitive announcements that need to go live at a specific moment, but which you don’t want to create a campaign release for. We’re exploring the ability to schedule a publish date and time for individual pieces of content, allowing them to be automatically released into the platform at the right moment.

Reorder Content on the Explore Page

When content sits under a secondary tag on the Explore page, there's currently no way to control the order it appears in beyond chronological. We'd like the ability to arrange content in a specific sequence that makes sense for our learners.

Warn you when archiving content that is used in pathways

It’s currently possible to archive content without visibility of where it’s being used. This can lead to content being unintentionally removed from live pathways, causing gaps in learning experiences and issues with compliance, audits, and reporting. We’re exploring ways to provide better visibility and safeguards when archiving content — for example, highlighting where content is used or preventing archiving if it’s part of a pathway. This would help reduce risk and ensure critical learning content isn’t removed unintentionally.

Support numerical custom fields in user profiles

Currently, custom profile fields only support text values, making it difficult to store and use numerical employee data within Thrive. This limits audience targeting and automation use cases where administrators need to segment learners based on measurable criteria. We’re exploring support for custom number fields that can be populated manually or via integrations and used within audience rules. This would enable use cases such as targeting learners based on tenure, performance scores, certification counts, or other numerical attributes using operators like greater than, less than, equal to, and between.

Manager status based on active reports only

Currently, users are treated as managers if they have reporting lines, even when those reports are no longer active (for example, suspended users). This can result in users being included in manager audiences, accessing manager-only content, and appearing in reporting where they no longer have active responsibility. We’re exploring updating manager status so that it is based only on active direct reports. With this change, users without any active reports would no longer be treated as managers in the system.

Extend profile privacy controls

Current privacy settings only prevent users from appearing in search results. Hidden profiles can still be discovered through other areas of the platform, such as team structures or event attendee lists. This can create a mismatch between how organisations expect privacy settings to work and the level of visibility users actually have. We’re exploring extending profile privacy controls so hidden users remain hidden across the platform, giving organisations more consistent control over employee visibility and privacy.

Vicky Higgins

Access to full transcripts for learning content

Some learners find it difficult to follow content without being able to read along or review at their own pace. Currently, transcripts are not always available in a way that allows users to easily read the full content. We’re exploring the ability to provide access to a full transcript alongside learning content, so learners can read, review, and consume content in a way that suits them. This could improve accessibility and support different learning preferences.

Language Equivalents in Assignment Notifications

We want to direct learners to the appropriate language variant for a piece of assigned learning/content within a notification. It is anticipated this will be achieved as part of our 2026 plans to introduce full language support on mixed content (via the Content Creator).