Adding OpenID Connect and Facebook authentication options to the Sign-In utility page.

Previously, comments might have been trapped in the Liferay UI; now, they are first-class citizens in the API, allowing for seamless discussion threads across any connected platform.

Liferay has expanded its Headless API capabilities to include full management of Object Entry comments. When commenting is enabled for an Object definition, developers can now interact with those discussions via dedicated REST endpoints. This update supports full CRUD operations (GET, POST, PUT, and DELETE) using External Reference Codes (ERCs) for easier identification across systems.

Key Benefits:

• Feature Parity for External Applications: Developers building custom front-ends can now provide a fully interactive "social" experience.

• Complete CRUD Capabilities: Users aren't just able to read comments; users can programmatically create, update, and delete them.

Customers can now leverage a Liferay Toolkit to quickly and reliably spin-up Liferay in AWS. By leveraging our toolkit, customers can speed-up their deployments, as well as benefit from a robust and reliable infrastructure that reduces costs and increases predictability in the long run. 

Key Benefits:

• Increased visibility of Liferay Application and every other application in your EKS cluster;

• Reliable deployment process with easier to spot drifts;

• Operational cost reduction for running Liferay in AWS.

The Digital Sales Rooms provide a streamlined experience where sales representatives can quickly launch branded deal portals using pre-configured site templates. Within these rooms, a centralized content hub allows for the seamless sharing and management of documents, proposals, and multimedia assets, ensuring all stakeholders are aligned on the latest versions.

To drive proactive sales strategies, the platform includes an Engagement Tracking Dashboard that monitors buyer activity in real-time, highlighting which assets are being viewed or downloaded. Collaboration is facilitated through a persistent commenting system that keeps deal-related discussions in context, while a library of specialized Page Fragments allows teams to build tailored, visually engaging buyer experiences, such as milestone timelines and video introductions, without requiring technical design skills.

Access is managed through a secure, account-based invitation flow, ensuring that sensitive deal data.

Key Benefits:

• Accelerated Deal Velocity: By centralizing documents and approvals, DSR reduces the friction caused by "lost" emails and versioning confusion, leading to faster decision-making cycles.

• Data-Driven Sales Strategy: Engagement analytics allow Sales Reps to gauge buyer "heat" levels, knowing exactly which stakeholders are active and which documents are most interesting, enabling more targeted follow-ups.

• Professionalized Buyer Experience: Provides B2B buyers with a modern, self-service portal that is consistently branded and easy to navigate, reinforcing the seller’s position as a premium partner.

• Reduced IT Overhead: The no-code site creation flow empowers non-technical staff, such as Sales Engineers or Account Executives, to spin up secure environments without intervention from the IT department.

1. Digital Sales Room - Creation

2. Digital Sales Rooms - Uploading Documents

3. Digital Sales Rooms - Invitations & Contributor's Perspective

4. Digitial Sales Rooms - Analytics

The platform now features a "Reset Consent for All Users" button located within the Instance Settings under the Platform configuration for Terms of Use.

When an administrator activates this button, the system automatically resets the agreedToTermsOfUse flag for every account in the instance, which effectively forces all users to review and accept the current legal version upon their next login.

To ensure complete transparency, this action triggers a specialized AGREED_TO_TERMS_OF_USE audit event rather than a standard user update log. This dedicated event captures critical metadata within its payload, specifically the articleId and groupId, to provide definitive proof of exactly which version of the terms was active at the time of the reset.

Key Benefits:

• Regulatory Compliance: Easily prove exactly which version of your legal terms a user accepted, simplifying audits for GDPR, CCPA, or internal legal reviews.

• Operational Efficiency: Eliminates the need for manual workarounds or technical intervention when legal documents are updated; a single click handles the entire user base.

• Granular Reporting: By using a dedicated audit event instead of a generic update flag, administrators can filter logs more effectively to monitor compliance trends and completion rates.

We’ve introduced the ability to import and export categories and tags directly within the new CMS. This feature allows you to manage your site’s organization in bulk, removing the need to create or edit every individual item one by one.

Key Benefits:

• Saves Time: Quickly set up or update large lists of categories and tags through a single file upload rather than manual entry.

• Better Accuracy: Easily audit and clean up your tags in a spreadsheet to ensure consistent naming and organization across your entire site.

