Skip to main content
Community Manager
October 15, 2025

Announcing the October 2025 release of Adobe Learning Manager

  • October 15, 2025
  • 1 reply
  • 211 views

The October 2025 release of Adobe Learning Manager is now live! Check out the highlights of this release below.

 

Go1 enhancements
You can now directly bring curated content from Go1 directly into your Adobe Learning Manager Learning Paths. If you have an active Go1 license you can access Go1 hub from within the learning path creation flow to curate a playlist from Go1 content using their advanced search capability, AI chat assistant and more filters.
Also, Go1 courses can now be part of recurring certifications. This allows consuming any compliance courses at regular cadence without setting up certifications again.

 

Instructor marked completions in Learner Transcripts
Earlier when using incremental Learner Transcripts (LT) for automation workflows, instructor marked completions after the session date were not captured. The completion timestamp reflected the original session end time, but not the time instructors marked the completion. As a result, learners' attendance and completion data was excluded from reports. Under the new enhancement, Learner's Transcripts will include completion data marked by instructors after the session date. This will ensure that any delayed attendance marking Attendance states like “Attended with pass/fail” will appear automatically in incremental LT exports.

 

Scoped announcement permission for custom administrators
As a custom administrator, you can now create announcements only for the user groups or catalogs within your defined scope.
What's new
1. Scoping rules allow custom administrators to create announcements for specific user groups or catalogs only.
2. When defining a custom role, administrators can assign announcement permissions with scope on user groups or catalogs.
3. Custom administrators are limited to creating announcements within their given scope.
4. The notification announcement report for custom administrators will display learners only within their assigned scope.

 

Social learning enhancements
Learners can now be tagged in social learning posts and comments through the ALM Learner Portal, Public API, and ALM Reference Site.
For Private Boards, the list of learners available for tagging is filtered based on the board-level scope settings. For example, on the Cardiologists External Private Board, only learners belonging to the Cardiologists user group assigned at the board level will be shown.
Learners who are tagged in a post, reply, or comment will receive both email and in-app notifications.

 

Internal user ID and manager email columns added to user report
The User report now includes a user’s internal user ID and their manager’s email address, to map them uniquely across different tools or API endpoints.

 

Language-based player status
Learners can now seamlessly switch between languages during their learning journey without losing progress and retaining module completion status for each language individually, allowing unlimited language changes while preserving all advancement.

 

And a lot more. Check out the details of all that's new and changed in this release.

 

    1 reply

    Participant
    October 16, 2025

    IMPORTANT TO NOTE: The inclusion of the "Mark Complete Date" column in the Learner Transcript reports was done in a way that it shifts other columns from their original position.

    For those customers using FTP integration connectors with other applications (e.g. HRIS systems) this change of columns position might affect your integrations. In our case, we used the "Status" column that was originally in the "Y" position, but then moved to "Z". Our integration did not recognize this change and the ingestion of data into our HRIS failed. It took us some time to find the culprit.

    It would be great if the Adobe engineering team communicated the potentioal impacts of these changes to avoid issues with data integrity or even data loss. Alternatively, new columns can be added to the end of the data set instead, even though it would still have an impact depending on how the integration scripts or SQL queries would run.