This epic is focused on implementing targeted improvements to the import/export translations functionality. In the past, due to resource and time constraints, we were not able to fully optimize the user experience for this feature. This work is aimed at addressing those known shortcomings, specifically by improving the UX and the functionality of key buttons and drag and drop for uploading items, to make the process more intuitive and user-friendly.

As part of Liferay strategy to increase product led growth, we are going to offer a free tier version of our CMS with some key limitations to allow users to test and interact with the product enough to understand if the product meets their needs.

To make this possible, we need to implement how the tiers (Free and Enterprise) will affect the product and how these customers can move from the Free to the Enterprise through the product.

Key Benefits:

• Lower Barrier to Entry: Users can start building and testing their ideas immediately without upfront investment, making it easier to validate the CMS for their specific needs.

The product currently relies on a legacy CMS alongside a newly developed CMS, requiring parallel maintenance, duplicated functionality, and fragmented content workflows. This increases operational cost, slows down feature delivery, and creates inconsistencies in how content is managed and consumed.

This epic aims to inform the users that we are putting the current CMS in maintainance mode, preparing the field to add the feature flag in next releases

Key Benefits:

• Inform the users about the features set as In Maintenance

During the reviewing of the CMS experience and fixing bugs, we detected some product gaps and improvements that can make the user experience smoother, so this epic’s goal is to tackle them to ensure a stable and reliable user experience.

Key Benefits:

• Allow to search members in a space for non admin users

• Improved category creation

• Filter by space for content structures

• List view for Space home view

We have introduced several new bulk actions to the CMS to help you manage large volumes of content more efficiently. Instead of handling items individually, you can now perform complex administrative tasks across multiple selections simultaneously.

Key Benefits:

• Assign Workflow for Content Structures in bulk

• Expire content in bulk

• Delete versions of a content in bulk

• Export translations of different content in bulk

As part of improving asset management efficiency, this epic introduces bulk Copy and Move actions for assets within the CMS. These actions will allow content creators to organize and duplicate multiple assets at once, across locations in Spaces they have access to. The functionality should maintain the same user experience principles and behavior as the existing single-asset Copy and Move actions, extended to handle multiple selections simultaneously.

Key Benefits:

• Copy assets in bulk

• >Move assets in bulk

The Questions Widget is a legacy application that was primarily maintained to support Liferay Ask. With the recent migration from Ask to Discuss (Liferay's new forum platform), this widget is no longer needed. Therefore, the Questions Widget is being deprecated to reduce technical debt and ongoing maintenance costs.

Search re-indexing has been optimized to deliver shorter re-index windows, especially for Objects-heavy deployments. In testing against production databases and architecture, we observed re-index improvements of 2x or more across the evaluated datasets, with gains reaching up to 10x on specific workloads. The optimizations primarily targeted improvements that scale with the volume and complexity of Object data being indexed.

Key Benefits:

• Shorter re-index windows reduce maintenance overhead and downtime risk

• Validated on a production-equivalent distributed architecture

• Largest impact for Objects-heavy installations

Building on the automated database repair routines introduced in 2025.Q4, Liferay DXP continues to expand the set of repair processes that run during the upgrade. Based on additional research into customer upgrade issues, new repair routines automatically identify and correct further sources of database inconsistencies, orphan references, and invalid data — before they cause upgrade failures or performance bottlenecks. These repair routines remain targeted at known issues with data structures only, keeping your critical data content safe. Details of each repair process continue to be provided for review in the Upgrade Report after the database upgrade completes.

Key Benefits:

• Minimize risks for current and future upgrades

• Automates data maintenance

When using the Liferay DXP Database Partitioning feature, the system now enforces strict access controls ensuring only the authorized database partition is accessible for any given request. This completes foundational security work and extends proper enforcement to all Liferay entry points, including Headless APIs and Client Extensions.

Key Benefits:

• Prevents unauthorized cross-partition data access in multi-tenant environments

• Ensures consistent partition access enforcement across all Liferay entry points (Headless, Client Extensions)

This is a major version release that brings important platform updates and security enhancements alongside several necessary breaking changes to ensure the continued delivery and stability of Liferay Developer Studio.

Key Benefits:

• Eclipse Platform Update: The underlying platform was updated to Eclipse 2025.12, taking advantage of the latest features and security updates from Eclipse. For more information, please see https://eclipse.dev/eclipse/news/4.38/.

• Blade Version Update: The packaged Blade version was updated to 8.0.1-SNAPSHOT.

This feature introduces a centralized administration interface within the Data Set Manager to oversee and moderate User Views. Administrators can now access a global list of all User Views to monitor usage or perform cleanups.

Key Benefits:

• Centralized Oversight: A new "Manage User Views" button in the Data Set Manager provides a complete list of all User Views for easier monitoring.

• Contextual Access: Admins can jump to the management view from specific Data Set settings, where the list is automatically pre-filtered to show only the views belonging to that Data Set.

• Administrative Control: Enables admins to maintain system hygiene by deleting individual or multiple User Views via bulk actions.

• Full Visibility: Provides key details at a glance, such as which user created the view and which Data Set it belongs to, ensuring better governance of user-generated configurations.

From now on CK Editor 5 will be the default rich text editor present in Liferay DXP. For those customers with custom plugins or other particularities over CK Editor 4 that don’t want to upgrade yet, they can enable the deprecation Feature Flag (FF-11235) to have CK Editor 4 as default in DXP.

Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.

From now on CK Editor 5 will be the default rich text editor present in Liferay DXP.

Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.

Content teams can now find and replace text, URLs, or terms across the entire CMS repository in a single action — covering titles, content fields, and friendly URLs. Every operation includes a mandatory preview, scoped targeting, and automatic versioning, so large-scale updates like rebrandings or URL migrations are fast, reversible, and low-risk.

Key Benefits:

• Cut rebrandings and terminology rollouts from hours of manual edits to a single bulk action.

• Preview every change before it's committed, with automatic versioning if you need to roll back.

• Scope replacements by site, content type, or field so global updates stay surgical instead of sweeping

CMS administrators can now modify content structures and their repeatable fields after publication — adjusting field configurations, nesting order, and repeatable settings without deleting existing content. Teams iterate on their data models as business needs shift, and all previously published entries stay intact.

Key Benefits:

• Refine your content model based on real-world usage instead of locking in every decision up front.

• Skip the "delete everything and rebuild" cycle when requirements change — existing entries come along for the ride.

• CMS admins adjust structures directly, without pulling in developers or database work for every tweak.

Data modelers can now define Link Content fields that let content creators select existing entries from other objects—single or multiple—instead of retyping the same values across entries. The CMS moves from isolated documents to a connected data model, so information like vendor names, categories, or authors stays consistent across every publication.

Key Benefits:

• Eliminate typos and inconsistencies by picking existing entries instead of re-entering text.

• Reuse the same author, category, or vendor across hundreds of entries—update it once and it propagates everywhere.

• Support both single and multi-select relationships, from "one author per article" to "many products per campaign.”

This release rounds out the Pages Management APIs with new endpoints, broader page-type coverage, and refinements to how references and scopes are handled. The updates close long-standing gaps — supporting more page types end-to-end, expanding the catalog of page elements and fragments exposed through the API, and hardening the data architecture around scopes and secure references. The result is more reliable imports, exports, and staging across every site component.

Key Benefits:

• Broader API coverage: every page type is now supported end-to-end, not just the subset covered before.

• Fewer surprises in staging: scope-aware identifiers catch missing references and deleted assets before they break the live site.

• Consistent behavior across sites, staged environments, and imported content — the API no longer behaves differently depending on the page type.

We've refined how users discover and install Marketplace fragments from inside the Page Builder. Browsing, previewing, and installing partner and community fragments now feel native to the editing flow—fewer clicks, clearer discovery, and less context switching between the editor and the Marketplace. Native, already-installed, and Marketplace-available fragments now live side by side in the same experience.

Key Benefits:

• Faster discovery and installation of Marketplace fragments without breaking the editing flow.

• Clearer distinction between native, installed, and Marketplace-available fragments, so builders pick the right one at a glance.

• Less context-switching: everything happens inside the Page Builder instead of jumping to the Marketplace and back.

The Style Book Editor has been improved to make managing design tokens simpler and more intuitive, with a clearer approach to editing colours and improved overall usability.

Key Benefits:

• Faster updates: Edit colour tokens quickly through a single, clear interaction point.

• Easier to use: Fewer competing controls reduce confusion and make the editor more approachable.

• Consistent experience: Interaction patterns now align with the Page Editor, improving learnability.

• Built for growth: A stronger foundation to support future design token capabilities and enhancements.

• Fewer errors: Improved interactions reduce friction and mistakes when updating styles.

Style Book tokens are now aligned with Clay variables, ensuring that design changes apply consistently across UI components and themes.

Key Benefits:

• Reliable theming: Changes made in Style Books now correctly reflect across all Clay-based components.

• Real consistency: No more gaps where updating a token doesn’t affect parts of the UI (e.g. alerts, buttons).

• Better visibility: Token changes are accurately represented in the Style Book editor.

• Stronger foundation: Clay now exposes core variables (colours, typography, spacing) as CSS custom properties, making them easier to control.

• Future-ready: Sets the groundwork for more advanced theming and design system capabilities.

The Global Menu has been promoted from Beta to GA and is now the default, fully supported navigation experience in Liferay DXP. It provides a single, consistent entry point to access applications and settings, with improved structure, stable behaviour, and integrated search for faster navigation.

We are excited to announce the General Availability (GA) of the OpenSearch 2 Connector v2.0.0 for 2026.Q1 and v2.1.0 for 2026.Q2. This release is an important milestone in our Cloud Native Experience strategy, providing a viable alternative for Liferay DXP users.

This version has undergone additional testing and validation to ensure dependency alignment with the latest OpenSearch 2 clients and field mapping consistency with our Elasticsearch 8 connector.

The new version of the application is will be released on Liferay Marketplace.

Key Benefits:

• Native AWS Integration & Cost Optimization: Connect Liferay DXP with AWS OpenSearch Service. By leveraging managed infrastructure, organizations can reduce operational overhead, streamline their cloud stack, and optimize hosting costs through AWS-native service configurations.
• Flexible Search Architecture Production-ready alternative to Elasticsearch. This connector ensures that Liferay DXP remains flexible, allowing you to choose the search engine that best aligns with your infrastructure requirements and corporate standards.

Note: Liferay supports the connector and its features. While Liferay can provide an example deployment configurations for AWS OpenSearch Service, the management and maintenance of the underlying service remain the responsibility of the infrastructure provider.

Manage site updates with total confidence using the new Maintenance Mode. This feature allows Site Administrators to take a site offline for the public while maintaining full operational access behind the scenes. When enabled, visitors receive a dedicated maintenance page with the correct SEO-friendly status (HTTP 503), while administrators can continue to navigate, edit, and verify site pages to ensure everything is perfect before going live again.

Key Benefits:

• Safe Production Verification: Unlike standard deactivation, Maintenance Mode allows admins to view and test the full site experience live, ensuring that deployments are successful before the public ever sees them.

• SEO Protection: By serving a proper 503 Service Unavailable status, the system tells search engines that the downtime is temporary, protecting your search rankings during major updates or migrations.

Managing large-scale site deployments just got easier. We have introduced new headless API endpoints that allow developers to toggle site states (Active or Inactive) programmatically, bypassing the need for manual configuration within the Control Panel.

Key Benefits:

• Automated Site Governance: Enables high-speed bulk management of site states, allowing your team to sync site availability with external business systems or custom orchestration tools.

• Enhanced System Stability: Built-in safeguards protect the platform by preventing the accidental deactivation of essential system sites (like Global), while strict permission validation ensures only authorized users can trigger state changes.

Reviewing complex page updates is now faster and more intuitive. We’ve introduced a Review Side Panel within the Publications Review Change screen that automatically surfaces content changes made on a Content Page. Instead of manually digging through the full change list or a Pages’ Children tab, reviewers can now see exactly which text and images have been modified in a page’s Fragment Entry Links via a consolidated, easy-to-read list.

Key Benefits:

• Focused Decision-Making: Instantly identify high-impact changes (like text and image updates) without getting lost in technical changes.

• Streamlined Workflow: Eliminates the need to cross-reference multiple tabs or Fragment Entry Links, allowing content reviewers to complete reviews with total confidence.

The page reviewing experience now provides a more accurate way to locate and compare changes. The Publications Display tab for Content Pages now provides the Unified view, highlighting additions, removals, and format changes, so you no longer have to hunt for differences on the new page version.

Key Benefits:

• Review accuracy: Reviewers feel confident that no change goes to production without the proper attention.

We have implemented a new translation status feature in the web content editor, labeled "Translating," which provides information about the number of translated fields and those still requiring translation. This feature helps users to quickly identify areas needing translation. Additionally, all translatable fields, including metadata, are now conveniently displayed on the left side of the screen, reducing the likelihood of overlooking them.

Users can readily spot content that is not visible to Guest users through an icon, whether it's in list or table view or within the web content editor. Additionally, this feature is accessible in the item selector, empowering users to discern which content is not viewable by Guest users.

You can now have access to the event’s details when selecting a calendar event and be redirected to the already existing details page of that particular event. It is also possible to map a Calendar Event’s specific URL, along with some other fields, in order to use it in emails so the recipient can click on it and be redirected to the Event’s details.

Now it is possible to easily identify the content you have created and any recent content you generated. This enhancement streamlines and optimizes this workflow.

Easily configure the friendly URLs for the different asset types, updating URL separators. In addition to that, now users are able to set categories within a blog’s friendly URL and easily identify by the URL what is the main topic of the page they are visiting.

This feature aims to refine the Analytics Cloud Usage Page. Alongside UI enhancements for a better user experience, we focused on enhancing data accuracy and real-time precision. Our efforts aimed to eliminate data discrepancies and prioritize transparency for the users.

Key Changes:

1. To promote pricing transparency, we removed the outdated prices from the Workspace settings and implemented a clear message prompting users to reach out to their Customer Success Manager for information on upgrading their plan.

2. Aiming to simplify the interface and highlight pertinent subscription details, some changes were made to the UI of the Subscription and Usage menu, focusing on displaying relevant information to the customer related to their current plan.

We're introducing advanced script loading options for JavaScript Client Extensions in Liferay, providing developers more control over how JavaScript is applied to pages. This update allows the specification of async and defer attributes directly in the extension's configuration, optimizing the loading process and improving page performance.
Benefits for users:

• Improved Page Load Performance: by setting async or defer attributes, scripts can be loaded non-blocking, enhancing page responsiveness.
• Enhanced Control: developers can pre-set these attributes in the YAML configuration or through the UI, ensuring scripts behave consistently across all pages without further adjustment.
• Streamlined Configuration: once set, these attributes are locked at the extension level, eliminating discrepancies and simplifying script management.

Allow developers to specify additional attributes to the <script> tag when deploying in with the JS Client Extension.

Example usage in client-extension.yaml: liferay-portal/workspaces/liferay-sample-workspace/client-extensions/liferay-sample-global-js-2/client-extension.yaml at master · liferay/liferay-portal

    scriptElementAttributes:
        async: true
        data-attribute: "value"
        data-senna-track: "permanent"
        fetchpriority: "low"

Or, developers can configure the attributes via the create Client Extension UI too:

When configuring a JS CX on a page and async/defer Boolean attributes are present in the CX (set in the yaml / defined through the UI), the following behaviors apply in regards to the Load type options:

1. The attribute set in the CX will be used and the ability to change it when applying it on a page will be disabled.
2. When both attributes are set in the CX, async will be applied.
3. When async or defer is set to false in the CS, the related option will be removed from the Load selector. (e.g. if defer: false the load options available for the user will be default and async).

This feature introduces the capability to connect Liferay Objects with SugarCRM Objects, empowering users to synchronize and store their data efficiently between the two platforms. By bridging these systems, users can streamline their workflows, enhance data consistency, and leverage the robust features of both Liferay and SugarCRM.

Users can now, with low effort, connect their Liferay and SugarCRM environments, eliminating the need for manual data transfers and reducing the risk of errors. This enhancement not only simplifies data management but also enhances the overall user experience by providing a cohesive and integrated ecosystem for managing customer data.

We have improved the behaviour of an existing configuration to be able to properly publish a child page in a Staging process to Live site without its parent(s). This also improves the performance of publishing changes.

It is now possible to select Date Times as a product option type, configuring purchase options for products based on date, times, time zones, and durations, allowing for the sale of time slots.

Manage contacts directly related to accounts like phone numbers, emails, websites, addresses.

A new Contact Tab in Account details page with 2 internals tabs was created:

1. Addresses
2. Contact Information

Users with “Accounts > Account Entry: Manage Addresses” permission should be able to manage their contacts with all these actions:

• Add
• Edit
• Remove
• Mark as primary

Example of managing a phone number:

Users without “Accounts > Account Entry: Manage Addresses” permission should be able to only view the existing phone number entries.

The Server Administration interface provides powerful tools for controlling the server. As an added layer of security, CAPTCHA is now required for actions in Server Administration pages and the Gogo Shell page. Due to the sensitive nature of these controls, the system will still enforce CAPTCHA on these pages, even if the “Maximum Challenges” configuration is set to a negative number.

To create Sign In, Forgot Password, and Create Account utility pages, it's necessary for these three views of the Login portlet (i.e., Sign In widget) to be available as individual widgets, which can be placed on pages separately. As a result, Sign In, Forgot Password, and Create Account are now accessible as separate widgets.

It's worth noting that the Sign In widget retains its previous functionality.

We aimed to facilitate seamless navigation between various Utility pages, whether there are multiple or just one.

It allows users to map fields on the first level of related elements or any hierarchical structure through a tree view which is searchable and expandable.

In addition, it is possible to map leaf fields, the common use case, but also parent fields which include all the children data to be rendered through a Client Extension.

Until now the Data Set was always rendered as a table with one column for each mapped field. From now on, the admin user can define up to three different visualization modes for the same data: Table, List and Cards.

These visualization modes share the configurations about: filters, actions, sorting and pagination. However, each visualization mode can have different mapped fields decided by the admin users.

Also, a new Settings tab to select the default mode has been added.

Final users will be able to view the visualization modes created by Admin Users and they will be able to change between them to discover the data in the way they want.

The Data Set for actions has been improved to provide new capabilities to the users:

• For the Item Actions: now there are 4 new available types available on top of the link Action: Async, Headless, Modal or Side Panel . It allows Admin Users to connect items to new functionalities and use cases.
• Creation Actions: this option has been created in order to allow Admin Users to create new data or direct their users to a place where they can create it.

The autocomplete attribute grants the user agent permission to provide automated assistance in filling out form fields. This feature can significantly speed up the form-filling process, especially for repetitive or standard information like names, addresses, and email addresses. This also allows screen readers which use standard attributes such as autocomplete to assist users navigating websites.

Incorporating the HTML autocomplete attribute into your forms is a simple yet powerful way to enhance user experience. By leveraging autocomplete suggestions, you can streamline the form-filling process, reduce errors, and ultimately create a more user-friendly environment. Experiment with different values, test across browsers, and watch as your users appreciate the improved efficiency of your forms.

When publications go out of date, they are completely useless and all changes made to them can not be leveraged in any capacity. The changes in this feature allow publications users to move changes from an out of date publication to another publication. This allows users to salvage changes after an upgrade.

This feature prevents portal from being unusable when a change-tracked entity being modified in a publication is removed from production. If an entity is being modified in a publication, it cannot be removed from production. If a deleted entity in a publication is being modified in another publication, the publication with the deletion cannot be published.

We are constantly working on improving performance of Publications. We have implemented improvement for Timeline and Conflict checking icons.

Boost the performance of reverting changes , when the DB has huge amount of records. This way the usability of Publications further increases.

If a conflict appears between the scheduled publication and Production before or during publishing stage, we have added a functionality to provide more information inside Liferay notifications when this situation occurs.

This features creates a reviewer role that has read-only (and no update) permissions. It grants permission to review the draft of a content page, or the pages that are submitted through a workflow and are still pending approval and publication.

Page Creator now can efficiently manage permissions for their website, distinguishing between public and restricted pages. Key functionalities, such as unique designs and restricted access, are incorporated seamlessly.

Requirements include easy identification of page visibility, bulk permission management, and configuration options for both individual pages and entire branches.

Provide the option at Instance and Site settings to the XML sitemap to allow customers to customize the inclusion or exclusion of content according to the SEO technical requirements.

When the User reaches Control Panel → Instance Settings, a new menu item (SEO), under Platform, will be shown. By accessing this menu, the user will be able to include/exclude different content.

When the user has Download permission on a file, then the Documents and Media File result features a download link in the Search Results widget in all out-of-the-box widget display styles.

The Search Results widget Template Context has received a new field to obtain the download URL in custom display templates: ${entry.getAssetRendererURLDownload()}